Any suggestions on how I could farther make this animation nicer?

if (targetState == SettingsDestination.Main) {
    slideInHorizontally { width -> -width } + fadeIn() with fadeOut()
} else {
    slideInHorizontally { width -> width } + fadeIn() with fadeOut()
}

Hi! I am using Material design extended icons in my android app developed with Jetpack Compose. However, I do not see a way to adjust their weight/grade/boldness. Can someone please help me with this? Thanks!

Hey, I’m looking for a Button with a CircularProgressIndicator inside of it.. The indicator would hide/show based on some loading state, and the buttons width might animate accordingly. I’m sure I found a really good example of this online somewhere, but I’ve lost it. Has anyone got an example, to save me re-implementing this?

I am using a BoxWithConstraints inside it a LazyVerticalGrid where the number of items is dynamic based on the available space. My problem is it is drawing items but in cases where my device is a tablet or foldable, it isn't using the maximum available width in the last row of items. Any guess??

Hi, I'm new to the compose. Actually I'm migrating my application to compose. I have custom widgets in my project which use properties in a map written in room database. When activity is created, I fetch properties of a widget from database and I pass properties in a map to widget and widget is created. Everything works. Now, I have converted my custom widget to composable and I'm must use same old properties technique. But I'm stuck like how should I handle properties for a composeable. Should I just pass entire map to composeable that could include more than 100 properties?? Also, how should I handle states or in other words how should I create states out of map and hoist them outside composeable because widget behavior is changeable from outside. Any suggestions would be highly appreciated.

Hello, I have been using compose for sometime now however I have come to the realisation that i need "futher education" what would be really useful if I could "test drive" some sample apps that "Do" compose properly especially apps that make real network and database calls with List and Detail screens i am currently having difficulty in "Thinking In Compose"!!! any suggestions are more than welcome 😄

Hi all, id like a sanity check on an architectural decision our team has made with structuring compose. Code in replies

Perhaps a starter's question: Our compose application depends on a legacy library function which needs a android.graphics.BitMap as input parameter. This BitMap is just a text with a background color. The question is how we can create a BitMap object using the Text composable?

Hello! What is the best practice to deal with modifier chain creation for each recomposition? Remember? Or there are any compiler optimizations?

Hello peeps. What android studio version you are using with compose. Whenever I change anything in my composable it crash app and after few reload i need to kill emulator and start it again . Really painful. This is my android studio version

Hello! Now that Jetpack compose is in the stable state, is it fine to use jetpack compose in hybrid mode (combination of xml + jetpack ) on production in business critical apps? Has anyone done this already? Pardon me if this has already been discussed on this channel, I was not able to find the thread.

In Compose performance article there is suggestion to defer state reads using lambdas. Why not to pass State and defer call to State.value?

Is this a bug? I have a

ComposeView

(

match_parent

width and height) inside a

FrameLayout

. I’m using this

ComposeView

as a place to show Compose Snackbars (and some other overlays) right now but the

ComposeView

doesn’t allow

Talkback

interactions with anything below it, even when no content is set inside it.

How can i have a child element in Box Composable, which has only the 1/4 size of the Box Composable? Is it possible to get the width and height of a composable?

I am trying to build an interactive screen that have a lot of reusable composables that fly on the screen with random offset. Video in thread 🧵 . Currently it works with

mutableStateListOf

where I am adding new items on each click. Then I call list.onEach { } to render new composable. I feel like this solution is not ideal, cause the list teorytically may have ♾️ elements. I tried to delete the items when animatino ends, but that is causing the view to recompose with some elements “inProgress” and introduce a lot of glitches. What is the proper way to fire these emojis?

I’ve an

IconButton

in a list item of a

LazyColumn

to which I pass

Icon

in two ways: 1. using

painterResource()

with my in app Image drawables (vector)

Icon(
    modifier = Modifier.size(16.dp),
    painter = painterResource(
        id = if (isLiked) R.drawable.ic_like_filled else R.drawable.ic_like
    ),
    contentDescription = null,
    tint = if (isLiked) AppTheme.colors.selected else AppTheme.colors.unselected
)

This leads to Recomposition of Icon. 2. using

imageVector

with MaterialIcons

Icon(
    modifier = Modifier.size(16.dp),
    imageVector = if (isLiked) Icons.Rounded.Favorite else Icons.Rounded.FavoriteBorder,
    contentDescription = null,
    tint = if (isLiked) AppTheme.colors.selected else AppTheme.colors.unselected
)

This skips Recomposition of Icon. Internally both seem to using

rememberVectorPainter()

and I’m failing to see why

painterResource

internal implementation can cause a Recomposition. Am I missing something here? 🤔 (Attaching the recomposition counter screenshots for reference. Attached in order of the above cases)

This message was deleted.

I want to show an

AlertDialog

on a specific action and I'm thinking in tow ways: 1- Pass the action to the root Composable fun then show the dialog. 2- Show the dialog from the Composable that manage the action and then pass the result to the root Composable? I tend to the first option since it's more manageable, what do you think?

Is there a way to have early-return behavior in composables from sub-functions without using exceptions? In standard Kotlin, we can use exceptions for early return:

// this is not idiomatic, just an extremely simplified example
fun foo(bar: String): Int {
    val int = bar.toIntOrNull()
    requireNotNull(int) { "Early return here" }
    return int
}

Using Arrow, the

either

comprehension enables similar features:

fun foo(bar: String): Either<String, Int> {
    val int = bar.toIntOrNull()
    ensureNotNull(int) { "Early return here" }
    return int
}

Using Flows, similar behavior can be emulated using

catch

:

fun foo(bar: Stirng): Flow<Result> = flow {
    val int = bar.toIntOrNull()
    requireNotNull(int) { "Early return here" }
    emit(Result.success(int))
}.catch {
    if (it !is IllegalArgumentException) throw it

    emit(Result.failure(it))
}

Which brings it to my question: what is the equivalent with

@Composable

functions?

Using

AnnotatedString

with `SpanStyle`'s defining large font sizes the space between lines becomes smaller and smaller. It seems to be fine until font sizes larger then 24 sp. Anyone noticed this too? What could be wrong?

teams

Hi is there a "Better" way to handle multiple compose navigation destinations when passing "Down to Lowever levels"?

I have seen numerous posts in this channel about handling your own config changes in a Compose app/activity, but I feel like I must be missing something. I am using a custom design system as described in the official documentation here. When I change the TextSize in accessibility settings or change the theme by using

AppCompatDelegate.setDefaultNightMode

I can see that

onConfigurationChanged

is called in the Activity, but nothing automatically changes in my composables. Is there more setup needed that I have missed in a thread?

Hii, I want to center align last item if it is single item in LazyVerticalGrid. Is that possible using LazyVerticalGrid or i need to use custom layout?

Hey 👋 Kinda noob question, but I am a bit confused about this one. Why does

rememberSaveable

could store a list of instances, but not an instance alone? Code in the 🧵

I'm trying to create a

SnapLayoutInfoProvider

for a

ScrollState

(used by a

Pager

composable, where all the items have

fillMaxSize

), but I don't really get what

calculateSnappingOffsetBounds

is expected to return. I don't understand the doc either. I mean, shouldn't an offset be enough (i.e. the new `ScrollState`'s

value

)?

Any Compose Desktop folks in this channel?

Non-Desktop specific Compose comment: A Table composable would be amazing

I could be mistaken but I believe compose doesn’t offer a “native/default” functionality like this. Is there any “accompanist” lib do help us with this kind of “fast seek”? If not, what’s you favourite lib to achieve it?

This question has come up on this slack a lot, so posting this thread here for reference. https://twitter.com/zachklipp/status/1583165356322930688?s=20&t=571G9Tb_dtjeHKrYKNb3JA