compose-destinations
voyager
Our great sponsors
compose-destinations | voyager | |
---|---|---|
25 | 11 | |
2,995 | 2,115 | |
- | - | |
9.0 | 8.1 | |
16 days ago | 3 days ago | |
Kotlin | Kotlin | |
Apache License 2.0 | 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-destinations
- What do you use for compose navigation?
-
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?
https://composedestinations.rafaelcosta.xyz/ I use this
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
voyager
- Are Fragments in Android going to be deprecated in favor of Jetpack Compose?
-
Why compose multiplatform don't get more popular?
If I were to start a project right now, I'd use https://github.com/adrielcafe/voyager although, it doesn't support Web Canvas or iOS yet I don't think.
-
Which navigation library for compose do you suggest?
Voyager has some bugs (apparently SavedStateHandle doesn't work and the PR is open since Nov 24), Appyx is nice but I hear it's laggy (but honestly, everything in Compose is laggy all the time, so if you use Compose, that's pretty standard tbh), I don't know enough about Navigation-Reimagined to tell you, Compose-Destinations is a codegenerator over Navigation-Compose so you drag in Accompanist-Navigation to have basic screen transitions which is pre-alpha tech.
-
ViewModel: for UI business, not UI operations 😮
Voyager
-
voyager VS Appyx - a user suggested alternative
2 projects | 19 Sep 2022
-
What's the Current State of Android Developmentâ„¢?
https://github.com/adrielcafe/voyager/issues/42 open since January
-
The State of Navigation in Jetpack Compose
I recently tried Voyager, and unfortunately I ran into this issue: https://github.com/adrielcafe/voyager/issues/42
Yes, I've checked (it doesn't). I've also read AndroidScreenLifecycleOwner's source code, and I don't see a way for it to ever go to the ON_PAUSE state.
-
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
-
voyager VS compose-navigation-reimagined - a user suggested alternative
2 projects | 4 Feb 2022
What are some alternatives?
Decompose - Kotlin Multiplatform lifecycle-aware business logic components (aka BLoCs) with routing (navigation) and pluggable UI (Jetpack Compose, SwiftUI, JS React, etc.)
compose-navigation-reimagined - 🌈 Type-safe navigation library for Jetpack Compose
PreCompose - Compose Multiplatform Navigation && State Management
navigation-compose-typed - Type-safe arguments for Jetpack Navigation Compose using Kotlinx.Serialization
compose-shared-element - Experiment with SharedElement transition in Jetpack Compose, inspired by Flutter Hero widget.
mapbox-navigation-android - Mapbox Navigation SDK for Android
Duo Navigation Drawer - A flexible, easy to use, unique drawer library for your Android project.
Chip Navigation Bar - An android navigation bar widget
SlidingTutorial - Android Library for making animated tutorials inside your app
compose-richtext - A collection of Compose libraries for advanced text formatting and alternative display types.
Keyboard Dismisser - Dismiss your keyboard by tapping anywhere outside it.
FragNav - An Android library for managing multiple stacks of fragments