A modern programming language that makes developers happier.

kotlinlang

found this <https://www.youtube.com/watch?v=Rc-1TAUNX_0|great talks> from Luca Nicoletti, the sample shown using orbit earlier version with alpha version of jetpack compose

<https://github.com/orbit-mvi/orbit-mvi/tree/main/samples|Stocklist, Post &amp; Calculator> seems using Views, cmiiw if there’s a sample on v3.1.1 using Jetpack Compose already that I’m not aware of :pray:

No sample yet, it’s on our to-do list :slightly_smiling_face:

<https://github.com/orbit-mvi/orbit-mvi/issues/10>

There’s not much to it though, you use `Container.stateFlow.consumeAsState()`

I’m creating the sample at the moment, although as mikolaj mentions consuming it isn’t much of a problem. Converting the whole of the UI to Compose is taking me the time :rolling_on_the_floor_laughing:

Agreed, migrating the old Views to Jetpack Compose was the time consuming :laughing:

Been using this samples as references:

1. <https://github.com/uniflow-kt/uniflow-kt/blob/master/doc/compose.md>
2. <https://codingtroops.com/android/compose-architecture-part-1-mvvm-or-mvi-architecture-with-flow/>

I just played with uniflow myself today, what was your impression <@U5HHHHBAM>?

IMHO, The `uniflow` maintainer seems a bit outdated atm. Also it's seems not KMM ready due to coupled with `LiveData` afaik. 

&gt; Didn't catch up with the library in this few months. 
&gt; 
Their documentation (README) &amp; samples was good for starter (they forked <https://github.com/uniflow-kt/compose-samples/tree/uniflow/Jetsurvey|official> jetpack composs) 

Also the parallel or <https://www.github.com/uniflow-kt/uniflow-kt/tree/master/doc%2Fmultiple_streams.md|multiple stream> supported by their API

Yeah the docs are nice, very easy to follow.  It’s something we’re looking to improve on ourselves. At the moment <@UPWE6PJCE> is working on publishing what we’ve got to a better looking website but there are no doubt plenty of things missing too. 

Not sure how I feel about multiple streams! It’s too easy to slip back into the pattern of these being tightly coupled as they often were when using live data in MVVM in the first place, but perhaps I’m missing something. 