Hey, have you an idea how to reduce the delay for triggering a long press detected by compose ? Ideally i would like it to be 100ms or something like that. I tried using combinedClickable and detectTapGestures but with no really success.

I have this in design mockups. How would I go about adding white background to the text? I have tried doing two

Text

composables in the

Box

, with the former having

+ 1.sp

, but it doesn't align as perfectly as in the screenshot.

hi. somewhere i heard about Flow.collectAsState with an "InLifecycle" or "OnLifecycle" appended. It is preferred to the regular collectAsState. Anybody has more infos on it?

Seems like a noob question but can someone tell me why it would be bad to pass an activity to a screen/top-level Composable (one that already takes a ViewModel for instance, so it’s not skippable)?

is there an article about best practices for compose navigation? Should I do navigation in seperate composable or should I pass navController to viewmodel and do the navigation from there? What is the recommended way?

is this Compose idiomatic? to convert this:

@Composable
fun Example() {
    Row(modifier = Modifier.fillMaxWidth()) {
        Text(
            text = "Left",
            modifier = Modifier.weight(1f),
        )
        Text(
            text = "Right",
            modifier = Modifier.weight(1f),
        )
    }
}

to:

@Composable
fun Example(
    left: @Composable (Modifier) -> Unit,
    right: @Composable (Modifier) -> Unit,
    modifier: Modifier = Modifier,
) {
    Row(modifier = modifier.fillMaxWidth()) {
        left(Modifier.weight(1f))
        right(Modifier.weight(1f))
    }
}

am asking because of passing

Modifier

to parameter `@Composable`s. I want to hide

Modifier.weight(1f)

and I want everything using

Example

to have exactly 2 elements that occupy 50%/50% of space, without wrapping

left

and

right

into

Box

, for example, and applying

Modifier.weight(1f)

to

Box

container

hey folks, I’m using

NestedScrollConnection

as part of a collapsable view with LazyColumn work,

Box(
        modifier = Modifier
            .fillMaxSize()
            .nestedScroll(nestedScrollConnection)
    ) {
        LazyColumn ..

        CollapsingView..
    }

the idea is I want to get notified when user stops scrolling + they no longer interact with view,

onPostScroll

unfortunately is fired when scrolling stops regardless if I still have my finger down, any idea if there is a workaround?

Hello everyone! Does compose support ViewPager with Paging3?

After upgrading Compose from 1.2.1 to 1.3.0-beta01. This code can cause crash in release build even minify is disabled.

LineHeightStyle(
  alignment = LineHeightStyle.Alignment.Center,
  trim = LineHeightStyle.Trim.None
)

with this error message:

java.lang.NoSuchMethodError: No virtual method getCenter-PIaL0Z0()I in class Landroidx/compose/ui/text/style/LineHeightStyle$Alignment$Companion; or its super classes

Hi, my composable is moving the offset, but the background color is not moving. If I look in the layout inspector, I can clearly see that the offset has been moved. But the background color is still displayed at the old offset. What’s the problem?

@Composable
private fun QuackSelectedTabUnderBar(
    modifier: Modifier = Modifier,
    color: QuackColor,
    offsetProvider: Density.() -> IntOffset,
    widthProvider: Density.() -> Dp,
) {
    val density = LocalDensity.current

    Box(
        modifier = Modifier
            .offset(offset = offsetProvider)
            .then(other = modifier)
            .height(height = QuackTabUnderBarHeight)
            .width(width = density.widthProvider())
            .background(color = color.value)
    )
}

I used

Modifier.offset(offset: Density.() -> IntOffset)

for moving offset.

I see that

LazyColumn

crops half of its last item, am I missing anything? Code in 🧵

After having some recomposition problems with a List I started to look into the Compose Compiler reports and even though I have changed every single list to ImmutableList the reporting still gives me a weird result. A

Post

is (in theory) stable but a ImmutableList of Post is not... Am I missing something?

stable class Post {
  stable val id: String
  stable val title: String
  stable val subtitle: String
  stable val description: String
  stable val tags: ImmutableList<String>
  stable val imageUrl: String
  stable val type: PostType
  <runtime stability> = 
}

the strange thing is the empty “<runtime stability>” then I wrap this into a sealed with 3 states (this is for extra context but not directly related)

stable class Content {
  stable val showError: Boolean
  stable val tags: ImmutableList<Tag>
  unstable val posts: ImmutableList<Post> <------- ?¿?¿?¿
}

the Compose result is:

restartable scheme("[androidx.compose.ui.UiComposable, [_]]") fun DiscoverList(
  stable scrollState: LazyGridState
  unstable items: ImmutableList<Post> <-------- ?¿?¿
  stable onItemViewed: Function2<Post, Int, Unit>
  stable onItemClicked: Function2<Post, Int, Unit>
  stable header: Function2<Composer, Int, Unit>
)

Post is a simple data class… is it because it has a List of Strings?

Hello, I use Accompanist Pager but it looses the state of screens. I researched a bit and ran into this issue. And a related issue on IssueTracker is still empty. Did anybody here face a similar issue at all?

What is a recommended way to handle a variable that is only used for the very first composition and changed to null so it is not used again. But changing to null causes the recomposition so trying to find a good way to avoid this.

Hello! Does anyone have any idea at where should I start looking when getting:

Fatal Exception: java.lang.IllegalStateException: LayoutCoordinates androidx.compose.ui.node.InnerPlaceable@25c38a is not attached!

Im stuck with compose 1.0.5 and whenever I try to update (1.2.0-rc02 and accompanist 0.24.12-rc) crashes start popping into firebase. I have some Integration test running ok, and cant even reproduce locally but the amount of crashes in FB is significant to ignore. The stack-trace ( Full in 🧵 ) does not helps ( at least to mee)

Is Jetpack Compose not optimized for big projects? I tried now for 1 1/2 Weeks to get my performance right but didn’t succeed. Now I finally figured out that it has something to do with the sheer size of my project. When I simply comment out the the call to my MainScreen() inside the setContent{} method and put in some different code (for example Horizontal Pager + Tab Layout + LazyVerticalGrid) it performs worse in my big project than in a freshly created one even though it is running the exact same code. Only difference is that the laggy project has hundreds of other classes in it (which are not getting called cause I commentet out the call to MainScreen) and a lot more dependencies. Running both projects in Release + R8 enabled So as stupid as it sounds but I just simply have to give up on Jetpack Compose and get back to XML… I’m loosing hope

Does anyone know if there’s a way to make all the items in a row have the same height as the tallest item in compose? I could use a SubcomposeLayout but not sure if there’s a simpler way

I'm using Compose Coil for image loading in my project, I have a grid of images shown in my composable and they're driven by a state that would update the grid to another set of images. I'm using Coil with this image loader

val imageLoader = remember {
    ImageLoader.Builder(context)
        .bitmapFactoryMaxParallelism(10)
        .respectCacheHeaders(false)
        .build()
}

(I was playing around the bitmap parallelism and cache headers, I also tried providing disk/cache policies and enabling them in the

ImageRequest

but it seems like Coil is quite slow to load the images after they are cached. I tried my same code but use picasso-compose and the images load instantly (After being cached) whereas using Coil there's a split second load, I added a debugger to Coil to make sure it's not loading the image again from the internet (and it's not) The above was on production build for both Coil and Picasso Has anyone experience some performance issues with Coil in Compose?

Jetpack Compose stability in a KMM project I’m currently writing a KMM application where I use Jetpack Compose on the Android side. Of course most of the business logic, the ViewModels and data classes are placed in the

shared

module under

commonMain

. Now I have the problem that the Compose compiler determines all of my (immutable) data classes as unstable because they are placed in a different module. I cannot add the Compose runtime dependency to

commonMain

because this is not a multiplatform dependency and the project just won’t compile when doing so. Of course I could add wrapper classes like described in the linked article and use them only for Android, but this would mean I would have to start using generic types in my ViewModels extensively to ensure that I still share most of the business logic. Isn’t there another way of telling the Compose compiler which classes are actually immutable/stable, maybe via command line arguments or a configuration similar to ProGuard/R8? I’m using version

1.3.0

of Compose compiler.

With Horizontal view pager from accompanist lib it’s not possible to to get individual view model per pager , is there any solution or workaround for this ? Thanks in advance

Unfortunately Jetpack Compose is not as stable as advertised. I have 3 weird glitches in the app and one can only guess what the reason could be. I decided to go back to fragments

I have two texts inside a

Row

. I want each of them to fill all the available space, when their size isn’t equal (one small, one large), but apply

Modifier.weight(1F)

when both are large, so they would extend to the next line. Any thoughts on how to achieve that?

Have gone through this issue, https://issuetracker.google.com/issues/240016022 I am looking for another possibility as follows,

LazyColumn {
                items(10) {
                    CustomLookAheadLayout {
                          Text(text = "First Item")
                          Text(text = "Second Item")
                    }
                }
            }

Still I get error. Is this yet to support ?

In general, blurring is an expensive operation, so animating it is probably not the most efficient thing you can do 😄 You could try using Modifier.graphicsLayer and setting a render effect to use blur, and only apply the modifier to the content below. This only works on 31+ though

@RequiresApi(Build.VERSION_CODES.S)
fun Modifier.blur(): Modifier = then(
    graphicsLayer {

        renderEffect = RenderEffect.createBlurEffect(10f, 10f, Shader.TileMode.CLAMP)
            .asComposeRenderEffect()
    }
)

I wrote up a more concise Stackoverflow post for this issue here: https://stackoverflow.com/questions/73570553/how-to-prevent-accessibility-focus-from-moving-to-controls-behind-texposeddropdo

I want to apply an offset to the visible items in a lazy column based on their position in the layout container. I can get the visibleItemInfo from lazylistscrollstate which contains their offset to the top but having extreme difficulties with passing the changing offset to the visible items as the list scrolls

I’m going through some design review and fixing up inconsistent design. Honestly my UI code is a bit of a mess in this regard; padding, for example, is applied inconsistently, all over the place, as I’ve been just patching things together. So I’d like to build some reusable components to get it into a more consistent state. Can I ask for feedback on my approach?

Does anyone know of any reason

BackHandler

might not be intercepting back press? I am using it in a fragment:

@AndroidEntryPoint
class MyFragment : BaseFragment() {

    override fun onCreateView(
        inflater: LayoutInflater,
        container: ViewGroup?,
        savedInstanceState: Bundle?
    ): View? {
        return ComposeView(requireContext()).apply {
            setContent {

            BackHandler {
                    // not called when back press
                   someAction()
            }
        }

Is having janky frames normal with Jetpack Compose? I build two test apps, one in Compose and one in XML with a TabLayout + HorizontalPager and a GridView with 3 Columns. I recorded the stacktrace of both apps and uploaded it to Perfetto. The one with many janky frames is jetpack compose. The lags appear while swiping through the HorizontalPager, scrolling through the LazyVerticalGrid is working fine. I think I either have to stop using HorizontalPager + LazyVerticalGrid or switch back to XML. Any ideas what could cause this many janky frames? Code is in Thread ->