simple-stack-compose-integration
[ACTIVE/BETA] Compose integration for Simple-Stack. (by Zhuinden)
navigation-compose-typed
Type-safe arguments for Jetpack Navigation Compose using Kotlinx.Serialization (by kiwicom)
| simple-stack-compose-integration | navigation-compose-typed | |
|---|---|---|
| 21 | 6 | |
| 103 | 238 | |
| 0.0% | 0.4% | |
| 3.5 | 0.0 | |
| 6 months ago | 4 days ago | |
| Kotlin | Kotlin | |
| Apache License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
simple-stack-compose-integration
Posts with mentions or reviews of simple-stack-compose-integration.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-03.
-
The navigation compose library is the most confusing thing I've tried to learn in a while.
Yup, that's why we're working on https://github.com/Zhuinden/simple-stack-compose-integration/ to make it as simple as backstack.goTo(SomeScreenKey(arg1, arg2)) instead of this navController.navigateTo("some/screen&arg1=${UrlEncoder.encode(arg1.toBase64())} stuff. If you are working on an Android app that will always be on Android-only, why would you inherit limitations from Kotlin Multi-platform?
-
Should I use fragments with Jetpack Compose?
We have https://github.com/Zhuinden/simple-stack-compose-integration/ but the fact that I'd normally prefer to use fragments kinda holds it back
-
Are Fragments in Android going to be deprecated in favor of Jetpack Compose?
Simple-Stack-Compose https://github.com/Zhuinden/simple-stack-compose-integration
-
What do you use for compose navigation?
However, it's worth noting that thanks to a guy named @matejdro we are working on a pure-Compose version, in which setup has been reduced to
-
ViewModel: for UI business, not UI operations 😮
And ,yes, although not being made for Compose, also Simple stack :)
-
What's the Current State of Android Development™?
i'd love to recommend simple-stack-compose-integration but i never wrote this missing link
-
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
-
How to migrate an existing app to compose?
If you're deadset on full compose navigation I'd check out Zhuinden`s simple-stack-compose-integration
-
What is the thing you most struggle with when using Jetpack Compose?
I'm almost tempted to use multiple ComposeViews, but I'm definitely not using 1 ComposeView N composables any time soon, even though technically I have the code to support it.
-
java.lang.IllegalStateException: You cannot access the NavBackStackEntry's ViewModels until it is added to the NavController's back stack
Yea I also have https://github.com/Zhuinden/simple-stack-compose-integration but I saw that I really need to put in the work to have the LocalLifecycleOwner etc set up for a given key 🤔
navigation-compose-typed
Posts with mentions or reviews of navigation-compose-typed.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-03.
- Should I use fragments with Jetpack Compose?
-
Are Fragments in Android going to be deprecated in favor of Jetpack Compose?
You can use this lib which is build on top on navigation compose https://github.com/kiwicom/navigation-compose-typed. Its strong typed
-
What do you use for compose navigation?
Official navigation compose but strong typed https://github.com/kiwicom/navigation-compose-typed
-
Compose only apps question
I'd personally definitely go with compose only, use androidx.navigation and use this https://github.com/kiwicom/navigation-compose-typed to give me the convenience of not having to make the type safe destinations myself. It's a great middle addition to the library from my experience. Oh and for now you'd also need to bring in accompanist navigation for animation support, but that's very straightforward too.
What are some alternatives?
When comparing simple-stack-compose-integration and navigation-compose-typed you can also consider the following projects:
safer-navigation-compose - Type-safe extension library for the official Jetpack Compose Navigation library with Serializable data classes support. [GET https://api.github.com/repos/uragiristereo/safer-navigation-compose: 404 - Not Found // See: https://docs.github.com/rest/repos/repos#get-a-repository]
navigator - A small navigation library for Android to ease the use of fragment transactions & handling backstack (also available for Jetpack Compose).
voyager - 🛸 A pragmatic navigation library for Compose Multiplatform
simple-stack - [ACTIVE] Simple Stack, a backstack library / navigation framework for simpler navigation and state management (for fragments, views, or whatevers).
accompanist - A collection of extension libraries for Jetpack Compose