We were thinking with some of our QA engineers to look into starting an effort to have them write some UI tests with something like appium (or whatever alternative) but I was worried that now that our App is a hybrid of View/Compose this might be more tricky than it already is. Has someone gone down that road? Got any resources to share regarding it? Maybe I’m missing some part of the official docs. Everything I’ve tried to look regarding such tests with Appium (Maybe appium is the wrong path for them to take) seems to be from 4+ years ago so no mention of compose whatsoever.

Is this considered “Stable”?

@Stable
class Foo {
   var fieldA: Boolean by mutableStateOf(false)
}

Is there a character you can use that looks like a space but is not treated as one when a Text is overflowing into a new line so you can control that multiple words including “spaces” will overflow together?

I'm starting a new project with Compose, but I tend to use fragments(and use ComposeView inside them) instead of pure compose for several reasons: 1- I see one activity multiple fragments architecture is more constant than pure Compose (correct me). 2- I like Navigation component with safeArgs that Compose doesn't support, although, I heard a lot of complaints about NC Compose. 3- I need an easy way to write XML code if I faced any blocked issue with Compose or when I need it. Any tip/resource apricated :)

I have textfield and end drawable which is info type. When I click on that I want to open this popup menu look like this. I don't know what we call this. Anyone guide me how can I make like this?

I have a weird API design consideration. I'm writing a container which can arrange and animate its items

val state = rememberNiceState(itemPositions: Positions.Stage0)
NiceContainer(
  itemCount = 3,
  state: NiceState = state,
  itemContent = { index -> MyItem(index) }
)
LaunchedEffect(Unit) {
  state.animateItems(Positions.Stage1)
}

The problem is that to calculate an (x,y) of each item given the "stage" I need to know the

itemsCount

: both in State consctructor and in

animateItems

. I could make

itemCount

private val in State, but I do not want to require user to pass

itemsCount

both to

NiceContainer

composable and to State constructor, this feels weird. Similarly passing

itemCount

only to State constructor and removing it from

NiceContainer

argument list feels not like something you do in other composable container layouts... Any suggestions?

Hello everyone, I have a question that maybe you have already answered, why the

@Preview

does not work in libraries, I am creating a library of components for my project, but the previews do not load, one of the proposed "solutions" was to include

androidx.appcompat:appcompat

in the library, I did it but it still does not work, do you know anything about it?

What should be done when a component has too many inputs and events? Is there such a thing as too many inputs/events from a single component?

MyComponent(
  input1...,
  inputN,
  event1...,
  eventN
)

Hello everyone, I have a strange error, has anyone else experienced this error?

Been writing compose apps for like a year+ (3 fully compose apps shipped to prod) I've never written

@Stable

in any of my codebases. 🙈 Am I missing something basic here? Should I be marking classes as stable?

I'm trying to implement a PIN entry text field, therefore it can only accept digits and it has a fixed number of digits. I was considering using

BasicTextField

and its

onValueChanged

parameter to filter out any non-digit character. However, reading the documentation I found this :

Please keep in mind that

onValueChange

is useful to be informed about the latest state of the text input by users, however it is generally not recommended to modify the value that you get via

onValueChange

callback. Any change to this value may result in a context reset and end up with input session restart. Such a scenario would cause glitches in the UI or text input experience for users.

Does that mean that something like

var text by rememberSaveable { mutableStateOf("") }
BasicTextField(
    value = text,
    onValueChange = { input ->
        text = input.filter { it.isDigit() }.take(5)
    }
)

could be a problem because I am not passing

input

as is to

value

?

Hello, I have a problem with

isSystemInDarkTheme()

I am adding it to the theme but sometimes it returns true after false

2022-08-10 17:12:22.215 6489-6489/ E/isSystemInDarkTheme: true darkMode 
2022-08-10 17:12:23.338 6489-6489/ E/isSystemInDarkTheme: true darkMode 
2022-08-10 17:12:24.478 6489-6489/ E/isSystemInDarkTheme: false darkMode 
2022-08-10 17:12:30.008 6489-6489/ E/isSystemInDarkTheme: false darkMode 
2022-08-10 17:12:30.697 6489-6489/ E/isSystemInDarkTheme: false darkMode

@Composable
fun Theme(
    darkTheme: Boolean = isSystemInDarkTheme(),
    content: @Composable () -> Unit
) {
    val colors = if (darkTheme) {
        DarkColorPalette
    } else {
        LightColorPalette
    }

    ProvideHapiColors(colors) {
        MaterialTheme(
            colors = if (darkTheme) darkColors() else lightColors(),
            typography = Typography,
            shapes = Shapes,
            content = content
        )
    }
}

New compose versions released today 🎉. Some interesting things from my pov stable • 1.3.0 stable of compose compiler • 1.2.1 stable of most other artifacts • 1.2.1 stable releases are pretty minor but it did fix a memory leak and some layout inspector issues alpha • 1.3.0-alpha03 is avail • New param in

Crossfade

,

animateAsState

and

Animatable

for tooling label • Added

atFraction

function for defining keyframes at a fraction instead of at a specific duration. • Resource Fonts now support setting font variation settings (API 26+). • Variable font support in

DeviceFontFamilyNameFont

• Text fields will now throw more detailed exceptions when the

OffsetMapping

provided by a

VisualTransformation

returns invalid indices. • Introduce experimental APIs to share item provider logic between Lazy layouts. 🤔 • Deprecate

TextInputService.show|hideSoftwareKeyboard

. Please use

SoftwareKeyboardController

instead in app code and

TextInputSession

in IME-management code •

LayoutCoordinates.findRootCoordinates()

is now public • Added experimental API to get the

LayoutCoordinates

in the

PlacementScope

. This lets developers know where the current layout is to place children relative to its position • Paragraph is now expect|actual and defined for Android and Desktop. • Added

@RequiresPermission

to APIs that require granting the

POST_NOTIFICATIONS

permission on SDK 33 and above. material 3 • 1.0.0-alpha16 • Support specifying a custom width on a navigation drawer • Removes

Divider

from

MenuDefaults

and

TabDefaults

I have asked a similar question before here when I was just starting with compose but I still feel a bit confused now that I ran into this section of the documentation: Defer reads as long as possible (https://developer.android.com/jetpack/compose/performance#defer-reads) which states:

You should defer reading state variables as long as possible. Deferring state reads can help ensure that Compose re-runs the minimum possible code on recomposition. For example, if your UI has state that is hoisted high up in the composable tree and you read the state in a child composable, you can wrap the state read in a lambda function. Doing this makes the read occur only when it is actually needed.

All other documentation and examples seem to prefer passing only immutable data classes for state -- is this deferring technique recommended only for the most intensive cases (for example animations with values changing every frame)? To my understanding, when a value changes, the whole scope that read it is recomposed, including all child composables (unless the inputs are @Stable in which case all of the inputs will be diffed and recomposed only if the inputs are different). What is the downside of doing deferred reads and passing

State

, how much overhead does it add compared to diffing all parameters of invalidated child composables in a large invalidated scope? Also, does it matter how the state read is deferred? I have preferred not to use the delegate syntax for mutableStateOf so I can easily pass

State<T>

objects directly to child composables. Is there some reason why the provided example uses a callback and not something like this:

@Composable fun Child(state: State<T>) { state.value }

?

Hi, I am using Parent Layout as Column and then adding vertical Scroll state, inside column i have used AndroidView With RecyclerView now my problem is how i can addOnScrollListener on scroll so i can add functionality based on recyclers scroll.

Can I set

ViewCompositionStrategy

to the ComposeView from the XML?

Hi everyone, why content not scroll in Compose, even i add adjustResize in the manifest and also keyboard opened but not scrolling not worked.

Column(
        modifier = Modifier
            .fillMaxSize(1f)
            .background(color = Color.White)
            .verticalScroll(state = rememberScrollState(),
    ) {
        HeaderSection("Welcome!", "It's great to have you here") {
            viewModel.events.postValue(AuthModuleClickEventsObject.BACK_CLICK)
        }
        ContentSection(
            modifier = Modifier
                .background(
                    color = Color(0xFFF3F6F9),
                    shape = RoundedCornerShape(topStart = 34.dp, topEnd = 34.dp)
                )
                .fillMaxWidth()
                .fillMaxHeight()
                .padding(horizontal = 17.5.dp),
            {}, {
                viewModel.events.postValue(AuthModuleClickEventsObject.FORGOT_PASSWORD_CLICK_EVENT)
            })
    }

Are there any plans to improve stability inference? It looks to me like this, but also many more complex, super common structures could be inferred to be stable by the compiler (may not be straightforward, but still, possible). https://kotlinlang.slack.com/archives/CJLTWPH7S/p1660121060190209

Hi all, is there anyone also facing the issue of Column didn`t scroll when keyboard open even i added verticalScroll state.

How can a function with unstable values be restartable & skippable? All documentation Ive read on the subject tells me that this is impossible, or is it?

restartable skippable scheme("[androidx.compose.ui.UiComposable]") fun BottomBar(
  unstable pages: List<ExplorePage>
  stable currentPage: ExplorePage
)

Hey all! Is there a way to pass a click event from top view to bottom view in overlapping views? I've a

Column

overlapped by a

LazyList

(trying to implement a nested scroll) and I was wondering if there's a way to pass click events to the

Column

beneath and scroll events be handled by the

LazyList

itself. I want to preferably do this only for the first item in the list. Is something could be done in Compose today?

Are there any good solutions for typesafe and boilerplate free Compose Navigation? 1. For specific navigation graph only a certain set of destinations (sealed class hierarchy/enums) can be passed to

navigate()

2. Pass navigation arguments (like item IDs) in a typesafe manner 3. Automatically generate the route URIs with argument placeholders 4. Easily extract the navigation arguments without additional boilerplate I'm writing extension functions and sealed class hierarchies/enums for this, but this is such a common use case that maybe someone already came up with a library (or at least someone of you has good suggestions).

Does anyone know how to get the contents of a compose Row to be spaced by a minimum amount, but if the parent is larger, to then increase that spacing size? A combination of

Arrangement.spacedBy

and

Arrangement.SpaceBetween

?

There is an animateItemPlacement modifier

Is it OK to pass mutable state across a nested graph? I have screens in a

NavHost

where each

composable {}

contains a Composable function that is passed State representing the app’s settings (the State’s value actually, originating as

by mutableStateOf

above

NavHost

). I decided to separate out all the settings screens into a subgraph (same module) using an extension function called

NavGraphBuilder.settingsNavGraph

. In order to get the state to continue to track in the screens now moved into the subgraph, I pass a lambda to

settingsNavGraph

that reads the

.value

of the settings. (Locally, just above the

NavHost

call, I declared

val settingsAsState = rememberUpdatedState(settings)

in order to set this up.) This seems to work well, but I wanted to know if it was OK to do so, or if there is a better way. (The Compose Owl sample app does something similar, passing a

State<>

to the extension function – but it looks like it is the only sample app that does this.)

Hi guys, I'm facing an issue with compose

navigation-animation

: When I interrupt the transition to another screen by pressing the back button, the animation gets bugged (List screen moves up a bit). I found this issue tracker link, which is probably the cause: AnimatedContent sets incorrect target animation on interrupt Has this ever happen to any of you, and is there a solution? In the video, you can see the expected behaviour happening in the second attempt, and the bug happens in the first and third attempts.

Hi guys, I’m trying to validate a TextField with Jetpack Compose using StateFlow on a ViewModel I saw an example that looks like this:

val isButtonEnabled: StateFlow<Boolean> =
        combine(isLoading, login, password) { isLoading, login, password ->
            isLoading.not() && login.isNotBlank() && password.isNotBlank()
        }.stateIn(viewModelScope, SharingStarted.Eagerly, false)

But I only have 1 field instead to validate so I try to put it like this

val isContinueEnable: StateFlow<Boolean> = MutableStateFlow(login.value.isNotBlank())
        .stateIn(viewModelScope, SharingStarted.Eagerly, false)

but when I start typing on the TextField it doesn’t change de value to

true

so is there a method similar to

combine

to get

Flow

but just with one element?

Does

Locale

make sense as a composition local? How do y’all handle things like

uppercase()

which accepts a locale argument?

When we navigate from screen “A” to screen “B”. Screen “B” has some default background Color. How do make this screen B partially transparent so that I can see screen A . Thanks in advance 🙏