Kotgo
Conductor
Our great sponsors
| Kotgo | Conductor | |
|---|---|---|
| 0 | 6 | |
| 1,599 | 3,895 | |
| - | 0.1% | |
| 0.0 | 3.9 | |
| about 3 years ago | 6 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.
Kotgo
We haven't tracked posts mentioning Kotgo yet.
Tracking mentions began in Dec 2020.
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.
The last enterprise level app we put together was in 2018; we chose to go with Conductor and run with custom views and minimal activities. The codebase has been a pleasure to maintain and apart from some boilerplate here and there, a Single Activity, Multiple View app has filled all our requirements.
-
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).
- 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?
Moxy - Moxy is MVP library for Android
Anvil - Minimal UI library for Android inspired by React
android-priority-jobqueue - A Job Queue specifically written for Android to easily schedule jobs (tasks) that run in the background, improving UX and application stability.
Small - A small framework to split app into small parts
RoboMVVM - MVVM framework for Android
SQLDelight - SQLDelight - Generates typesafe Kotlin APIs from SQL
android-common - Android common lib, include ImageCache, HttpCache, DropDownListView, DownloadManager, Utils and so on
droidparts
apf - Android Plugin Framework
ACDD
RoboBinding - A data-binding Presentation Model(MVVM) framework for the Android platform.
legend - A framework for hook java methods.