Makes absolute sense :) If you have separate (and uncoupled!) features, using Dependency Inversion for navigation (and any other (shared) dependencies they may rely on) is the way to go!
@fabiovokrri517Күн бұрын
That's exactly how the documentation tells you to develop navigation
@warTag6823 сағат бұрын
Golden content as always!
@grossadmiralthrawn87698 сағат бұрын
Interesting and good video.
@ngappsКүн бұрын
The same as shown in Now in Android google sample app
@TheMikkelet22 сағат бұрын
multi module is great in theory, but usually end up with giant core module (essentially an app in it self) and a few, small feature modules - too small to get benefit from compiler... mosty multimodule is good for data layer, like remote and/or local that you can use in any app your need
@CeisluckКүн бұрын
what if feature A or B have more than 1 screen, is a overkill to emulate navcontroller, then the options left is to pass down the naController or make a navhost inside feature A or B, wich is BS in a way to see it. But I am ok with what google is recommending in the nowInAndroid sample app
@ShivaPrasad-hm5lk5 сағат бұрын
I am making an app now using jetpack compose in which I have used single activity and then in each composable I have one or more apo calls called in coroutines foe sthis mean I am not doing a lot of work on main thread?
@shreyassathya374Күн бұрын
Great informative video on multi module, Is it possible to please make a video on Event Bus, and use case with a sample app, Thanks in advance.
@yuMYlylyКүн бұрын
Vielen Dank für dieses Video! Jetzt habe ich ein neues Hobby, nämlich lustige Videos zu finden und sie mit meinen Freunden zu teilen🍒
@unknownBoy85loverКүн бұрын
A worthy video thank you sir ❤
@TheFlexathКүн бұрын
thanks Philipp
@Tomas-g2j4f9 сағат бұрын
you should have feature level navigation files to make the navhost more readable this approach won't work if you have 50 screens
@grossadmiralthrawn87698 сағат бұрын
Does anyone know an Android library for the Matrix protocol.
@mikejawoski5904Күн бұрын
Is it possible to do shared element transition with multi module?
@PhilippLackner22 сағат бұрын
@@mikejawoski5904 of course
@AndrewDChristieКүн бұрын
Thanks!
@tiltedbybox611815 сағат бұрын
9:39 isn't that what you actually deleted? 😅
@baadrqaaba952918 сағат бұрын
Thats the point of using MMA
@tasnimulhasan7329Күн бұрын
Yeah that's the way google recommend 😊
@lale5767Күн бұрын
FYI philip I personally hate these kind of titles 'Why you'rr doing it wrong'. How are you aware of what I'm doing? Are you spying on me? 😂 Seriously though, I find it insulting and I'm sure I'm not the only one who finds it tacky.
@Mike-er2ihКүн бұрын
Clickbaitsssss
@PhilippLacknerКүн бұрын
Thanks for the feedback
@viniciussantosmachado4196Күн бұрын
I personally don't care if the content is good
@lale5767Күн бұрын
@@PhilippLackner anytime bro
@lale5767Күн бұрын
@@viniciussantosmachado4196 maybe if you're a heavy youtube uaer, it'll wear down on you after a while.
@SiamakAshrafi6 сағат бұрын
You should never pass anything complex to your Composable. It should be side effect free and stateless. The ViewModel should do all the work ... so this is obvious :-) Thanks
@PhilippLackner5 сағат бұрын
@@SiamakAshrafi if you're a beginner this is everything but obvious 😄
@SiamakAshrafi5 сағат бұрын
@@PhilippLackner Don't tell us we are doing it wrong!!! We have been doing it this way from day one ... 👎🏾