Jetpack-Navigation-Multistack-Example
simple-stack-ftue-sample
Our great sponsors
| Jetpack-Navigation-Multistack-Example | simple-stack-ftue-sample | |
|---|---|---|
| 4 | 2 | |
| 38 | 27 | |
| - | - | |
| 0.0 | 4.3 | |
| over 1 year ago | 9 months ago | |
| Kotlin | Kotlin | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Jetpack-Navigation-Multistack-Example
-
Question about placing fragments in nav-graph when using navigation component
If you DON'T actually rely on the multi-stack behavior (1 stack / tab) then there is no need to use NavigationExtensions (personally I wouldn't use them even if I needed that, because the implementation is a bit wonky; you can do more reliable code manually.)
-
A fragment -> auth flow-> bottom navigation w/ Navigation component/jetpack
See this sample for auth / conditional navigation then pretend that "ProfileFragment" is the fragment in this sample
-
What are the pros of going with Jetpack's Navigation Component?
I am managing multiple backstacks with Jetpack Navigation just fine in this example https://github.com/Zhuinden/Jetpack-Navigation-Multistack-Example/tree/master/app/src/main/java/com/zhuinden/jetpacknavbottomnavfragmentexample 🤔
- BottomNavigation replace fragment
simple-stack-ftue-sample
-
LiveData vs SharedFlow and StateFlow in MVVM and MVI Architecture
A simplified variation can be seen in this repo, a LiveData variant with Jetpack stuff can be seen in this repo, my issue with this sample is that as there is no input + debounce + filter + async data load example in it, there is no switchMap (and even for combineTuple, I can use my other helper validateBy here), and those would be key to understanding the difference in terms of expressibility and power...
-
A fragment -> auth flow-> bottom navigation w/ Navigation component/jetpack
See this sample for auth / conditional navigation then pretend that "ProfileFragment" is the fragment in this sample
What are some alternatives?
android-showcase - 💎 Android application following best practices: Kotlin, Coroutines, JetPack, Clean Architecture, Feature Modules, Tests, MVVM, DI, Static Analysis...
android-template - Project with various common components, to reduce "project setup" operations
Enro - A simple navigation library for Android 🗺️
jetpack-navigation-ftue-sample - [DEMO] Sample code to display "First-Time User Experience" in a Single-Activity app using Jetpack-Navigation, NavGraphs, Dagger, SavedStateHandle, Hilt, and EventEmitter - based on the FTUE example code in simple-stack-tutorials, but originally described by Google.
BottomNavChildFragmentExample - An example showing how to use bottom navigation with child fragments.
live-event - [ACTIVE] Lifecycle-aware wrapper over EventEmitter, for modelling one-off events.
event-emitter - [ACTIVE] The event emitter allows you to register multiple observers, but enqueue events while there are no observers.
android-template - Android app starter template