Decompose
Conductor
Our great sponsors
Decompose | Conductor | |
---|---|---|
20 | 6 | |
1,946 | 3,896 | |
- | 0.2% | |
9.2 | 3.9 | |
8 days ago | 12 days 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.
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
Conductor
-
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.
-
Reddit Recap: State of Mobile Platforms Edition (2022)
We aren't doing anything specific for Compose. The majority of our screens are still written in Views and we need to ensure we have interoperability to navigate to and from screens written with either UI layer. All of our screens, whether based on Views or Compose, use the same navigation library, Conductor.
-
Single Activity architecture with custom views. Common pattern or anti-pattern?
I don't know how common/popular it actually is, but it's definitely not uncommon. Square has been doing this kind of home-made navigation for quite a while as far as I know (most recently in the form of workflow-kotlin), Lyft (Scoop) as well, and more (e.g. Conductor).
-
Is reddit android app Native or react-native?
Pretty sure it's native and they were mentioning they use Conductor instead of official activity/fragment solutions in some post.
- What are the current best alternative libraries to Jetpack Navigation Component which preserve state and backstack and work with Bottom Navigation?
What are some alternatives?
voyager - 🛸 A pragmatic navigation library for Jetpack Compose
Anvil - Minimal UI library for Android inspired by React
PreCompose - Compose Multiplatform Navigation && State Management
Kotgo - Create kotlin android project with one line of command.
Appyx - Model-driven navigation + UI components with gesture control for Compose Multiplatform
RoboMVVM - MVVM framework for Android
koin - Koin - a pragmatic lightweight dependency injection framework for Kotlin & Kotlin Multiplatform
android-common - Android common lib, include ImageCache, HttpCache, DropDownListView, DownloadManager, Utils and so on
Kotlin-Multiplatform-Libraries - Kotlin Multiplatform Libraries. Welcome PR if you find or create new Kotlin Multiplatform Library.
droidparts
compose-samples - Official Jetpack Compose samples.
Elf Framework - Efl is an Android Framework to simplify the android development process