workflow
Conductor
Our great sponsors
workflow | Conductor | |
---|---|---|
2 | 6 | |
1,103 | 3,896 | |
0.5% | 0.2% | |
3.3 | 3.9 | |
2 months ago | 8 days ago | |
Shell | 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.
workflow
-
Single Activity Apps: Fragments vs Views in 2022
Otherwise there's solutions like Squares Workflow that afaik support both View and Compose
-
Are there any 3rd party State Management libs for Jetpack Compose?
I've been playing around with Square's Workflow in a side project and have liked it a lot.
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?
molecule - Build a StateFlow stream using Jetpack Compose
Anvil - Minimal UI library for Android inspired by React
MVIKotlin - Extendable MVI framework for Kotlin Multiplatform with powerful debugging tools (logging and time travel), inspired by Badoo MVICore library
Kotgo - Create kotlin android project with one line of command.
riverpod - A reactive caching and data-binding framework. Riverpod makes working with asynchronous code a breeze.
RoboMVVM - MVVM framework for Android
compose-destinations - Annotation processing library for type-safe Jetpack Compose navigation with no boilerplate.
android-common - Android common lib, include ImageCache, HttpCache, DropDownListView, DownloadManager, Utils and so on
KotlinBloc - A predictable state management library for Kotlin and Jetpack Compose, using the BLoC design pattern.
droidparts
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
Elf Framework - Efl is an Android Framework to simplify the android development process