I have a design system that is not like Material at all EXCEPT for the "card" pattern. We want to keep cards and especially their properties for dark theme (where elevation gets converted to brightness)> Anyway. What do you all recommend? Not using Material dependency at all? Copy pasting the card code into my app directly. Or including material dep, and just using a Material card?

This message was deleted.

What's equivalent of SwiftUI's

GeometryReader

for getting the dimensions of the screen/window?

Hello! Happy New Year! The latest Jetpack Compose minor release, alpha10, is here! You can get it now from Google’s Maven Repository. Release notes are available at https://developer.android.com/jetpack/androidx/versions/all-channel. Please log issues at https://issuetracker.google.com/issues/new?component=612128.

So.. I was wondering... How to modularize (gradle modules) with compose? Since we can't deeplink a function. How to keep features isolated, but still be able to launch a composable that I don't have a direct access to?

Updating to alpha10…

@Deprecated(
    "offsetPx was deprecated. Please use offset with lambda parameters instead.",
    ReplaceWith(
        "offset({x.value}, {y.value})",
        "androidx.compose.foundation.layout.offset",
        "kotlin.math.roundToInt()"
    )
)

I can’t find this replacement function 🤔

I’m getting this lint

@Composable properties should be declared with the @Composable annotation on the getter, and not the property itself.

But it won’t let me do it. What’s the right way?

Note: Modifiers can play a similar role to XML attributes in the View system, but the type safety of scope-specific modifiers helps you to discover and understand what is available and applicable to a certain layout. Compare this with XML layouts where it was not always clear if a layout attribute was applicable to a given View.

This is copied from the Jetpack Compose Codelab "Layouts in Jetpack Compose". But it's not true as far as I know, because xml layouts does have the ability to tell if a layout attribute is applicable to a given View. Am I wrong or have I misunderstood what the doc says? Source: https://developer.android.com/codelabs/jetpack-compose-layouts?continue=https%3A%2F%2Fd[…]developer.android.com%2Fcodelabs%2Fjetpack-compose-layouts

Trying out LazyVerticalGrid. Seems to work great however I’m not able to easily add a row at the end to display a loader for infinite scroll since I can only add grid-cells with the available API.

One of my AndroidViews are re-inflating on alpha10 on every recompose. I’m curious what causes a reinflate for an AndroidView. Can anyone help shed light on this? The documentation says it should only run exactly once.

animate

has been deprecated and should now be

animateAsState

however, there are 2 different top level functions for

T

, and one for

Color

androidx.compose.animation.animateAsState

(Color)

androidx.compose.animation.core.animateAsState

(T) Is that intended?

is there a way to remember a layout height in compose? Use-case: • I have some Box positioned in the screen (it's inside the Column) • User hits some button, some job begins • Now I want to hide the box and show a CircularIndicator positioned at that (now invisible) Box's center In code I do something like

if (isJobRunning) Box() else CircularIndicator()

but that makes progress bar jump. In old View system I would wrap them both in FrameLayout and have the indicator use

layout_gravity=center

while setting

box.visibility = INVISIBLE

. What path should I take in Compose?

Is it ok that

onSizeChanged

reports size without padding?

@Preview
@Composable
fun Test() {
    val density = AmbientDensity.current
    Box(
        modifier = Modifier
            .padding(with(density) { 50.toDp() })
            .size(with(density) { 50.toDp() })
            .background(Color.Red)
            .onSizeChanged { println(it) }
    )
}

I expect this to print

150 x 150

, but get

50 x 50

instead.

Hi! Any blog post, tutorial, anything... about compose animations, for dummies, given that I even not do animations on old android?

Hi! How to solve this error on composable preview? compose:alpha10, ui-tooling:alpha07

java.lang.NoSuchMethodError: 'androidx.compose.runtime.SlotTable androidx.compose.runtime.Composer.getSlotTable()'   at androidx.ui.tooling.InspectableKt.Inspectable(Inspectable.kt:63)   at androidx.ui.tooling.preview.ComposeViewAdapter$WrapPreview$1.invoke(ComposeViewAdapter.kt:357)   at androidx.ui.tooling.preview.ComposeViewAdapter$WrapPreview$1.invoke(ComposeViewAdapter.kt:-1)   at androidx.compose.runtime.internal.ComposableLambda.invoke(ComposableLambda.kt:146)   at androidx.compose.runtime.internal.ComposableLambda.invoke(ComposableLambda.kt:-1)   at androidx.compose.runtime.AmbientKt.Providers(Ambient.kt:188)   at androidx.ui.tooling.preview.ComposeViewAdapter.WrapPreview(ComposeViewAdapter.kt:356)   at androidx.ui.tooling.preview.ComposeViewAdapter.access$WrapPreview(ComposeViewAdapter.kt:-1)   at androidx.ui.tooling.preview.ComposeViewAdapter$init$1.invoke(ComposeViewAdapter.kt:397)   at androidx.ui.tooling.preview.ComposeViewAdapter$init$1.invoke(ComposeViewAdapter.kt:-1)   at androidx.compose.runtime.internal.ComposableLambda.invoke(ComposableLambda.kt:146)   at androidx.compose.runtime.internal.ComposableLambda.invoke(ComposableLambda.kt:-1)   at androidx.compose.runtime.AmbientKt.Providers(Ambient.kt:188)   at androidx.compose.ui.platform.AmbientsKt.ProvideCommonAmbients(Ambients.kt:274)   at

Is it possible to create an Icon composable with a Resource ID? If not, what's the best way to do it with a vector drawable?

How can I hide the TopAppBar when scrolling a LazyList like I would typically do with a CoordinatorLayout?

Is it possible to pass a value from a BroadcastReceiver to a Composable? If so, how? If I use an intent and putExtra, my Composable is not in an Activity so I'm stuck. 🤔

👋 As per https://twitter.com/chrisbanes/status/1349985729871552512?s=21 Chris is hinting that in alpha09 support for nested scrolling has been released. Can anyone name the relative APIs? :thank-you:

Trying to listen to DrawerState so I could clear focus on its content on close. There is a

confirmStateChange

callback but seems it is only invoked when dismissed with a swipe gesture. A gentle drag, invoking

drawerState.close

, or clicking outside the drawer doesn’t trigger this callback. Makes me think that callback is broken if it’s only valid for a swipe gesture 🤔

I can’t search for compose code in cs.android.com anymore, only samples show up. E.g. if I search “Scaffold.kt”, only scaffold samples appear. Is this a known issue?

Is there difference between passing composable emptyContent VS null ?

@Composable
fun SomeComposable(content : @Composable (() -> Unit)? = null) {}

@Composable
fun OtherComposable(content : @Composable () -> Unit = emptyContent()) {}

Let's say I have such code

@Composable
fun ComposableA() {
  val stateA by savedInstanceState { "id" }

  ComposableB(stateA) // <-- How to drop all subtree state on stateA change?
}

@Composable
fun ComposableB(state: String) {
  val stateB by savedInstanceState { "stateB" }
  
  // deep nested structure with more states
}

I want

ComposebleB

to be composed with fresh child states when

stateA

changes. What would be right way to achieve such behavior?

Are there any settings to control the "dimensions" of @Previews that are rendered?

hello fellow composers, question about state keeping. I have two tabs. Only one of them is visible at given time, hence when

tabA

is visible

tabB

is not in composition tree. My problem is that when I switch between them state is not remembered, for example scroll state. How can I tell to compose to remember this discarded tab, that it can be needed soon? (sample code in thread)

is it an practical example of theming in compose? The material theme class is enough? or should I make my own theme class?

Is there already a FloatingActionMenu somewhere? https://github.com/Clans/FloatingActionButton

Hi there, I'm working on migrating an existing app to Compose. We're using viewBinding to wrap our existing design components which works fairly well except in terms of accessibility. I've seen some documentation on using semantics, but not on how to use them properly with custom design elements. If anyone can point me to an article, example or other docs on this I would really appreciate it.

Typing into a text field in a lazy column is laggy (even in the state codelab where it does this) Is that an issue or is there something we can do to fix this?