What’s the best way to scope a VM inside a composable? I’ve a Pager with x screen and they all use the same VM, but I need a different instance for each screen. Any ideas?

What is an idiomatic way to write "slot-based" custom layouts? For example I want to have 3 slots:

Layout(content = { leftSlot(); centerSlot(); rightSlot(); }) { measurables, constraints -> ... }

And layout logic is based on the assumption that I'll have 3 measureables: for example I want to always expand

centerSlot

. But I've found that if a

centerSlot()

composable will not emit any UI (return Unit), I'll have

measurables.size == 2

, and also I won't know which one of them is missing. For now I solved this by wrapping each slot in a box (e.g.

Box { leftSlot() }

), but I'm not sure if this is the best way.

Why my

Image

sometimes can't load Uri? This Uri(

<content://xxx>

) can be loaded by

Glide

but can't be loaded by

Coil

. The coil only show white screen. And when they load

android.resource:// xxxx

, both of them can show picture.

I feel like there is a ton of haptic feedback types missing here. Should I just assume this list will be completed in the future and refrain from adding haptic feedback now or am I searching at the wrong place? I’m trying to implement a haptic feedback for switches

Has anyone tried to create a chart in compose?

Hi! I am trying to put Composable views as Markers on Google Maps, but it seems to be a pretty challenging exercise. I used this article to create Bitmaps from Composables, then used an

AndroidView

to be able to render them on the map. It appears that some modifiers are interpreted differently during the transformation and for example `clip`ping is ignored as you can see in the image. (However using the

background

modifier with a

Shape

is working, but it isn't a full solution for the problem.) Did anyone try this before? Any other solution ideas on how to put Composables on Google Maps?

I am trying to drag a small circle around the screen but it seems the

DraggableCircle

is not getting composed with the updated position received from the lambda.

@Composable
fun DraggableSample() {
    Box(
        modifier = Modifier
            .fillMaxSize()
    ) {
        var position by remember { mutableStateOf(IntOffset.Zero) }

        DraggableCircle(position = position, onPositionChanged = { position = it })
    }
}

@Composable
fun DraggableCircle(
    modifier: Modifier = Modifier,
    position: IntOffset,
    onPositionChanged: (position: IntOffset) -> Unit
) {
    Box(
        modifier = modifier
            .offset { position }
            .size(100.dp)
            .background(color = Color.Green, CircleShape)
            .pointerInput(Unit) {
                detectDragGestures { change, dragAmount ->
                    onPositionChanged(dragAmount.toIntOffset + position)
                    change.consumeAllChanges()
                }
            }
    )
}

Hey, I have few doubts about Navigation with Compose (my first time using it) - maybe someone can help me with: 1. Should we reuse the NavController or each NavHost should have one? E.g., a NavHost that internally has a screen with a tab and another NavHost. 2. Is there a way to create a NavGraphBuilder without a NavController? I would like to create one using Dagger + Multibinding and reuse it in 2 NavHost. Thank you in advance.

Compose tests don't work. Error `Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported`` . Do you know how to win?

Until Kotlin makes compiler plugin APIs stable, Compose version is tied to Kotlin version and vice-versa. Traditionally, active development in Jetpack libraries is done in alpha/beta channel, leaving stable channel for bug fixes only. When Compose was in alpha/beta, it had biweekly releases, and support for new Kotlin version was added to Compose in next release or two. I have a concern that latest stable Compose will fall behind the Kotlin version. Will new Kotlin releases be supported in stable channel of Compose in future?

How can I achieve a TextField that’s aligned to the bottom of the screen and floats above the keyboard?

Hi this might be a silly question, but is there something fancy you have to do to make testing in compose work? I have this test (see code in thread) but it looks like it just stalls and then after 45 sek it gives the error

java.lang.AssertionError: Activity never becomes requested state "[RESUMED, CREATED, STARTED, DESTROYED]" (last lifecycle transition = "PRE_ON_CREATE")

I saw that someone here had this problem before and solved it by adding a ComponentActivity in their manifest, but I just get the same result. Has anyone here had the same experience? 😄 🤔

Hi there, is there a way to use offset/absoluteOffset in a Column and force the column to fit the content ?

Has anyone tried compiling compose content with kotlin 1.5.10, and then using that in a project as an external dependency (aar) which uses kotlin 1.5.20? I’m wondering if it’s just the compiler that needs 1.5.10 or will the runtime engine have issues?

Do we have any indication of which Compose version will support Kotlin 1.5.21?

I get this when trying to run a preview on the device Error running 'TodoRowPreview': androidx.compose.ui.tooling.PreviewActivity is not an Activity subclass or alias

Is there any "official" connection between Datastore and compose?

hey guys, I'm fighting with this error, any help would be appreciated I only bumped the compose version to 1.0.0, my gradle file link https://github.com/FunkyMuse/Aurora/blob/main/build.gradle Using the latest stable arctic fox studio

androidx.compose.compiler.plugins.kotlin.IncompatibleComposeRuntimeVersionException: You are using an outdated version of Compose Runtime that is not compatible with the version of the Compose Compiler plugin you have installed. The compose compiler plugin you are using (version 1.0.0) expects a minimum runtime version of 1.0.0. The version of the runtime on the classpath currently is 1.0.0-rc01.

Trying to understand how LazyList works under the hood but it’s not that easy. 🤔 Is there anyone knows how the recycling works in a LazyColumn? Do items get recomposed or do they just exit the composition and new one are created ? And finally what would be the effect of using

DisposableEffect

inside a composable used by a LazyList in the case the items are reused? 🙏

Hey everyone, I am implementing a map-heavy application. I am following the Crane sample to set up the

MapView

. I am trying to move the camera as the user is sliding up a bottom sheet. The problem is that if i change the camera position according to the offset with

GoogleMap.moveCamera()

, the maps moves really laggy. Calling

GoogleMap.setPadding()

is smooth though. Can anyone help me with this? Thanks in advance!

I have a question about a behavior that I didn't expect. 1. I have a

@Composable
fun ForgotPasswordScreen(successEvent: () -> Unit, vm: ForgotPasswordScreenViewModel){
...
  ~buttonOnClick {
    vm.makeNetworkCall(successEvent)
  }
...
}

2. successEvent: () -> Unit, is a navigational event that takes me back to SignInScreen 3. ForgotPasswordScreenViewModel has

fun makeNetworkCall(onNetworkCallCompletedSuccessfully: () -> Unit)

and on completion of the network call,

if (call.isSuccessful) successEvent()

When I throttle the network call (for testing) it takes like 10 seconds, and I background the app, wait 20+ seconds... and I come back in the app, I can see that the app navigated successfully and the SignInScreen is showing. I guess I was wrong in thinking that the successEvent() wouldn't have any action since the app was backgrounded?

I want to create view like that below. I try:

@Composable
fun SearchBar(label: String) {
    RateMeAppTheme(isSystemInDarkTheme()) {
        Row(
            modifier = Modifier
                .fillMaxWidth()
                .wrapContentHeight()
                .background(MaterialTheme.colors.onBackground)
                .clip(RoundedCornerShape(20.dp))
                .padding(20.dp)
        ) {}
    }
}

but I get rectangle max width without rounded corners. Why?

Compose question. Once user authenticates, how do I remove authentication compose screens to not be in stack anymore? Multiple activities (e.g. AuthenticationActivity, ContentActivity) ?

Is there any performance Improvement in Compose 1.0? I just update my App on Play Store and I noticed slightly better performance. btw I am not using Lazy* Composable, the last time I used it had poor performance on older devices hopefully it improved as well 👍

I'm an animation noob so please excuse me if this comes off as trivial. I have a little tutorial screen I'm making and there is a rubber duck in the center :rubber_duck: and my requirements are to make it "bob" up and down slightly, on an infinite loop. I would have typically maybe considered this using MotionLayout, but is there an easy way to animate this kind of bobbing effect in compose?

Hello, I have tried to rebuild my custom progress bar in compose but faced issue, delay in TweenSpec works not as expected:

val transition = rememberInfiniteTransition()
val value = transition.animateFloat(
        0.5f,
        1f,
        infiniteRepeatable(
            repeatMode = RepeatMode.Reverse,
            animation = tween(
                durationMillis = 650,
                delayMillis = 160,
                easing = BezierEasing
            )
        )
    )

it applies delay on each iterate, is there any legit way to delay only first iterate? like startDelay in ValueAnimator?

If i pass boolean inside compose navigation route like url encoded param (ex:

login?authorized=true

) then later when i extract it from navigation arguments (Bundle) it appear there as

String

but not an as

Boolean

. It is a bug or feature? How can i pass

Boolean

between nav destinations without converting?

can someone help me understand what I might be doing wrong. I am using insets v0.13 (haven't upgraded to compose 1.0 yet). Whenever I tap the TextField, the first time the padding from the inserts work perfectly however, on subsequent runs the padding seems like it's doubled somehow. (Code in thread)

I was wondering if it is possible to use MutableStateOf with a Delegates.observable ? I want to know inside my ViewModel() subclass when my MutableState variable changes. I am looking for an equivalent of the following SwiftUI code:

@Published var meInformation : Me? {
        didSet {
           print("MeInformation changed: \(meInformation)")
        }
    }

This doesn’t compile for me: (unresolved reference: by)

class AuthenticatedUser(val context: Context) : ViewModel() { 
    var meInformation: MutableState<MeInformation?> = mutableStateOf(null) by Delegates.observable("<no name>") {
        prop, old, new ->
        println("$old -> $new")
    }
}

I’m not sure if it matters (being new to Kotlin), but meInformation is a @Serializable object