compose-navigation-reimagined
FragNav
Our great sponsors
| compose-navigation-reimagined | FragNav | |
|---|---|---|
| 17 | 3 | |
| 524 | 1,493 | |
| - | - | |
| 7.4 | 0.0 | |
| 3 months ago | about 2 years ago | |
| Kotlin | Kotlin | |
| MIT License | - |
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.
compose-navigation-reimagined
-
Are Fragments in Android going to be deprecated in favor of Jetpack Compose?
Navigation Reimagined https://github.com/olshevski/compose-navigation-reimagined
- What do you use for compose navigation?
-
Compose Navigation Reimagined 1.4.0 released
Look at how deeplinks are converted into destinations/backstack here: https://github.com/olshevski/compose-navigation-reimagined/blob/main/sample/src/main/kotlin/dev/olshevski/navigation/reimagined/sample/ui/MainScreen.kt. It is all manual in comparison to the official Navigation Component, but I feel it gives developers much more control on the deeplink handling.
-
ViewModel: for UI business, not UI operations 😮
Compose navigation reimagined
-
4 reasons Jetpack Compose is better than XML
Using any of the 5 prominent community alternatives is a better approach (even though most people hoping to use the docs as if it was like, written for stable code, will muck around with their apps crashing if the user inputs a & symbol). I have this thing but I'd consider taking a look at https://github.com/adrielcafe/voyager or maybe https://github.com/olshevski/compose-navigation-reimagined
- Will Jetpack Compose Take Over XML?
-
Why using Navigation-Compose in your Jetpack Compose app is a bad idea
Also, I'll just leave it here: https://github.com/olshevski/compose-navigation-reimagined
- Show HN: Compose Navigation Reimagined – open-source library for Android
- Compose Navigation Reimagined
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?
voyager - 🛸 A pragmatic navigation library for Jetpack Compose
Duo Navigation Drawer - A flexible, easy to use, unique drawer library for your Android project.
Appyx - Model-driven navigation + UI components with gesture control for Compose Multiplatform
SlidingTutorial - Android Library for making animated tutorials inside your app
Cicerone - 🚦 Cicerone is a lightweight library that makes the navigation in an Android app easy.
Okuki - Okuki is a simple, hierarchical navigation bus and back stack for Android, with optional Rx bindings, and Toothpick DI integration.
Bubble Navigation - 🎉 [Android Library] A light-weight library to easily make beautiful Navigation Bar with ton of 🎨 customization option.
Alligator - Alligator is Android navigation library that will help to organize your navigation code in clean and testable way.
Dual-color-Polyline-Animation - This library will help to show the polyline in dual color similar as Uber.
Fragula - 🧛 Fragula is a swipe-to-dismiss extension for navigation component library for Android
Debug-Artist - Debug menu for happy android dev