Enro
FragNav
Our great sponsors
| Enro | FragNav | |
|---|---|---|
| 5 | 3 | |
| 241 | 1,493 | |
| - | - | |
| 9.0 | 0.0 | |
| about 1 month ago | about 2 years ago | |
| Kotlin | Kotlin | |
| 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.
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
FragNav
- Does navigation component require more workarounds compared to fragmentmanager?
-
Example for restoring data when navigating to previous fragment using navigation component.
I use fragNav for most of project.
-
Thoughts about it? 🤔
I think it's a fairly complex app, ~100 screens with a lot of custom transitions/animation and I'm still using dagger-android with custom scoping 😅. I would say before dagger hilt the nav library was pretty rough to use, we had to use a lot of dirty workarounds and nested fragments to get desired behavior. Right now it's in a really good spot. My biggest issues now are with how the IDE editor works; it can be really annoying about edge case features (like graph level args) and it inhales memory. I think alternatives like fragNav are much better for smaller projects.
What are some alternatives?
simple-stack - [ACTIVE] Simple Stack, a backstack library / navigation framework for simpler navigation and state management (for fragments, views, or whatevers).
Duo Navigation Drawer - A flexible, easy to use, unique drawer library for your Android project.
Jetpack-Navigation-Multistack-Example - [DEMO] An example using Jetpack Navigation and bottom nav multi-stack using child fragments.
SlidingTutorial - Android Library for making animated tutorials inside your app
android-showcase - 💎 Android application following best practices: Kotlin, Coroutines, JetPack, Clean Architecture, Feature Modules, Tests, MVVM, DI, Static Analysis...
Okuki - Okuki is a simple, hierarchical navigation bus and back stack for Android, with optional Rx bindings, and Toothpick DI integration.
android-multibackstack - Persistent bottom navigation like in instagram
Bubble Navigation - 🎉 [Android Library] A light-weight library to easily make beautiful Navigation Bar with ton of 🎨 customization option.
Dual-color-Polyline-Animation - This library will help to show the polyline in dual color similar as Uber.
Debug-Artist - Debug menu for happy android dev
RecyclerTabLayout - An efficient TabLayout library implemented with RecyclerView.
PagerSlidingTabStrip - An interactive indicator to navigate between the different pages of a ViewPager