Android-MultiStacks
simple-stack
| Android-MultiStacks | simple-stack | |
|---|---|---|
| 1 | 40 | |
| 30 | 1,354 | |
| - | - | |
| 10.0 | 5.8 | |
| over 3 years ago | 9 months ago | |
| Kotlin | Java | |
| - | 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.
Android-MultiStacks
simple-stack
-
Why so many people are quitting Android development
As someone who had been using single-activity since 2015 (a'la Flow) and eventually just rewrote the whole thing to fix all the bugs we had with it in 2017, I find it sad that the single-activity approach was questioned not because it was harder, but because people made their own lives harder. And then Google made their lives harder.
-
Passing context to a UseCase class inside the domain module
I've been using single-activity but with Simple-Stack since 2016 and never deprecated it because Navigation just has these quirks that impede you a lot. I know how to use it but wouldn't really pick it.
-
Does anyone know hows Fragment lifecycle work in NavHostFragment (Bottom Navigation Views Activity)?
This is why we've been using https://github.com/Zhuinden/simple-stack and it was never deprecated. We've been using it for 6 years, I'd say there was a critical bug but it was fixed in 2.3.1...
-
Can we all please settle on one
I mean, we use Simple-Stack because it makes things easier, if it didn't we'd have ditched it long ago https://github.com/Zhuinden/simple-stack
-
What do you use for compose navigation?
Agreed. I also added support for it 2 weeks ago.
-
How do you deal with complex nested navigation in Jetpack Compose?
I don't, because we use this and it's better than activities+intents 😅
-
Am I the only one who feels that Google's "new stuff" approach is badly hurting productivity?
We've been making single activity apps with https://github.com/Zhuinden/simple-stack and it has been easier than multi-activity.
-
Guia - Jetpack Compose Navigation
I still use https://github.com/Zhuinden/simple-stack to this day, although I still use it with fragments.
-
Single Activity Apps: Fragments vs Views in 2022
I have been using Fragments instead of compound viewgroups lately with simple-stack as the navigator for the single-activity, although I need to figure out how to switch to use onBackPressed+onBackInvokedCallback and not just onBackPressed.
-
Architecture: How to inject/provide dependencies to custom ViewGroups
You can think of Simple-Stack as a direct successor of Mortar+Flow.
What are some alternatives?
android-multibackstack - Persistent bottom navigation like in instagram
FragNav - An Android library for managing multiple stacks of fragments
Enro - A simple navigation library for Android 🗺️
TabSync - An Android lightweight synchronizer between Tabs and Lists. Available for Views and Jetpack Compose.
accompanist - A collection of extension libraries for Jetpack Compose
guide-to-kotlin - [GUIDE] This tutorial assumes all you know is Java, but you want to learn Kotlin.
BottomNavChildFragmentExample - An example showing how to use bottom navigation with child fragments.
sunflower - A gardening app illustrating Android development best practices with migrating a View-based app to Jetpack Compose.
Conductor - A small, yet full-featured framework that allows building View-based Android applications
scene - Android Single Activity Applications framework without Fragment.
material-dialogs - 😍 A beautiful, fluid, and extensible dialogs API for Kotlin & Android.
kotlin-result - A multiplatform Result monad for modelling success or failure operations.