workflow-kotlin
A Swift and Kotlin library for making composable state machines, and UIs driven by those state machines. (by square)
Sesame
Android architecture components made right (by aartikov)
Our great sponsors
workflow-kotlin | Sesame | |
---|---|---|
9 | 7 | |
977 | 109 | |
0.8% | - | |
9.2 | 0.0 | |
7 days ago | about 2 years ago | |
Kotlin | Kotlin | |
Apache License 2.0 | MIT License |
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.
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
Sesame
Posts with mentions or reviews of Sesame.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-04-14.
-
Do you guys feel like Jetpack Paging3 library messes with your Architecture a lot?
If you are looking for a paging library take a look at https://github.com/aartikov/Sesame/tree/master/sesame-loading
-
What's your way to expose an immutable StateFlow / LiveData from your ViewModel without bloating up your code?
I use property delegate that wraps MutableStateFlow. This solution results in minimum of boilerplate code:
-
Why is there nothing like Redux, Vuex, MobX, etc... for Android?
My Sesame-property is inspired by MobX. It provides observable mutable properties for core state and observable computed properties for derived state.
-
A safer way to collect flows from Android UIs
My library Sesame Activable works exactly as you described.
-
Sesame - Android architecture library
Sesame has a navigation component. But this one is supposed to be minimalistic. While Alligator has all the navigation implementation out of the box (passing screen arguments, controlling fragment backstack, animations and so on) Sesame provides only a way to deliver navigation messages. Both approaches has cons and pros. I personally will start my new project with Sesame navigation and copy-pasting some simple navigator like that FragmentNavigator.kt
-
Sesame - Android architecture components made right
Hi. I have developed a library called Sesame.
What are some alternatives?
When comparing workflow-kotlin and Sesame you can also consider the following projects:
mobius - A functional reactive framework for managing state evolution and side-effects.
MVICore - MVI framework with events, time-travel, and more
Flow - Name UI states, navigate between them, remember where you've been.
compose-samples - Official Jetpack Compose samples.
architecture-components-samples - Samples for Android Architecture Components.
orbit-mvi - A simple MVI framework for Kotlin Multiplatform and Android
MobX - Simple, scalable state management.
mobx - Kotlin MobX implementation