Hey man... I appreciate this one-feature-tutorial videos, but I'd really love the app series. Specifically, I'd really like to know how you'd approach an app with a login feature which also has something like a bottom nav bar in the main app itself. I still haven't found an optimal way to go about this (navigation-wise).
I do think the next app I want to build would have a login screen and what not. But what is the issue you're running into? You should easily be able to have logic on all start that either pushes the user to a sign up/in Composable if they are signed out and then a "signed in screen" when they are authenticated. The signed in Composable would have the bottom nav at that point and the signed out state wouldn't. Alternatively, if you reeeeeaally needed to, you could have two activities if that is simpler for some reason.
@@TheAndroidFactory Yeah, I believe it is fairly easy to do with a bunch of when statements. However, I don't know how to approach the situation using purely Compose's Navigation Component. FYI the "signed in screen" that I'm using is a composable which uses the NavigationSuiteScaffold. I'm a beginner so I might just be totally missing something though 😛
@@TheAndroidFactory I meant no pressure it's just I love how professional your code and your explanation is will definitely build all your projects from now on...❤
good practice 🔥
Hey man... I appreciate this one-feature-tutorial videos, but I'd really love the app series. Specifically, I'd really like to know how you'd approach an app with a login feature which also has something like a bottom nav bar in the main app itself. I still haven't found an optimal way to go about this (navigation-wise).
I do think the next app I want to build would have a login screen and what not.
But what is the issue you're running into? You should easily be able to have logic on all start that either pushes the user to a sign up/in Composable if they are signed out and then a "signed in screen" when they are authenticated. The signed in Composable would have the bottom nav at that point and the signed out state wouldn't. Alternatively, if you reeeeeaally needed to, you could have two activities if that is simpler for some reason.
@@TheAndroidFactory Yeah, I believe it is fairly easy to do with a bunch of when statements. However, I don't know how to approach the situation using purely Compose's Navigation Component. FYI the "signed in screen" that I'm using is a composable which uses the NavigationSuiteScaffold. I'm a beginner so I might just be totally missing something though 😛
Woah interesting... I haven't worked with the suite scaffold you are talking about 🤔
good video, I have a question, is it a good idea to create textfield state and snapshotflow in a composable function?
We need more apps... Not just one app a season
I need more time haha 😅
@@TheAndroidFactory I meant no pressure it's just I love how professional your code and your explanation is will definitely build all your projects from now on...❤
I appreciate your support! All the code is on GitHub for you to consume as well :)
Please 😢 upload faster 😅
Hahaha thank you for the support!