Heads up, folks, dev11 is temporarily delayed while we work out a build system/gradle plugin issue that was producing artifacts with missing kotlin metadata. More as it develops and we're working to get it out ASAP.

What’s the easiest way to bottom align something

Box(
    modifier = Modifier.fillMaxSize(),
    gravity = Alignment.BottomEnd
) {
    Column(modifier = Modifier.fillMaxHeight()) {
        ....
    }
    val icon = vectorResource(id = R.drawable.ic_home)
    FloatingActionButton(
        onClick = {
        }, modifier = Modifier.padding(20.dp)
    ) {
        Image(asset = icon, modifier = Modifier.preferredSize(24.dp))
    }
}

Is there a better way than the above?

Because the AdapterList is not working correctly for now. I implemented my own custom list. I think the performance is more or less similar but it do not crash so often and it calls onDispose when a item is not visible any more. And also for me it is impressive that it is possible to implement a AdapterList in 60 lines of code.

I’ve created a custom theme by creating a color palette

val themeColors = lightColorPalette(
    primary = Color(0xFF092432),
    primaryVariant = Color(0xFF092432),
    secondary = Color(0xFF3DDB85)
)

And initialised the same like this

MaterialTheme(colors = themeColors) {
// children
}

Now if I access colors using

MaterialTheme.colors

, I’m able to get custom colors in all composables except for

Dialog

In

Dialog

, the colours reset to default values. Is this a known issue?

Is the dependency

"androidx.ui:ui-framework"

excluded from compose?

What are yall's thoughts on making composable functions to render a specific type: 1️⃣

DrawFoo(myFoo)

2️⃣

myFoo.draw()

Both functions are composable and do the same thing. Worded another way, when is it appropriate/idiomatic to create a composable extension function?

Is there any particular reason in some contexts the term “widget” is chosen over “component”? The framework, compose and Flutter for that matter, seem to have made this decision, and I wonder if I’m missing something or if it’s just general preference

1. The actual version of compose is just to have feedback from people playing with it, but it´s not expected to be enough to build a full app right? 2. Is someone trying to create a "real app" with compose and trying to have a polished view?. And in that case what are the thoughts about it?

It could be enough, it depends on your needs but APIs may (will?) change drastically and you may (will?) run into stability/performance issues. To us it is not production ready

What is difference between for example: “tagModifier.plus(focusModifier)” and “tagModifier + focusModifier”?

Figured I'd post this here too: https://twitter.com/chrisbanes/status/1261279161735208960 The MDC interop is especially useful as you migrate existing apps over

Hello everyone, Someone knows how to solve this preview problem??

A jetpack compose shimmer effect modifier library https://github.com/kazemihabib/compose-shimmer

Wondering if there is a notion of “scaling” a composable. Like if I increase the display size or scale of my android device, how does compose honor that? Moreover, if I want to do that at an individual composable level, what’s the best way to do it?

What's the plan regarding try/catch with compose? I really want my parent components to be able to catch and handle certain exceptions from children

Is there a way to draw rotated text? The Canvas API has no drawText

For ConstraintLayout, it seems percent(100f) refers to 100x the size of the parent? I reckon it should be renamed or changed a bit, since "percent" means "per one hundred"

Done the swipe action using the snippet

val modifier = Modifier.rawDragGestureFilter(dragObserver = object : DragObserver { })

Button( onClick = {
   log()
}) {
Text(text = "Delete")
}

Box( modifier = modifier.drawLayer(
            translationX = itemLeft.value
        )
) {
}

Button click not working !!! translationX not moving the actual UI coordinates !?

I've been using

OwnerAmbient

to get access to the root View for inflating nested Android views further down in the composition. The inflation is being done by another library, so I can't use the

AndroidView(Int)

composable. However,

OwnerAmbient

is deprecated. Is there (or will there be) another API for getting access to the View hosting a composition?

I noticed that in dev11 there was cleanup in the

ContextDrawScope

and

clipRRect

was removed from it. What’s the alternative if I want to clip a rect with rounded corners?

I've seen the word

subcomposition

multiple times in slack, what does it mean?

How should touch drag gesture consumption work? I have following problem. I do have e.g.: A scrollable list and each element can be swiped. The problem now is that both gestures are detected at the same time. But i want to stop detecting the swipe gesture when the user is scrolling and vice versa. Here is a sample (A little bit simplified just using Vertical/HorizontalScroller to demonstrate the problem:

VerticalScroller() {
    Column(Modifier.padding(10.dp)) {
        for (i in 0..50) {
            Box(backgroundColor = if (i % 2 == 0) Color.LightGray else Color.Gray) {
                HorizontalScroller(()) {
                    Row {
                        for (j in 0..10) {
                            Text("i: $i element $j", Modifier.padding(20.dp))
                        }
                    }
                }
            }
        }
    }
}

Anyone have any ideas why during build I get an error related to SurfaceView unresolved reference:

@Composable
fun buildUi() {
    Column(
        modifier = Modifier.fillMaxSize(),
        horizontalGravity = Alignment.CenterHorizontally
    ) {
        SurfaceView(ContextAmbient.current)
    }
}

Hi! Is there an alternative in Compose Text for TextView's autoSize text scaling?

Hey guys 😄 I’ve been testin Compose and I have a question, how do you draw a shadow into an Image??

Hello, Is it possible to try out compose without android itself? I mean just somehow use only compose core where I can write @Composable functions and somehow run (render) these functions with my own implementation.

Suppose I wanted to draw a loading spinner, but only if a load is taking longer than X milliseconds to complete (to avoid jarring/sudden UI changes for really quick async loads). Once the loading spinner is showing however, I want it to stick around for Y milliseconds before rendering the new data. Is this ux possible in Compose?

Hi folks, I'm writing a project that I download dynamically a font family and store at the device, there is anyway in Compose right now to generate a Font Family from this downloaded Files (Not resource ones) ?

Hey, I need a CoroutineScope that lives as long as the current composition. is this valid?

@Composable
internal fun composeCoroutineScope(
    coroutineContext: CoroutineContext = SupervisorJob() + Dispatchers.Main.immediate
): CoroutineScope {
    val scope = remember { CoroutineScope(coroutineContext) }
    onDispose { scope.cancel() }
    return scope
}