I REALLY DON'T UNDERSTAND THE HIGH COMPLEXITY OF THIS COMPOSE LIB. Navigation lib looks like it was designed by a web developer. I feel so dissapointed by this, I have to use activities + fragments and then compose in order to make decent navigation......
@martinseal1987
Жыл бұрын
Simple stack for the win
@ArturoDevA
Жыл бұрын
same opinion, with xml is perfect
@Zhuinden
Ай бұрын
@@martinseal1987 glad to hear you are happy with simple-stack :)
@Zhuinden
23 күн бұрын
@Ceisluck
23 күн бұрын
@@Zhuinden hahaha this is very opinionated answer don't you think?
@timothypaetz222
Жыл бұрын
You keep using the word "type safe". I don't think that word means what you think it means (Princess Bride reference)... Wrapping untyped code (compose navigation) with our own APIs does not make something type safe. If we incorrectly write our type safe APIs with non type safe navigation compose then our code blows up at runtime which is why devs prefer actual type safe code so it does not compile instead and we can fix the issue before shipping our app to prod.
@martinseal1987
2 жыл бұрын
Wasn't the whole point of the navigation component that we didn't potentially make a mistake while using fragment transactions? Seems it now has a lot more space for making mistakes
@yousefbeiruty6417
2 жыл бұрын
I prefer to use the raamcosta/compose-destinations is better for handling navigation from one compose to another.
@WarwickHunter
Жыл бұрын
Very useful. It helped me understand and restructure my first attempt at Compose Navigation.
@SiamakAshrafi
2 жыл бұрын
Thanks for providing this. Super dense with lots of info and after watching this 100 times ... Tip #5: need to study the Now In Android code sample to understand how to exactly do this ... Also wondering when adding Navgraph if Android Studio can help make sure we setup with best practices ???
@johnshepard1267
Жыл бұрын
Untul now 3rd party libraries like Compose Destination does the job a lot better. Would be nice if Google complitely reinvented or also build something on top of the existing navigation for compose which will make it's usage as easy as it was with fragments and Navigation Component!
@conorsmall1373
Жыл бұрын
If that library stops getting supported we're all screwed
@USS_Daedalus
Жыл бұрын
@@conorsmall1373 or got hacked or infected by malicious code or so.
@dleonardo3238
7 ай бұрын
what about voyager?
@marlonlom
2 жыл бұрын
Thats a great content for checking the navgraph in multi-module android apps... one question is: how is handled the nested navgraph when talking to dynamic feature modules?
@ruhy99
9 ай бұрын
im interested on that, do you have any news?
@DouglasQueirozLima
Жыл бұрын
The documentation is down
@tashi7160
Жыл бұрын
great to see Ian no longer talking about fragment.
@Vihor95
Жыл бұрын
Way too complicated.
@kleeenco
8 ай бұрын
the code on the slide at 3:49 is invalid kotlin?
@erik9035
Жыл бұрын
This is still not type safe
@heshansandeepa9471
3 ай бұрын
Nice
@legui444532
9 ай бұрын
this library obligates you build your app like a website
Пікірлер: 26