Whats the best way to put compose into a vertically scrolling tab driven via

FragmentStateAdapter

/

CoordinatorLayout

w/

NestedScrollView

? Do we need to wrap it in some scrollable parent or should LazyColumn be sufficient?

Hi, Are there any samples for creating idlingresources? What is the replacement of countingidling resources from espresso. Thanks

[SOLVED} How do I set inside Scaffold • bottomAppBar + FAB As they are Overlapping or even better (FAB insert into bottomBar)

Compose's dark theme doesn't affect the status bar, right? How to work around this?

Hi all. Someone can explain me why lazy column slow and skipping frames and when it will be fixed? 🙂

Consider the `FancyTextField`:

@Composable
fun FancyTextField(value: String, onValueChange: (String) -> Unit, modifier: Modifier = Modifier) {
    Column(modifier) {
        TextField(value, onValueChange)
        Text("fancy!")
    }
}

While looking innocent, this code breaks the passed modifiers. If I pass for example

Modifier.fillMaxWidth()

, then only the

Column

will have expanded width, and the

TextField

will stay the same size, meaning that

fillMaxWidth

will not make

FancyTextField

fill max width (in practice). Obviously passing a modifier to

TextFIeld

(instead or in addition) won't work well. So how should

FancyTextField

be declared in such a way that modifiers work as expected?

Even tho I read the documentation, I can't wrap my head around why we need to use

SideEffect

here. The functionality works without the

SideEffect

call. Can someone tell me why we need it? https://google.github.io/accompanist/systemuicontroller/

To get Compose preview to work I need this dependency:

implementation "androidx.compose.ui:ui-tooling:$compose_version"

But then that means that library will increase the size of my production build. Is there a way around this?

This message was deleted.

Layout Inspector bug? I have an App that starts out using UIView XML layouts, and later navigates to Compose defined screens. Layout inspector works on startup, but as soon as we navigate to the Compose screen, it shows the screen but the Component Tree is blank and no elements are clickable i.e. the inspector breaks. Using

1.0.1

and

ui-tooling

etc. same on Device / Emulator 🤷. Not even sure if the UIView/Compose mix is significant... inspector just plain doesn't work on Compose. Documentation says it should?

Why is not NavController a local? I'd love to use ~ findNavController() instead of creating callbacks for every action/or passing the NavController down.

Is it possible to properly use the SplashScreen compat library (https://developer.android.com/about/versions/12/splash-screen-migration#splashscreen_compat_library) with Jetpack Compose? According to the examples, I would use it like so:

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        installSplashScreen()

        setContent {
            // ...
        }
    }
}

However,

setContent

replaces the root view when it finishes loading, so any custom splash screen animation will not play. Is there a better alternative?

Hi! Is there an option on

TextField

to prevent showing soft input similar to

showSoftInputOnFocus

on

EditText

?

Is there a way to use

collectAsState()

(or an equivalent) inside of a

LazyListScope

(outside of a

@Composable

)? The usecase is conditionally emitting either A or B items, depending on the content of a

StateFlow

And another question: I implemented the shown navigation transition by having a upper nav host and a lower nav host. The lower nav host is wrapped inside a scaffold, which is a composable in the upper nav host. I know that it is always recommended to not use nested nav hosts and instead conditionally show the top and bottom bar in the scaffold. However, I want this specific transition, which scales in the second screen above the top and bottom bar of the first screen. As far as I'm concerned, this is not possible by using a single nav host inside a scaffold. Am I wrong / is there an alternative?

Does anybody develop cross platform native apps, KMM for example? Is there compose

remember

analog in SwiftUI?

Hi folks, is there a substitute for

ViewTreeObserver.OnPreDrawListener

in Compose? Looking for a way to delay startup due to data initialization. Was looking on https://developer.android.com/about/versions/12/features/splash-screen but can’t connect it with compose.

Hi! I’m trying to replicate merging semantics information of a component’s children from the testing tutorial, but I’m running into different results than the tutorial. 🧵

Is it possible to override a child composables onclick & ripple effect if its a button? In my scenario, a button is placed at the bottom of a card with padding around it; Id like the clickable area to cover the entire width of the card (similar to what could be acheived by specifying

selectableItemBackground

on the parent rather than child view in XML). If I specify a clickable composable around the button, the button will still grab focus (even if I mute its ripple effect through

Modifier.clickable

). I can acheive it by using a

Text

instead of

Button

since it wouldnt be clickable, but then Id have to continiously mimic the button style exactly in the text composable.

I imagine there are cases in which impossible constraints are specified to a

ConstraintLayout

. Will

ConstraintLayout

throw an exception in that case? Or just try to make do, ignore some constraints, etc? I'm facing a case in which I have a slightly complicated layout, and it seems like some constraints i'm specifying are being ignored

How do I load images from device storage using coil?

rememberImagePainter

always returns empty state when I pass a content Uri to

data

Is there any rule of thumb when to bundle multiple single states of a

ViewModel

into one state object (e.g.

data class ViewState(..)

)? In my opinion both have advantages and disadvantages. Exposing multiple states from VM keeps changes to the UI more granular but it's more cumbersome to keep track of every single state. On the other hand, exposing just one bigger state object has better maintenance because you always have to deal with just one state in your UI but in contrast when one of the fields changes, a new object is created. Imagine you have following state object:

data class MyScreenState(
    val isLoaded: Boolean,
    val items: List<SomeType>,
    val sortedItems: List<SomeType>,
    val recommendedItems: List<SomeType>,
)

While

isLoaded

might changes quite frequently, the other fields do not and this yields to a massive unbalanced object creation. So I'm wondering if there is any rule of thumb when to use which approach?

Survey: How long have you been leveraging Jetpack Compose for user-facing features in your Android production apps? follow up question, were there any gotchas / surprises in the wild that you encountered?

What's the consensus on providing your uiState via

CompositionLocalProvider

to other composables from your main composable? I assume this would be good for composables that you don't plan on re-using and are coupled tightly to that uiState. Rather than passing in my uiState to every composable that needs it. Or is this already a smell because each composable should only have things passed into it it needs? I've thought about this when let's say composable B needs to send data to composable C from composable A (from the uiState) and rather than pass in 8 things to composable B, I'd rather pass in a uiState so I have access to everything I need. (If a composable only needs 1-2 things then it makes sense to only pass those, but for composable dependencies that need 7-8 fields does this make sense to do?)

What is the reason to not update the UI if you use Room directly with Compose:

dao.get().collectAsState(emptyList())

with

interface Dao { @Query(...) fun get(): Flow }

? You have to use a ViewModel to get updates on DB changes. WA: wrap the

collect

in VM and emit them to the flow accessed by Compose...

Anyone know of any tutorials for managing TopAppBar actions with the nav controller? In the past, we set the supportActionBar and then within each fragment inflated a menu. I’m curious what the equivalent process would be for compose. (short of maintaining one huge view model with flags for when to enable each menu item)

This is the only way I could figure out how to tile a background image loaded by Coil. 🤔 Any thoughts on making this better/more correct?

var tiledBackgroundImageShader by remember { mutableStateOf<ShaderBrush?>(null) }
    val imageLoader = LocalImageLoader.current
    val localContext = LocalContext.current
    LaunchedEffect(backgroundImageSrc) {
        val builder = ImageRequest.Builder(localContext).data(backgroundImageSrc)
        val result = imageLoader.execute(builder.build()).drawable?.toBitmap()
        if (result != null) {
            val shader = ImageShader(result.asImageBitmap(), tileModeX = TileMode.Repeated, tileModeY = TileMode.Repeated)
            tiledBackgroundImageShader = ShaderBrush(shader)
        }
    }

and for the content:

Box(
        modifier = Modifier
            .drawWithCache {
                onDrawBehind {
                    drawRect(backgroundColor)
                    tiledBackgroundImageShader?.let { drawRect(it) }
                }
            }
    ) {

This message was deleted.

Has anyone successfully performed Compose UI tests on the content of a

ComposeView

within a traditional

View

hierarchy? Any examples of this?