This might be a dumb question... but one thing I've always wanted to have in android is like a completely flexible emulator height and width so that I can "check" that my designs and layouts work on a WIDE range of android phones. This is just something I'm used to with web dev. Load my site. And just drag the bottom right hand corner to expand and contract the window. Could compose-desktop be used for "stress" testing my layouts like I envision or does compose desktop do something differently and I shouldn't bank on the compose desktop to match what would actually happen on my android device?

Hi folks, do AGP stable supports Compose?

Hi, is it fine that size Modifiers from parent has more priority than from inline layout e.g. Column?

Hi, got a question regarding Dialog, usually it has some horizontal padding, now generally it is fine, but right now i need a dialog, that will fill the entire width of screen, is there some simple way of doing that? I found a solution on stack that, i can add properties in style.xml, but it changes it for every Dialog i have, and thats not what i’m looking for. Anyone had similiar problem?

Regarding the reuse of an Android View. Is there any way of unloading resources once the view is destroyed? I want to avoid leaking things.

I have a composable A which I want to be allowed to be used only within composable B (kind of like make it internal to Composable B). Is there any way to achieve this?

I have a difficulties to deal with the

pointerInput

Modifier

, I try to implement a custom drag behavior. Based on a position on a

Box

I compute a color. If I use

var color by remember { mutableStateOf(initialColor) }

inside my composable and update color value based on drag position it works. If I extract a state (to allow parent composable to consume it), and hoist it, it doesn't work anymore. My understanding is that the value captured by

onDrag

is stale and still consider the initial value used and never update it. I don't understand the difference with state being hoisted or inline within Composable… (code in thread)

Hi 👋 Do you know where I can get those samples from? I see them in docs but can’t find them when clicking on the link

when using LazyRow to show a list of items, at what point do views of items which are scrolled out-of-view get cleaned up/recycled?

Is it possible to get a hardware-accelerated Canvas in Compose? I’m doing some canvas drawing currently with

SurfaceView.lockHardwareCanvas()

. I didn’t see anything here about it: https://developer.android.com/jetpack/compose/graphics

Hello all, I'm using

HorizontalPager

. When I run the app, I get

java.lang.NoSuchFieldError: No static field Companion of type Landroidx/compose/foundation/layout/BoxScope$Companion; in classLandroidx/compose/foundation/layout/BoxScope; or its superclasses (declaration of 'androidx.compose.foundation.layout.BoxScope' appears in /data/app/~~t1Ai-4vbEvAZ8lELuEQ7cA==/com.partnersincrime.focuslauncher-I6-eS_JANYdA0QptWYtpzA==/base.apk)
        at com.google.accompanist.pager.Pager.Pager(Pager.kt:461)
        at com.google.accompanist.pager.Pager.HorizontalPager(Pager.kt:147)

Is it possible to have nested scrolling but with a scrollable component inside a draggable component? For example: a vertically draggable bottom drawer that can only be dragged up to a certain height and, inside it, a LazyColumn; in this case, when the bottom drawer has been dragged up to the maximum height, I would like the LazyColumn to receive the gesture as scroll.

Here’s my latest medium post Compose, Camera and Canvas, it’s about creating a custom view using Jetpack Compose with the help of canvas and camera for 3D transformations. Also, this is the final result, had lots of fun developing it, maybe you find it worthwhile reading 🙂 thanks.

Is there an easier way to preview

CoilImage()

similar to

<ImageView tools:src="@tools:sample/avatars" ... />

or possibly any alternatives to quickly viewing image composable while designing a screen?

Is there any out of the box way to support the password toggle that came with material android/xml?

Hello everyone. I'm new to Jetpack Compose and was experiencing a problem implementing it. Any assistance would be highly appreciated: https://stackoverflow.com/questions/67073647/java-lang-nosuchfielderror-no-field-companion-of-type-landroidx-compose-foundat

Do compose material surfaces get that superpower where if two surfaces have the same elevation, and are placed on top one another or side by side, they are merged (somewhat) into one surface? (CardViews in View system have this ability; at least on recent android api levels) 🤔 (if no, how can I fake it?)

I try to migrate from

compose-router

to jetpacks

navigation-compose

and I'm wondering how to handle constructs like those properly:

// (container) screen with a BottomNavigationBar
fun ScreenContainer(
    ...
    childs: @Composable (PaddingValues, SomeState, SomeHighOrderFunction) -> Unit
) 

ScreenContainer(
    ...
) { innerPadding, SomeState, onError -> // How to easily pass things like innerPading or highorder functions to child screens?
    NestedRouter(startPoint = Screen.A) { backStack ->
        when(backStack.last())
           is ScreenA -> ScreenA()
           is ScreenB -> ScreenB()
    }
}

vs.

NavHost(navController = navController, startDestination = "container") {
    composable("container") { ScreenContainer(
        ...
    ) // childs are now called via navController
    composable("screena") { ScreenA(innerPadding = ?, state = ?, onError = ?) }  // How to get these parameters?
    composable("screenb") { ScreenB(innerPadding = ?, state = ?, onError = ?) }  
}

Thanks in advance!

Let's say I have 4 versions of button (primary, error, secondary, ...) What is the preferred (more idiomatic?) way to do the API: 1️⃣

ButtonPrimary(onClick = {}) { Text("Primary") }
ButtonSecondary(onClick = {}) { Text("Secondary") }

or having it configurable via a property and enum? 2️⃣

Button(Kind.Primary, onClick = {}) { Text("Primary") }
Button(Kind.Secondary, onClick = {}) { Text("Primary") }

My SwiftUI friend forces me to the enum way but I would prefer rather the first one (their syntax seems better here - they may use only the

.Primary

token as the value.)

Hello guys, I have an Animatable animation running in a coroutine, the problem is that when I put the app in the background, my animation stop, and when I return to the app, my animation has finished instead of continue in the interrupted value. How can I return to the app and continue my animation where I left off?

Hello, everyone. 👋 Quick question: was real time code changes in the emulator (hot reload) enabled since day one or it was introduced in latest versions of AGP and Compose?

How can I show a Drawable object in an Image? The drawable is not from resources, its just an object from the Drawable class.

Is it possible to achieve

android:ellipsize="middle"

behavior with

Text

composable? I know there is

TextOverflow.Ellipsis

but how do I specify if it should be in the middle, end, etc?

Hey, I'm testing different methods for drawing a circle with a stroke. Why I'm getting a different result when using those 2 methods?

// first method - result on the left
  Canvas(modifier = Modifier.size(50.dp)) {
    drawCircle(Color.Blue)
    drawCircle(Color.Green, style = Stroke(width = 2.dp.value))
  }
  / second method - result on the right
  Surface(
    shape = CircleShape,
    color = Color.Blue,
    border = BorderStroke(2.dp, Color.Green),
    modifier = Modifier.size(50.dp),
    content = {}
  )

When showing lists, when my data changes the list is fully recreated. Is it possible to animate the item updates like how we could in DiffUtil?

Is there a way to change the statusbar color using Jetpack Compose? Sometimes I can set it, but its not completely filled.

How would you handle this

when

construct in a composable function:

when (val state = presenter.uiState) {
        UiState.Success -> {
           CallComponent() // composable code
        }
        is UiState.Failure -> {
           CallAnotherComponent() // composable code
           state = "setState" // non-composable code
        }
    }

presenter.uiState

is a mutableStateOf. Optimally this code should only be called when presenter.uiState has changed but instead it's called on every recompose. What's the right way to handle this?

Hi ! Let's say I've built an

@Composable

named

NonInteractiveZone

which has some process running or not based on a

Boolean

state (let's say

shouldBeRunning

). I would like to let other

@Composable

call some "methods/events" on it, let's say

startProcess()

and

endProcess()

. So that I could call

myNonInteractiveZone.startProcess()

. Can I achieve something like that with a

@Composable

? More in the thread.

Has anyone ever had a Switch that wasn't controlled by animation?

val normalModifier = 0.dp
val expandModifier = 700.dp

val animatedHeight by animateDpAsState(
    targetValue = (if(viewModel.textListSwitch) expandModifier else normalModifier),
    animationSpec = tween(500)
)

I wrote a height animation of the expanded content, but I found that the Text control inside can be hidden in this way, while the Switch control is still displayed