how are you going between screens? what are you us...

# compose

[Leland Richardson [G]]

how are you going between screens? what are you using for navigation?

[Bryan Lee]

I start in ActivityA with setViewContent{..}
Then something triggers a startActivity(ActivityB) and I transfer data data using @Model object

Now I'm in ActivityB with setContent{..} and trying to mimic how JetNews navigates between Composable screens and now figuring out how to move data between the composable screens.

[Bryan Lee]

& I start in activityA with setViewContent since i'm working with a custom mapview & this is how i'm working around going from setViewContent to setContent

[alexsullivan114]

Is there a good reason to actually transition activites?

[alexsullivan114]

(not saying there isn't; I'm just imagining a compose world being a single activity world)

[Adam Powell]

most android app UI worlds are a lot easier with single activity per entry point, not just compose 🙂

[Adam Powell]

when you decide to implement a screen as its own activity, you've decided that it must be able to stand in isolation, able to derive and load all necessary state from only the parcelable arguments in the intent that started it

[Adam Powell]

this is a great tradeoff when you want to publish that intent-based interface to the system or to other apps as API for your app, not nearly as useful for internal navigation.

[Bryan Lee]

I would prefer to use a single activity, but not sure how to transition between older views that need setViewContent and composable functions that need setContent. I'm assuming that's still a WIP so this is my work around for now.
Or maybe there is a way to transition that I haven't come across?

[Adam Powell]

Leland might know the transition api off the top of his head but it's changed a few times and I don't remember it. In the absence of that, fragments that host either compose or view UI are an option