Jetpack-Navigation-Multistack-Example
Enro
Jetpack-Navigation-Multistack-Example | Enro | |
---|---|---|
4 | 5 | |
38 | 242 | |
- | - | |
0.0 | 8.9 | |
over 1 year ago | 8 days 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
Enro
-
Android navigation with multiple back stacks
Enro
-
Thoughts about it? π€
I also have to try enro, but I don't have time right now to give it a try.
-
Jetpack Navigation and cross-nav graph destinations
You can find my library here: https://github.com/isaac-udy/Enro
-
What are the pros of going with Jetpack's Navigation Component?
So far i'm using Enro, it work really really well and it's much more readable for me: https://github.com/isaac-udy/Enro
-
I came up with a design to reuse some UI and behaviours between a couple of search features in a app I was working on and I would like to share it here
I'd be interested on your thoughts of the library I've been working on, and how it compares to the solution you've mentioned. The library is based around an annotation processor to handle passing arguments, receiving results from other screens and performing navigation. It's called Enro, check it out here https://github.com/isaac-udy/Enro
What are some alternatives?
android-showcase - π Android application following best practices: Kotlin, Coroutines, JetPack, Clean Architecture, Feature Modules, Tests, MVVM, DI, Static Analysis...
simple-stack - [ACTIVE] Simple Stack, a backstack library / navigation framework for simpler navigation and state management (for fragments, views, or whatevers).
simple-stack-ftue-sample - [DEMO] Sample code to display "First-Time User Experience" in a Single-Activity app using Simple-Stack, based on the "Conditional Navigation" section by Google.
FragNav - An Android library for managing multiple stacks of fragments
BottomNavChildFragmentExample - An example showing how to use bottom navigation with child fragments.
android-template - Project with various common components, to reduce "project setup" operations
android-multibackstack - Persistent bottom navigation like in instagram