Navigation Compose on every screen size

[@StraplessReligion]

so, there no silver bullet for all screensizes. at least a talk about it i was missing so far, also shines a bit more light on the navhost

[@AndroidDevelopers]

We're not quite able to take down the werewolf that is all screen sizes, but we are making it easier to manage! Arm yourself to tackle all screen sizes by checking out our codelab: goo.gle/3DLSdyA

[@Sherimankind]

What do we deprecate this time??

[@zaryabK-vi8fh]

@@Sherimankind 😂😂

[@codelabspro]

Compose is now deprecated 😂 Please use CSS instead 😂

[@zaryabK-vi8fh]

@@codelabspro hahaha 🤣

[@marlonlom]

What to say about wearos android apps and navigation? similar navcontroller? how to implement android ui tests?

[@LaughTale1993]

Hi @Android Developers Android Developers I am having a problem. Since 2-3 months now im working on my startup which is 2 apps using the same databases I don't know if I might call it like that...its like UBER which have the users(customers app) and users(drivers app) but both communicating with the same database...as a self taught android developer, im a little bit lost about how to connect the apps together...can someone give me a way pls, THANKS guys.

[@theren8311]

Sounds like you just need a backend application. Like Firebase's Functions or a Spring Boot backend, or a Rails backend. Basically, the apps already "connect" to each other, since they are using the same DB, they just present data (assuming by same DB you meant a DB running on a remote db server and not the device). To make that more streamlined, a backend would orchestrate the mobile apps state. So driver app, sends detail to backend, backend pushes detail to customer app, and vice versa. Thus, only the backend R/W to the DB.

[@LaughTale1993]

@@theren8311 i am using Colton as programming language instead of java...but as database I used Room database instead firebase or SQL as other developers...

[@yewo.m]

​@@LaughTale1993 Colton or Kotlin?

[@Dmitriy_Aralov]

Thanks Jeremy!

[@seguramlk]

All that shenenigan to go from one screen to another ):

[@stevensilitonga]

use a when statement.

[@jaehwanoh2002]

Where can I get this code? Especially example with deep link part.

[@clementjoymasinamela4244]

Thanks, very informative.

[@pinoy_marites_beh]

I know I have to dig further but just leaving a naive question, what's the difference between movableContent() vs rememberUpdatedState() ?

[@Zhuinden]

they are very different things, movableContentOf lets you "move" the same-looking composable hierarchy from A to B based on its ID, while rememberUpdatedState is a way to ensure that effects receive the latest incoming argument values even if the keys don't invalidate and recreate the effect.

[@pinoy_marites_beh]

@@Zhuinden thank you.

[@pablovaldes6022]

The NavHost/NavController behavior is that of a Backstack. If I want a different behavior, let's say a card roulette for a TV App or a navigation that allows more than one item Active in the screen at the same time, then it won't fit my needs. I think you guys should make the NavHost/NavController API more open to customizations. My navigation may not be "Backstack" related

[@benedikthengst6818]

Fully agree with it

[@theren8311]

Sounds like you just need another nav host. You can create a Nav Host per upper/main content. So in other words each screen has their own nav host with it's own nav graph. Hopefully I understood your problem correctly.

[@radu2173]

"Muvu content"

[@mondoshigua]

📱🇨🇴🙋🏻‍♂️👍🏼🤝🏼