Our very own @appmattus did a review of competing MVI libraries and has come up with some interesting conclusions. Well worth a read! https://proandroiddev.com/top-android-mvi-libraries-in-2021-de1afe890f27

Hello, it seems like the version 4.2.0 is not yet available

> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find org.orbit-mvi:orbit-core:4.2.0.
     Searched in the following locations:
<https://dl.google.com/dl/android/maven2/org/orbit-mvi/orbit-core/4.2.0/orbit-core-4.2.0.pom>
<https://repo.maven.apache.org/maven2/org/orbit-mvi/orbit-core/4.2.0/orbit-core-4.2.0.pom>
<https://jcenter.bintray.com/org/orbit-mvi/orbit-core/4.2.0/orbit-core-4.2.0.pom>

I want to have something like that sealed class ProfileViewState object Loading : ProfileViewState() object Error : ProfileViewState() data class ProfileLoaded( val name: String, val email: String ) : ProfileViewState()

Correct me if I’m wrong but the latest

2.4.0

release uses alpha version of androidx.lifecycle library. I have a wish and a request to write about things like this (alpha/beta versions of 3rd party dependencies) in release notes, maybe even with extra exclamation marks ⚠️ E.g. for us it’s a blocker to update orbit to

2.4.0

as we don’t have much faith in google’s alpha-beta quality…

Hello! I stumbled upon Orbit-MVI and I’m very motivated to try it out. Do you think we can also benefit from using it with a StateMachine - let’s say in the reduce function - so we can have a better control over the State? Have you tried?

I’ve a question regarding

intent

, I’ll add details in thread:

Hi! I am currently evaluating orbit-mvi and uniflow-kt (still on theoretical level). Since I am quite new to these topics, I already asked a lot of questions in the #uniflow channel. Not all of them have been answered so far. Feel free to provide your point of view on those and additional aspects here. I am especially interested in the following (see comments):

Hi! I am quite new to MVI, but your library looks very promising 🙂 I started looking into the orbit-sample-stocklist-jetpack-compose and how flow is used there for the request of the stocks. In the example the flows live as long as the ViewModel does. What would be the intended way of managing those flows with Orbit in case I need to close and open it again (e.g. with different parameters if I would have some kind of filter functionality). I already found this question in the github repo: https://github.com/orbit-mvi/orbit-mvi/issues/12 As far as I understand the suggestion there is to create coroutineScopes and cancel the previous Job if a new subscription is required. This works, but is there any better way in the meantime or is this still as intended?

Hello everyone, Is there a problem with this code that can cause the state not to be modified? The logs display very well when there is an error or when the operation is successful but at the view level the state has always the default value

private fun Flow<Result<List<Lottiefile>>>.fetchData() = intent(registerIdling = false) {
    collect { result ->
      when(result) {
        is Result.Error -> {
          Timber.e(result.toString())
          val errorMessage = result.exception.localizedMessage ?: "Unknown Error"
          reduce { state.copy(isLoading = false) }
          postSideEffect(ExploreEffect.ShowErrorMessage(errorMessage))
        }
        Result.Loading -> {
          Timber.e(result.toString())
          reduce { state.copy(isLoading = true) }
        }
        is Result.Success -> {
          Timber.e(result.toString())
          reduce { state.copy(files = result.data, isLoading = false) }
        }
      }
    }
  }

The state is collected like that

val state by viewModel.container.stateFlow.collectAsState()

Btw, any update on this: https://github.com/orbit-mvi/orbit-mvi/issues/20 (it’s in progress, good news 🙂 )

Hey guys, what do you think about tweaking the

runOnCreate

function so one could subscribe to container from it -> currently it’s impossible due to compilation restrictions, so in case of ViewModel we have to subscribe from the `init{}`which then could affect tests which don’t wanna run

runOnCreate

on TestContainer

Hi guys, just a quick question: Since you’ve logic regarding to SaveStateHandle (which it’s pretty handy), if for some reason I don’t want to store a specific member - let’s say a complex list - how should I do it? Mark it as

@IgnoredOnParcel

? Thanks!

Hi, we just finished our first little project based on a (for us) completely new technology stack including Orbit. We only touched its core features but so far we are really happy with it. Now that I am more into MVI, Kotlin, Coroutines, Flows, Compose etc. I can confirm what was initially more a gut feeling: Orbit is the right choice (for us) when it comes to MVI frameworks. Its technical foundation naturally fits to the rest of a modern technology stack. Using the same standard concepts across all architectural layers makes things easier, slick and seamless. So once again, thank you for answering all my stupid question a few weeks back and bringing me on the right track.

Hi again, as part of some architecture documentation I created the attached diagram. Does this make sense? Is it correct in terms of Orbit?

quick question on savedstate handling...is there a way to save only a partial bit of your viewmodel? e.g. just an ID to reload data with? or a Paging offset e.g. I didn't see anything in the API to do this...

Another quick question: if you have a multistage intent, can you have multiple reduce calls interspersed w/ network/db calls? e.g. reduce { state.copy(loading = true) } val results = loadstuff.await() reduce { state.copy(loading = false, data = results, loadingPhase2 = true) } val results2 = loadmorestuff.await() reduce { state.copy(loadingPhase2 = false, extradata = results2) }

Just finished a new POC with Orbit on KMM grounds. Not yet ready to make it public (SwiftUI time), but I can share a quick feedback about KMM/Android: ❤️ - there you go. A quick question: I know there’s no SavedStateHandle logic in KMM, but how one can save state when sharing ViewModels? 🤔 Is it even possible?

Question for folks using this in production...how do you handle savedstate (for app resurrection) when you only want to save part of your state but your screen state includes large lists of items? E.g. saving the paging offset of an infinite scroll list... You can't just mark your entire state class as parcelable because that would include your item list.

In the last video on Orbit, there was a mention of adding a timetravel feature...I didn't see an issue on design for it. Was mostly curious if there's a hook for watching the state transitions to add debugging logs.

For guardrails, is there anything that checks for people using vars or mutable state in data classes? Something like what mavericks has done: https://airbnb.io/mavericks/#/debug-checks

Hey guys, I'm considering using orbit-mvi for our project, currently I'm using MobiusKt by Drew Carlson but the lack of union types in Kotlin makes it too verbose. We are building a Multiplatform project, is there anything specific that needs to be done, or something to be aware of, when writing code with orbit-mvi for iOS?

Hi everyone, I have been playing around with Orbit-MVI lately and I really like its simplicity. However, after using Mobius for a long time I'm not too sure what the best practices are. So here's my problem. I usually represent my network calls as suspend function returning and Either from the Arrow library. In Mobius, when consuming an Either I would just call

fold()

and dispatch and effect on the left case (error), and a new state on the right case (success), within the same

fold()

Using Orbit-MVI I either have to fold the

apiResponse

twice in the reduce block and the suspend block from the

intent

(option1), or do the

fold()

outside the reduce block but then the fold is happening in the impure world which isn't good practice in my opinion. Which option do you think is best, and is there any alternative to achieve this?

Hey guys, yesterday lifecycle 2.4.0 was released which is a big deal 🎉 Just wonder is it planned to update orbit to 4.2.x with this stable dependency?

if there is ever a 3.0, it would be nice to rename SimpleSyntax -> SimpleReducer. If you extract on a function, AS will generate this currently:

private suspend fun SimpleSyntax<TaskScreenState, TaskScreenSideEffect>.addTaskReducer(
    onComplete: () -> Unit
) {

hmm....technically, that's not a reducer though... 🤔 but SimpleSyntax is an odd name for this too.

for a unit test, if an intent calls another intent, the 2nd intent doesn't seem to get executed. Is this expected? Works fine when. running the app live though...the 2nd intent does get run. 2nd intent was done that way get access to reduce, etc. but was intended to be shared code. Is the proper way to do this to pass the SimpleSyntax context along to the shared code?

Hi guys! I’m trying to open a KMM project to code iOS module and it fails to build with:

Is there any way to run intents multiple times in debug mode to verify that they don't have side effects (aka idempotent) like you can do with redux reducers or Mavericks?

Hello! Looking into KMM sample I have a question regarding iOS state object

Is it possible to add time travel to Orbit? Was looking at the issue tracker and wondering how it can be done without formal classes for intents to save all the parameters... Noticed Mavericks also doesn't have this and it's a similar MVVM+ MVI architecture instead of a more formal MVI one with the extra boilerplate...

Orbit MVI 4.3.0 has been released! 🎉 https://github.com/orbit-mvi/orbit-mvi/releases/tag/4.3.0 This is a minor release fixing issues with creating DSL extensions and adding few other minor features. Highlights: • Added Compose extensions for convenience • Fixed issues for DSL extension development • Updated

androidx.lifecycle

to

2.4.0

🎉 Enjoy!