compose-destinations
simple-stack
Our great sponsors
compose-destinations | simple-stack | |
---|---|---|
25 | 40 | |
3,048 | 1,353 | |
- | - | |
9.0 | 5.8 | |
28 days ago | 9 months ago | |
Kotlin | Java | |
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.
compose-destinations
- What do you use for compose navigation?
-
jetpack navigation(https://github.com/raamcosta/compose-destinations) with activity
This time is about navigation, when raamcosta ( https://github.com/raamcosta/compose-destinations) in jetpack compose
-
Compose only apps question
The biggest help of all by far was Compose Destinations. It takes away all the boilerplate of maintaining your routes. A simple way to not have to create all those routes yourself with placeholders etc, including deeplink patterns and all. It generates all of that for you in a typesafe way. Just check the basic example on GitHub or the dedicated documentation website.
-
How do you deal with complex nested navigation in Jetpack Compose?
Here is a great solution for navigation in compose. Actually this is what Google should have done in the first place https://github.com/raamcosta/compose-destinations
- New app: xml or compose?
-
Pure Compose Navigation
Compose destinations is another alternative: https://github.com/raamcosta/compose-destinations
-
A Type-safe extension library for the Compose Navigation library
Hey, thanks for sharing here. Do you mind sharing how exactly this library is different from this one https://github.com/raamcosta/compose-destinations and why one would use one over the other?
-
Single Activity Apps: Fragments vs Views in 2022
I don't have much experience with conductor, so I'm curious what your concerns about lifecycle is lacking compared to fragments? But if your team already knows that framework I might just stick with views over fragments. I see there is a compose integration if you do ever plan on picking that up with conductor. Otherwise compose makes fragments obsolete and your team already knows conductor. I do agree the navigation story in compose is not mature especially after jetpack compose navigation. But there are other 3rd party libraries like compose destinations or decompose, but would be nice to see something better 1st party.
-
Which navigation library for compose do you suggest?
I can't recommend the vanilla compose navigation from Google, but the community has built others like compose destinations which is pretty good.
-
ViewModel: for UI business, not UI operations 😮
Compose Destinations
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?
voyager - 🛸 A pragmatic navigation library for Jetpack Compose
FragNav - An Android library for managing multiple stacks of fragments
mapbox-navigation-android - Mapbox Navigation SDK for Android
Enro - A simple navigation library for Android 🗺️
Duo Navigation Drawer - A flexible, easy to use, unique drawer library for your Android project.
TabSync - An Android lightweight synchronizer between Tabs and Lists. Available for Views and Jetpack Compose.
Chip Navigation Bar - An android navigation bar widget
accompanist - A collection of extension libraries for Jetpack Compose
SlidingTutorial - Android Library for making animated tutorials inside your app
guide-to-kotlin - [GUIDE] This tutorial assumes all you know is Java, but you want to learn Kotlin.
Keyboard Dismisser - Dismiss your keyboard by tapping anywhere outside it.
BottomNavChildFragmentExample - An example showing how to use bottom navigation with child fragments.