simple-stack-compose-integration
compose-destinations
simple-stack-compose-integration | compose-destinations | |
---|---|---|
21 | 25 | |
102 | 3,061 | |
- | - | |
6.3 | 9.0 | |
9 months ago | 5 days ago | |
Kotlin | Kotlin | |
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.
simple-stack-compose-integration
-
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
-
simple-stack-compose-integration VS compose-navigation-reimagined - a user suggested alternative
2 projects | 4 Feb 2022
-
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.
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
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.)
voyager - 🛸 A pragmatic navigation library for Jetpack Compose
mapbox-navigation-android - Mapbox Navigation SDK for Android
navigation-compose-typed - Type-safe arguments for Jetpack Navigation Compose using Kotlinx.Serialization
Duo Navigation Drawer - A flexible, easy to use, unique drawer library for your Android project.
Decompose - Kotlin Multiplatform lifecycle-aware business logic components (aka BLoCs) with routing functionality and pluggable UI (Jetpack Compose, SwiftUI, JS React, etc.), inspired by Badoos RIBs fork of the Uber RIBs framework
Chip Navigation Bar - An android navigation bar widget
compose-navigation-reimagined - 🌈 Type-safe navigation library for Jetpack Compose
SlidingTutorial - Android Library for making animated tutorials inside your app
simple-stack - [ACTIVE] Simple Stack, a backstack library / navigation framework for simpler navigation and state management (for fragments, views, or whatevers).
Keyboard Dismisser - Dismiss your keyboard by tapping anywhere outside it.