Sesame VS workflow-kotlin

If you are looking for a paging library take a look at https://github.com/aartikov/Sesame/tree/master/sesame-loading

I use property delegate that wraps MutableStateFlow. This solution results in minimum of boilerplate code:

My Sesame-property is inspired by MobX. It provides observable mutable properties for core state and observable computed properties for derived state.

My library Sesame Activable works exactly as you described.

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

Hi. I have developed a library called Sesame.

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.

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.

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).

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.

There's kotlin workflow by square https://github.com/square/workflow-kotlin