Am I right in thinking that the screen structure ...
# compose-androidm
MarkRS
06/12/2023, 2:14 PMAm I right in thinking that the screen structure most in the "compose" mindset is a single activity with the various screens implemented as composables and routing controlled by a NavController?
This project is currently a (multiplatform) single-activity-multiple-fragment structure so I'm considering my best option for moving to composables.
The project is early enough in its lifecycle that I'd rather eliminate any tech deficit from this change immediately rather than let it build up.
✔️ 6
s
Stylianos Gakis
06/12/2023, 4:51 PMWith the caveat that NavController from androidx.navigation isn't multiplatform, so if you want a MP navigation solution you should look at alternatives.
m
MarkRS
07/08/2023, 10:37 AMWhat's your preferred solution for navigation?
I've found several libraries, of which Voyager seems like a credible "best".
s
Stylianos Gakis
07/08/2023, 2:52 PMI've never tried myself to work with a MP navigation library.
Voyager and decompose are popular choices afaik. I think Circuit has something around this area too.
m
MarkRS
07/08/2023, 2:53 PMDo you code your own navigation then?
a
Arkadii Ivanov
07/08/2023, 3:17 PMAnother option could be https://github.com/xxfast/Decompose-Router
m
MarkRS
07/08/2023, 3:19 PMThanks for that @Arkadii Ivanov, yes I saw that. Is it your library?
a
Arkadii Ivanov
07/08/2023, 3:30 PMNo, I believe Decompose-Router is maintained by @xxfast, though it leverages Decompose under the hood.
m
MarkRS
07/08/2023, 3:32 PMAh, you're the Decompose author? That's one (rather than Decompose-Router) I looked at
a
Arkadii Ivanov
07/08/2023, 3:33 PMYes, I'm the author of Decompose. 😀
m
MarkRS
07/08/2023, 3:35 PMLooks great, so why recommend Decompose-Router rather than Decompose?
a
Arkadii Ivanov
07/08/2023, 3:40 PMI think @xxfast could explain it better. As far as I understand, some people may prefer handling navigation inside Compose rather than creating separate classes for that. Though, Decompose may have more features (e.g. custom navigation models).
m
MarkRS
07/08/2023, 3:41 PMYes, Decompose looked like I'd have to do a lot of "other" things, which may be what you're saying too.
a
Arkadii Ivanov
07/08/2023, 3:45 PMWhat other things that you have to do? I meant that Decompose has many features, that you may want to use. Some features are even unique to Decompose currently.
m
MarkRS
07/08/2023, 3:46 PMI only looked briefly, but I mean that it was the "creating other classes" thing that stuck out
a
Arkadii Ivanov
07/08/2023, 3:47 PMAh yeah, so you can check alternatives and choose. Also most likely you will need classes for ViewModels anyway. Kinda the same amount of classes.
m
MarkRS
07/08/2023, 3:54 PMHmm, really? Ok. I'm feeling my way with this a lot so I guess I'll just have to choose and then take the consequences 😳
s
Stylianos Gakis
07/08/2023, 9:35 PMYou'll never know what you really want until you do something and figure out what you're missing.
Going with any choice and then bearing the consequences of that choice sounds like a great way to learn things. Plus, next time you'll know how to make a more confident decision.
x
xxfast
07/09/2023, 2:43 AMHi. Decompose-Router uses decompose under the hood and lets you keep all the navigation logic inside Composables themselves. Decompose-router meant to simplify use of decompose in a Compose-only project.
Should note that Decompose-router only really support child-stack navigation for now, so if you want other custom navigation models, i would go with Decompose too.
3 Views