I've run some more tests on Pager performance and if I haven't messed up the test itself, it seems that original ViewPager is still quite a bit ahead when it comes to performance (which is understandable given how young it is, but still, good to know). More details in thread.

What is the best approach to apply transition animation when switching between screens ?!

Hello during our implementation we notice a bug on

Scaffold(
    bottomBar = ...

When one of BottomNavigationItem's Layout contains NavHost it's crash when you select this BottomNavigationItem once and then the same item second time

I've got a HorizontalPager from Accompanist and 2 pages both with an ExoPlayer view. When I set the ExoPlayer to resizeMode=RESIZE_MODE_ZOOM, the video zooms correctly, but somehow the surfaces of the video overlap. What would be the correct way to fix this? Somehow clipping it? (Modifier.clipToBounds didn't work) Change from SurfaceView to TextureView?

Hi guys! Silly question here 🙋‍♂️ I want to make my lineal icons line thickness customizable. There are two possibilities: 1. Craft the icons "by code" using

Canvas

: compose-like approach, very customizable solution but it will be a pain for complex icons (this is what I'm currently doing) 2. Ship N drawables with different line thickness: not very customizable, increases app size, feels like a waste 3. ???

Hi everyone! Can anyone explain why this is happening? This doesn’t happen when using views only. Could this be a bug in compose? Code in 🧵

Hello guys, i'm using

mutableListOf<Int>

to track my calendar days which are selected in a period of time and then fill the square Grey. When I select a new period of time, I first empty the mutableListOf and later I save on it my new days in order to react and show the Grey square animation. The problem is that when I empty the mutableListOf and quickly select a new period of time, as you see in the beginning of the video, it seems that the mutableList has my old dates on cache? and then only the new days added to the period of time react to the change (the old dates animation doesn't trigger, you just see the square filled). However if I select a new date, and wait some seconds to select the endDay, my animation is triggered in all the days, because the mutableListOf doesn't have any data saved.

I am trying to use

paging-compose

for creating a grid and I found out that there is no

items

function for

LazyGridScope

that accepts

lazyPagingItems: LazyPagingItems<T>

as there is one for

LazyListScope

Basically I'm not able to use pagination for creating a grid view. Is there any workaround for it?

How I can add the Up button on Navigation Compose in the Detail View?

Is it acceptable to add like 50-100 (and possibly even more) destinations to a

NavGraph

? I can pass the

id

in a route but it would be great if I could do something like this:

SampleCategory.Buttons.samples.forEach { sample ->
    composable(sample.id) {
        sample.content()
    }
}

I want to have a list in my ViewModel that tracks what checkboxes the user selected. I saw this post which shows my approach is wrong https://github.com/Kotlin/kotlinx.coroutines/issues/2516, but what would be the correct approach? See thread for more info

So I asked a question on SO here about why the

composable

for a route was being recomposed whenever the state inside my HiltViewModel changed. After thinking through it a bit I think I know the answer but wanted some confirmation before updating the post. I’ll put what I think is going on in the thread.

I would like to apply a draw transform to a wrapped

IndicationInstance

, but

ContentDrawScope

doesn't allow for that.

I’ve been trying for a long time to get exoplayer working in a LazyColumn, but I can’t get it to work without a lot of jankiness. I’ve created a minimum sample on github, link in thread.

The y position of the composable changes when the state that is used for changing the shape or color of the composable gets updated.

@cb can we expect a drag n drop or reorder feature in

flowlayout

anytime soon?

has anyone tried compose (beta-08) with kotlin 1.5.20-RC?

I am trying to setup an animation for the search view here. The behavior should be, as soon as the user hit the search bar it should collapse and move to the top right next to the back button*(Screen 2)* and if I hit the back button it should return to the previous position in expanded form*(Screen 1)*.

There's no text "linkify" in compose right? I have a

Text

that contains an email and I want to just make it clickable. Do I have to basically just set up something like this or is there something simpler that I'm missing?

Is there any easy way to hide bottom sheet completely not just half collapse?

Has anyone implemented a tinder-like interface? Essentially a stack of cards thats swipeable? Going to attempt to build something myself, but curious if there is some kind of good starting off point.

What would be the correct way of passing a default value to a ViewModel inside a composable, one that can be accessed inside its

init

function? Context in thread

How to make step by step wizard in compose ? Is there any example code ?

I verified a different recomposition behavior between

1.0.0-beta07

and

1.0.0-beta08

This is the code:

LazyColumn {
    stickyHeader {
        CountriesListHeader()
    }
    items(items = countriesListState.countriesListItems, itemContent = { item ->
        CountriesListRow(
            item = item,
            favorite = countriesListState.favoriteCountries.containsKey(item.name)
    })
}

In case

countriesListItems

hasn’t changed but

favoriteCountries

has changed: • in beta07,

items

recompose (and that’s what I would expect, as in

CountriesListRow

the

favorite

parameter depends on

favoriteCountries

) • in beta08,

items

don’t recompose, as it seems Compose is just monitoring changes of

countriesListItems

and not

favoriteCountries

Is this a bug, or I should structure my code differently?

Is it somehow possible to interact with the child composables of Scaffold? I find it very unflexible. For example on scroll I want change the elevation of the appbar. (so that it has 0dp and the default elevation on scroll)

I'm a bit confused with the magic of compose regarding LocalContentAlpha. Generally our development workflow is that the designers build screens and define colors for each text. But now lots of prebuild composables change the LocalContentAlpha which leads to the situation that text colors are always different from what our designers intended. This usually leads to QA reviews like: "Can you check the text color of component a, b and c? It's different from what's in the ardboard". The only way around that I found so far is to always wrap everything in another

CompositionLocalProvider(LocalContentAlpha provides ContentAlpha.high)

. But that's a lot of overhead and it feels like working against the system.

Has anyone noticed gradients not quite working correctly on older API levels? Here's a gradient that uses

Color.Transparent

on API 23 and API 27

Just another compose thing 😉 🎉 https://twitter.com/theapache64/status/1403995465113169923