Decompose
simple-stack-compose-integration
Our great sponsors
Decompose | simple-stack-compose-integration | |
---|---|---|
20 | 21 | |
1,931 | 102 | |
- | - | |
9.2 | 6.3 | |
10 days ago | 8 months 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.
Decompose
-
What do you use for compose navigation?
I use Decompose, although I also have a kmp project which that supports. I find the compose extensions providing a very easy API when integrating with compose.
-
Anyone here who uses compose-multiplatform for desktop apps, what’s your feedback?
For one of our apps we used https://arkivanov.github.io/Decompose/ for navigation. It is mentioned in the Compose Multiplatform repo, but we found it pretty obscure to use and it has some confusing concepts built in.
-
Does View Model works with Compose?
View model is Googles recommended approach, but there are other approaches out their you can use like decompose
-
KMM: writing Kotlin API for Swift - 7 things you need to know.
When you are building your app in KMM, sometimes you need to pack some libraries along with project files in the shared module. For example if you are using Decompose you need to access it's Value class in Swift.
-
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 personally like decompose for its testability, clear separation of concerns, and apis for compose animations. Plus it's multiplatform so you can use it for other kmp targets.
-
Is MVI way to go for new applications with compose
Full discretion, all my new apps are built using mvi with MVIKotlin and decompose for the compose extensions for navigation animations. A sample project I have built with that architecture can be found here.
-
Decompose VS appyx - a user suggested alternative
2 projects | 30 Aug 2022
-
Appyx - Application mechanics for your Android apps, built on top of Jetpack Compose (Navigation)
Check out Decompose, it's multiplatform - https://github.com/arkivanov/Decompose
-
Received a job offer letter with "All inventions developed by you during your period of employment with the Company will be deemed as the property of the Company." Its a Web dev job. How would this affect my mobile app dev hobby. I occasionally publish apps/games to PlayStore.
Decompose
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.
What are some alternatives?
voyager - 🛸 A pragmatic navigation library for Jetpack Compose
PreCompose - Compose Multiplatform Navigation && State Management
navigation-compose-typed - Type-safe arguments for Jetpack Navigation Compose using Kotlinx.Serialization
Appyx - Model-driven navigation + UI components with gesture control for Compose Multiplatform
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
koin - Koin - a pragmatic lightweight dependency injection framework for Kotlin & Kotlin Multiplatform
compose-destinations - Annotation processing library for type-safe Jetpack Compose navigation with no boilerplate.
Kotlin-Multiplatform-Libraries - Kotlin Multiplatform Libraries. Welcome PR if you find or create new Kotlin Multiplatform Library.
simple-stack - [ACTIVE] Simple Stack, a backstack library / navigation framework for simpler navigation and state management (for fragments, views, or whatevers).
compose-samples - Official Jetpack Compose samples.
compose-navigation-reimagined - 🌈 Type-safe navigation library for Jetpack Compose