Conductor
A small, yet full-featured framework that allows building View-based Android applications (by bluelinelabs)
workflow-kotlin
A Swift and Kotlin library for making composable state machines, and UIs driven by those state machines. (by square)
| Conductor | workflow-kotlin | |
|---|---|---|
| 6 | 9 | |
| 3,896 | 985 | |
| 0.1% | 1.4% | |
| 3.9 | 9.1 | |
| 24 days ago | 6 days ago | |
| Java | Kotlin | |
| Apache License 2.0 | Apache License 2.0 |
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.
Conductor
Posts with mentions or reviews of Conductor.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-06.
-
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?
workflow-kotlin
Posts with mentions or reviews of workflow-kotlin.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-02.
-
Flow or RxJava
For example square has open sourced workflow https://github.com/square/workflow-kotlin (MVI + plugin based architecture), if you look other examples like molecule they use Presenters (not the MVP ones) which is completly different. The only common thing is that they are both UDF.
-
What libraries would you use if you were starting a new project?
workflow. Quite a shift in how you write an app, but enough extension points that it's not that much of an issue, and it's really pleasant to use.
-
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).
- Released workflow v1.0.0
-
Tap Response Time: Jetpack Navigation 🗺
We'll focus on Jetpack Navigation here, however most of the content applies for any navigation library or tap action. In fact, I first implemented this at Square on top of Flow and Workflow.
-
Why is there nothing like Redux, Vuex, MobX, etc... for Android?
There's kotlin workflow by square https://github.com/square/workflow-kotlin
What are some alternatives?
When comparing Conductor and workflow-kotlin you can also consider the following projects:
Anvil - Minimal UI library for Android inspired by React
mobius - A functional reactive framework for managing state evolution and side-effects.
Kotgo - Create kotlin android project with one line of command.
Flow - Name UI states, navigate between them, remember where you've been.
RoboMVVM - MVVM framework for Android
architecture-components-samples - Samples for Android Architecture Components.
android-common - Android common lib, include ImageCache, HttpCache, DropDownListView, DownloadManager, Utils and so on
MVICore - MVI framework with events, time-travel, and more
droidparts
orbit-mvi - A simple MVI framework for Kotlin Multiplatform and Android
Elf Framework - Efl is an Android Framework to simplify the android development process
mobx - Kotlin MobX implementation
Conductor vs Anvil
workflow-kotlin vs mobius
Conductor vs Kotgo
workflow-kotlin vs Flow
Conductor vs RoboMVVM
workflow-kotlin vs architecture-components-samples
Conductor vs android-common
workflow-kotlin vs MVICore
Conductor vs droidparts
workflow-kotlin vs orbit-mvi
Conductor vs Elf Framework
workflow-kotlin vs mobx