Hello is there a configuration for handle Landscape and Portrait UI in compose

Has anyone had success when using

SaveableStateHolder.SaveableStateProvider()

and

AnimatedContent

together? Whenever I try, the ui-state just seems to be lost after navigation; e.g. I can navigate between screens A/B/C while they keep their individual scroll-positions, but as soon as animated content enters the picture the scroll-positions are reset on each navigation. Id love to understand why this happens, if theres a way to work with it, or if I should just use

Animatable

and do the work myself?

I want to add a slideIn and slideOut animation on a

Image

, but I want the animation state of the slideIn/Out to be driven by the scrollState of my Column. Is there any way to hook those up to each other?

Does anyone know if 1.1.0 is going to be released at any point in the near future? What is Googles release cycle? Is 1.1.0-alpha02 a safe version to migrate to (like it is with fragmentx for example)?

Are there any potential flaws with using

DisposableEffect

to handle tracking screen views? Seems it’s a pretty good fit to know when a Composable is shown on screen and then knows when it leaves the screen as well It’s not really a operation that needs cleaning up though, so maybe doesn’t fit the typical use case of

DisposableEffect

Myself and @Nathan Castlehow at Vitruvian recently had the opportunity to rewrite our react native app entirely in compose. It took us about 6 months, and we’ve seen dramatic improvements in all areas. We couldn’t be happier with the decision to choose compose, huge thanks to the team and community! We’d love if you checked it out 😉

Is there a way to get proper hyphenation in compose?

Is there a way to show preview of the left and right pages of a fixed size with accompanist

Pager

without parent measuring with BoxWithConstraints/SubcomposeLayout?

Been searching for a while, is there a way to extract text from resource id in compose while testing it? All the matchers expect text as string

Hi! Do you know if it’s possible to change the size of the

CheckBox

. I’m taking a look on the internal implementation and it defines his size as a private val

private val CheckboxSize = 20.dp

. I don’t know why some Framework components are not be able to change their size. Same for the padding, it has an internal padding

private val CheckboxDefaultPadding = 2.dp

and I can’t figure out how to get rid of it.

Consider a Composable function with Logger at very first line. If I see the logs few times or dozens, is that means my Composable is recreated that amount ? Or simple Log.d() is not sufficient to judge that?

Hi, can I set a Spanned to Text( ) ?

How anal is it to use state hoisting? My screen params are starting to build up a lot of `OnClick() -> Unit`’s . Is it preferred that I pass the viewmodel around at this point? I was trying to avoid that because then I can’t preview the screen at all.

Okay I am sure this has been asked before in some form, but I am still being confused about how to properly collect flows from a VM inside my composables. More in Thread 🧵

Is there any setting or similar in compose to show rerenders visually like they have in flutter? https://flutter.dev/docs/development/tools/devtools/inspector#highlight-repaints

Hi guys, I'm fighting with a problem that seems trivial. Currently I have a

Button

that contains a

Column

(that contains other stuff), but I want that this column fills the remaining space inside the

Button

, basically I want that the column fit all the space inside the Button. In the old world I was used to put

match_parent

width.

.fillMaxWidth()

doesn't work well because in this way the buttons fills all witdh space in my composable. Any ideas?

Is there an easy way to call a function just when the screen is opened? 🤔 Detailed explanation: Using Navigation, I’m opening

ScreenA

which I’m using

LaunchEffect(viewModel) {
    viewModel.loadSomeData()
}

In this screen, somewhere in the future I call

ScreenB

. But when I go back to

ScreenA

, the

loadSomeData()

is called again… Is there a way to avoid that?

I've implemented bottom bar in compose. When I click on bottom bar item once, it navigate to that section, but if I click on it again, it's not showing that section. What am I missing here? (code is in thread)

Is there a preference between providing

Text

its

color

via a

TextStyle

(esp when using a

TextStyle

is coming from a

Theme.typography

), vs via the

color

parameter? i.e.

Text(style = MyTheme.typography.title.copy(color = #123456))

VS

Text(style = MyTheme.typography.title, color = #123456)

trying to choose the “best” approach in this case

Can someone explain to me why after upgrading to compose stable this code would fire the sideeffect twice after launching the app

SideEffect {
        viewModel.getPlatforms()
    }

In other words viewModel.getPlatforms fires twice where as it didn’t use to be the case before. Perhaps I was misusing the api before

Is there any performance improvement/benefit in using `lazy Column`/`Row` vs `verticalScroll`/`horizontalScroll` if there are only 5 to 10 items to show? but items will recompose multiple times.

How do you handle text capitalization in Button()? The text gets automatically styled with Typography.button as far as I understood but it doesn't seem to be actually capitalizing it.

Is there any example code on how to use the google sign in button in jetpack compose? Or do I need to wrap the google sign in button in an android view?

How do I use onActivityResult if FB's SDK is eating the intent and I cant use

rememberLauncherForActivityResult

because there's no intent to send into the launcher

Is there any way to write a compose test to check for certain behavior when a composition fails? E.g. logic in

RememberObserver.onAbandoned()

Is there a way to run a callback when a composable is finished animating it's transition in? In my use case I have a BottomSheetScaffold with a constant peekheight. However, when We use an animation, to navigate to the screen, it looks off as the bottom sheet slides towards the bottom nav bar, with a visible gap to begin with in between. I would like to show the sheet after the transition is done animating in.

Does anyone know how fragments work in jetpack compose? the documentation has a bunch of holes in its examples https://developer.android.com/jetpack/compose/interop/interop-apis#compose-in-fragments.

I have a bottom sheet. When collapsed the padding on top of the text is perfect (according to my designer), but when it's fully expanded, we want to add extra padding so that the text is pushed down. We want the bottom sheet to go all the way up because that's what our designer wants in our edge to edge application.

Is there any way to get the

size

of the screen as a value? I thought it would be available in

LocalDensity.current

but it isn't.

I need to pass activity to

Composable

for billing stuff like the code bellow

@Composable
internal fun BillingScreen(activity: Activity, billingClient: BillingClient)

is this a bad idea?