Is it Ok to use non-local state from a Composable function? An example would be a Composable that shows a Text with a String taken from a 

MutableState

 stored as a member of an object retrieved through an Ambient, like this:

data class ServiceX (
   val whateverString: MutableState<String>("meow")
)


@Composable
fun Whatever() {
   val serviceX = AmbientServiceX.current
   Text(serviceX.whateverString)
}

Will the Composable function repaint when 

whateverString

 changes? Are there any problems with this?

Hi, I have a preview composable defined like this:

@Preview
@Composable
fun PostHeader_Preview() {
    MyAppTheme {
        PostHeader(Post.PLACEHOLDER)
    }
}

that has a render problem that looks like this:

java.lang.NoSuchMethodException: com.example.myapp.components.PostHeaderKt.PostHeader_Preview

(full stacktrace in thread :thread-please: ) I have no idea how to fox that since the method actually exists, what can I do ?

I have a state

var current by remember { mutableStateOf(0) }

after any change on current value, AndroidView component does not recompose. Does anybody know the answer? How can I update the AndroidView() part?

which theme should be used in manifest? I need to create a light and a dark theme in xml too? or compose has a default for that?

Hello 👋 What is the best way/practice to change the color of the ripple effect in default Material Buttons ? Knowing that what I have done in this example doesn’t work because internally in the

Button

Composable, the

indication

modifier is set to

.indication(interactionState, AmbientIndication.current())

or should I build my own Button to have control over the indication ?

Is there any Pull to refresh Composable?

Hi guys, anyone are using Compose in production ? im ask because on my team we are thinking if we use in production or not.. if anyone is using, are having some troubles, or crashs ?

Wrong title on android libraries documentation page detected. @Adam Powell @jim https://developer.android.com/jetpack/androidx/releases/compose-compiler

Sorry wasn't sure how to inform about this. Whats the right way?

Hello folks. I'm wondering if anyone might have a more elegant solution to handling focus for multiple TextFields when triggering the ImeAction. I basically have a column of TextFields, and it seems like each field in the column scope must have its own

FocusRequester

. But perhaps

FocusOrderModifier

is what this is for...anyone have an example of how to use that? Here's what I have working so far:

val firstNameFocus = remember { FocusRequester()}
    val lastNameFocus = remember { FocusRequester() }
    val emailFocus = remember { FocusRequester() }
    val passwordFocus = remember{ FocusRequester() }

    Column(Modifier.padding(16.dp)) {
        onActive {
            firstNameFocus.requestFocus()
        }
        CommonTextField(
            value = firstName,
            onTextChange = onFirstNameChange,
            modifier = Modifier.padding(8.dp).fillMaxWidth().focusRequester(firstNameFocus),
            label = { Text("First Name") },
            onImeAction = {lastNameFocus.requestFocus()}
        )
        CommonTextField(
            value = lastName,
            onTextChange = onLastNameChange,
            modifier = Modifier.padding(8.dp).fillMaxWidth().focusRequester(lastNameFocus),
            label = { Text("Last Name") },
            onImeAction = {emailFocus.requestFocus()}
        )

        CommonTextField(
            value = email,
            onTextChange = onEmailChange,
            modifier = Modifier.padding(8.dp).fillMaxWidth().focusRequester(emailFocus),
            label = { Text("Email") },
            onImeAction = {passwordFocus.requestFocus()}
        )
        PasswordTextField(
            value = password,
            onTextChange = onPasswordChange,
            modifier = Modifier.padding(8.dp).fillMaxWidth().focusRequester(passwordFocus),
            label = { Text("Password") },
            isPasswordVisible = remember { mutableStateOf(true) },
            onImeAction = {viewModel.registerUser(firstName, lastName, email, password)}
        )

Hi guys What are some good practices for keeping code readable and simple when styling Views. i come from RN and getting each day in love with Android Compose. what im exactly looking for is a way to keep the modifiers in one place. in react native i would do something like

const styles = StyleSheet.create({
contaienr: {
....
...
...
},
box: {
...
...
}
})

is there any good practice to do this with android compose?

It seems that

Icon

can't be resized:

Icon(
	imageVector = Icons.Default.SentimentVerySatisfied,
	modifier = Modifier.size(40.dp) // has no effect
)

Image on the other hand works. It's a bit confusing when to use

Icon

and when

Image

.

ImageVector

,

ImageBitmap

Painter

makes it even more confusing. Can someone enlighten me here please?

Hi all, for

LazyColumn

, I want to hide things if I’ve scrolled on my list. I’ve tried

LazyListState

, but nothing is jumping out to me. Do we have an API to do this?

Does anyone know how far

remember{…}

can work on a list of Bitmaps? I was trying to use it to remember the state of a Bitmap I loaded from Picasso for list items, but scrolling back and forth on a list, I still see the bitmaps having to reload. Following example here: https://stackoverflow.com/questions/58594262/how-do-i-load-url-into-image-into-drawimage-in-compose-ui-android-jetpack

val imageState = remember(id) { loadPicture(url = item.photoUrl) }
private fun loadPicture(url: String?): State<ImageState> {
val imageState: MutableState<ImageState> = mutableStateOf(ImageState.Empty)
... //Picasso
}

sealed class ImageState {
    data class Success(val image: Bitmap) : ImageState()
    object Failed : ImageState()
    object Loading : ImageState()
    object Empty : ImageState()
}

Is there a guide for using the Compose Compiler only for building tree-like structures? This example from 6 months ago is using a prebuilt "compose wrapper" to work: https://github.com/ShikaSD/compose-server-side/tree/master/compose-wrapper Is there any simpler way, idealy only requiring adding dependencies in build.gradle?

Is there any pattern in Jetpack Compose to add actions to the

TobAppBar

from a Composable that does not have access to it? I am thinking in something like SwiftUI’s

toolbar

and

ToolbarItem

(e.g. see https://swiftwithmajid.com/2020/07/15/mastering-toolbars-in-swiftui/) . Also, is there a mechanism or pattern to set the `TopAppBar`’s title from somewhere else, like SwiftUI’s

navigationTitle

?

Question about recomposition granularity Given this composable with state:

data class State(
    val firstCounter: Int = 0,
    val secondCounter: Int = 0
)

@Composable
fun MyScreen(
    stateFlow: StateFlow<State>,
    onClick1: () -> Unit,
    onClick2: () -> Unit,
) {
    val state by stateFlow.collectAsState()
    Column {
        Button(onClick = onClick1) {
            Text(text = "One ${state.firstCounter}")
        }
        Button(onClick = onClick2) {
            Text(text = "Two ${state.secondCounter}")
        }
    }
}

If only one field of the

state

object changes will it trigger recomposition of only one (the one that’s reading that field) or both buttons ? Can someone point to some docs or examples to learn a bit more how recomposition actually works? :thank-you:

Is there any out of the box solution for handling long press on button, and for handling long presses in general? I've found

LongPressTimeout

, but can't find any example of it being used, have anyone tried it and could share some experience?

My intuition is failing me. I'm not sure if this is a bug in desktop, or a failure of my understanding. See thread.

Can we avoid using xml files for theming like colors.xml, theme.xml in the near future? Currently theming is a mix of xml and

MaterialTheme

composable. Another question would be if we can set the color of the system bar via compose or is it only via theme.xml possible?

Is there any support for popups or tooltips from AnnotatedString, or from text in general? For Desktop, specifically, but it seems like it would be a general compose API and thus more appropriate here. I looked into rolling my own, but the closest thing I could find is SelectionHandle & related things, but most of it relies on private stuff.

I’m used to extracting navigation logic from android layer (hiding the impl details behind the interface), but I decided to give compose navigation a try. That involves tight coupling of navigation with the ui, triggering navigation from callbacks inside composable functions. I’m wondering if effects such as

onDispose()

are safe to perform such action or it’s rather considered as an anti-pattern/might lead to unexpected state (is there a risk of recomposition causing not intended navigation?). See example code below (where

isInProgress

is a part of collected state

false

by default):

if (isInProgress) {
    CircularProgressIndicator()
    onDispose {
        navigateToDone()
    }
}

We’re getting this non-sensical crash. Just a wild guess that this is compose-related. Any ideas what could be the cause? This doesn’t crash on my environment, but it does from another computer.

Caused by: java.lang.ClassNotFoundException: Didn't find class "com.example.SomeScreen.SomeScreenKt$SectionTitle$1" on path: DexPathList[[zip

Morning composers, I got a

Box

in a

Box

and I want to offset the inner box by

x

dps from the left, I tried left padding and offset though nothing seems to work

Box(Modifier.background(Color.Red).width(128.dp).height(128.dp)) {
        Box(Modifier.background(Color.Green).width(32.dp).height(128.dp)) {

        }
    }

I want the inner box to have some space on the left hand size that I can specify hope that makes sense

Is compose compatible with android wear?

How can we make date picker in compose, Is there a way to do it?

From the docs over the

Surface

dec:

Elevation: Surface elevates its children on the Z axis by elevation pixels, and draws the appropriate shadow.

Does that mean that the

Surface

sets the

Modifier.zIndex()

value of all it's children?

Does State/SharedFlow work well in compose? Does anyone have any experience using these over LiveData in a compose app?

Hi there! 👋 This maybe an x-y question but... If I have this:

Modifier
    .fillMaxWidth()
    .padding(horizontal = 16.dp, vertical = 8.dp)

And want to keep the 

fillMaxWidth

 down the chain but remove the padding, is that possible? Thanks!!!