whats the best way to handle routing in compose, navigation component?

Does anyone know if there is a solution for this, I am having it on Alpha03 with Emulator and LG G6. I am using WebView in AndroidView with Compose Router on a subscreen if that is an issue?

Is this a bug or is there a reason why my preview looks different than my emulator ?

If I wrap

AnimatedVisibility

around the

TopAppBar

, I lose the elevation. Is there something else I should be using to toggle it’s visibility?

Hi, how can I observe when the application is in background? What's the alternative to onStart/onStop lifecycle methods in Compose?

Is there a way to know whether a composable is disposed because it gets removed compared to when it is disposed because the activity holding it gets rotated?

I did some playing around this weekend with using Compose for layout out and drawing to PDFs. Or in other words, making compose UIs printable. It's not a library yet, just a proof of concept, but there's a thread explaining how it works here: https://twitter.com/zachklipp/status/1310570706174967809?s=19 And here's the code: https://github.com/zach-klippenstein/compose-richtext

Any way to disable by default the new really obnoxious

Build on save

settings for preview instead of having to disable it in each file?

I am trying to set TextStyles by MaterialTheme.typography at init time for a class. Unfortunately, typography is a @Composable function and init cannot be Composable. Any good workarounds for this?

How is everyone handling navigation in their app?

I am doing a multiplatform project, and I am defining the color pallette in the shared view model. Is there a simple function to convert the 6-char RGB string (e.g. “CC6699”) into a 

androidx.compose.ui.graphics.Color

 object ?

Is there any way to implement a gradient like this? I tried using radial gradient but without success. I ended up drawing each line manually with a decay from the original color to full transparency. It's far from ideal but it's for a scrim so it does the job.

Hey, I wrote my first Medium article about Jetpack Compose, in particular - everything I know about the

@Preview

annotation. My intention was to have a single place with all the bits and pieces I've learned through different blog posts, docs, videos & my experimentations. If this is considered spam, I'm sorry about that and moderators/admins can delete this message. The article is not behind Medium's paywall, so - free for all 🙂 - Link. Any feedback or reporting errors are welcomed.

I haven't been able to add compose to my existing project for some time now because of kotlin reflect issues (that using moshi brings up) and some people recommended that I wait for 1.4.20 of kotlin. Since the 1.4.20 eap came out today I tried it. The app would crash at runtime due to a kotlin reflect issue with this

composeOptions {
    kotlinCompilerVersion '1.4.10'
    kotlinCompilerExtensionVersion '1.0.0-alpha03'
}

but now I updated to

composeOptions {
    kotlinCompilerVersion '1.4.20-M1'
    kotlinCompilerExtensionVersion '1.0.0-alpha03'
}

and the app won't even compile. stack trace attached. Is this a known issue by chance?

Is it intentional that

FlowRow

and

FlowColumn

don't have modifiers?

Hi @nickbutcher, may I ask a question about theming in compose. I have a situation where my primary color shouldn't be used for components that by default uses the primary color. for example: my primay color is Red so when using TextField, its active color defaults to Red. But I don't want it red but instead I need its active color to be Blue. If I understand it correctly, I would just have to create my own TextField and replace the active color. But then I look into Composable functions that create TextField and there are two. I would then have to have my own version of these two TextField Composable function with the overriden active color to Blue. It was fine here since there are only two functions I have to modify, but I was thinking what if there was more than two of these function or maybe in the future there may be additional of these functions. Is this the correct way to approach this problem?

Is there any way to make

DropDownMenu

work like

TextInputLayout

with

Spinner

? Like so?

I am trying to implement a chat screen , simillar to that of sample jetchat app. Problem is keyboard is overlapping parts of input text field and panel consisting of emoji, send button etc. Any idea why this is happening and how it can be corrected. I am attaching screen shots of both screen for mine code and original code

I am trying to add Compose to an existing project, however i get this error:

java.lang.AssertionError: Unbound symbols not allowed

Execution failed for task ':app:compileOmbordsalgStagingDebugKotlin'.
> Internal compiler error. See log for more details

Runtime JAR files in the classpath should have the same version. These files were found in the classpath: And then a loooooong list of Unbound public symbol for public kotlinx.android.synthetic...... Anyone know how to fix this?

A noob question. All samples for jetpack compose I have seen, also official ones have still groovy build files. Is there a reason for that or it is just a coincidence? I am asking becuase having issues (maybe be not related to jetpack) during migration to 1.4.x and compose.

The example of rotation in the jetpack compose playground seems a bit messy. Is there a simpler method to rotate a @Composable?

I noticed the source code is no longer visible. I wanted to take the slider code and make a customized vertical slider. Is the source for compose still going to be available?

Hello! I've seen that in AS canary 12, the

comp

live template default value is:

@androidx.compose.Composable
fun $NAME$() {
$END$
}

it should be

androidx.compose.runtime.Composable

, right?

Do we have Ratingbar in Compose ?

I am a noob to Android dev, but I understand the reactive UI pattern (from web dev). I have built a basic todo app with compose. But for ui, is it worth continuing to learn compose or should I wait for it to release and learn the current xml system for now?

Hello, I've had issues with alpha when updating from

alpha02

to

alpha03

.

alpha02

: animate alpha for a button, works fine

alpha03

: animate alpha for a button, main content animates correctly, but a weird border animation occurs I made an small sample:

@Composable
fun Alpha(modifier: Modifier) {
    val animation = animatedFloat(initVal = 1f)
    onActive {
        animation.animateTo(0f, anim = repeatable(
            iterations = Infinite,
            repeatMode = RepeatMode.Reverse,
            animation = tween(1000))
        )
    }
    Button(
        onClick = { ... },
        modifier = modifier.drawOpacity(animation.value)
    ) {
        Text("test")
    }
}

@Preview(showBackground = true)
@Composable
fun AlphaPreview() {
    Stack(Modifier.fillMaxSize()) {
        Alpha(Modifier.gravity(Alignment.Center))
    }
}

And this is how it looks if I use

alpha03

:

hey, is there any solution to define what was the

textAllCaps

when it comes to define the

TextStyle/Typography

? I wanted one of my typography styles to always be in caps.

So, i’ve been building my own theme, and i’ve been wondering why Colors is treating the individual colors as mutable state, but typography doesn’t? I imagine maybe it’s helpful for the recomposer so that it doesn’t have to rebuild the full component tree if colors change, it can just adjust the color of the individual elements, but i’d like to confirm that.

var primary by mutableStateOf(primary, structuralEqualityPolicy())
        internal set

It leads to a lot of extra code to create the update and updateColorsFrom functions, since everytime you add a new color, they have to be accounted for in both these functions.