@Arkadii Ivanov добрый день, пока нас двое в канале, спрошу по русски, прочел вашу статью и статью по MVICore, но так и не понял, что такое Effect, посмотрел сэмпл в mvikotlin, так же не нашел пока что это, можете как то пояснить что это такое?

Hello! Samples for iOS use SwiftUI, but it’s only for iOS 13+ and in most cases is not suitable for production. I would like to see the most primitive example of use with ordinary

UIViewController

. More specifically, working with Lifecycle, subscription for state changes and sending events. If I just copy

LifecycleRegistryExt

and

LifecycleWrapper

and do:

override func viewDidLoad() {

self.viewLifecycle = LifecycleRegistry()

self.controller?.controller.onViewCreated(...)

self.controller?.lifecycle.start()

}

override func viewDidAppear(_ animated: Bool) {

self.viewLifecycle?.resume()

}

override func viewDidDisappear(_ animated: Bool) {

self.viewLifecycle?.destroy()

}

deinit {

self.controller?.lifecycle.stop()

}

Would this be the right approach?

Another issue that concerns me is getting State. I used the same approach with Proxy as in the example. But

@Published

replaced with

PublishSubject

from RxSwift. I don’t like the need to use an additional library for such a simple task. In addition, in mpp-library I use coroutines. Perhaps there is an easier way to signal the

UIViewController

of a state change?

Hey! Are there plans adding more flexible logging strategy for

mvikotlin-logging

, for now everything gets logged,

storeName

,

eventType

and

value

, but

value

sometimes gets huge (mainly because of

Model

and

State

data classes) and pollutes the logcat. I saw that now we can specify

maxLenght

for log message, but that is more like guessing game.

Hello! In android I am using

StateKeeperProvider

to keep

Store

during configuration change. I do it as in the example:

stateKeeperProvider.retainStore (lifecycle) {...

But when I close the fragment and reopen it, I get the error “_The supplier is already register with this key: class com.example.MyStore_”. Shouldn’t the supplier unregister in such cases? And what should I do to avoid getting this error?

Hi, I want to clarify, does StateKeeper work when process was killed by system?

Hey, working with the TimeTravel feature it appears that if you use a Store with a Unit Action (to kickstart database load) that it is unable to be serialized when exporting. Is there a workaround for such cases?

Hey, I try to understand, I use

instanceKeeper

for reusing Store and in init I add

lifecycle.doOnDestroy(citiesStore::dispose)

of cause, it doesn’t work after configuration was changed. when should I dispose my store, if I reuse instance via instanceKeeper?

Hello, I’m trying to create multiplatform project using new kmm plugin, but I have a problem with ios when defining store

Use of unresolved identifier 'DefaultStoreFactory'

let store = NotesStoreFactory(DefaultStoreFactory())

here is my build.gradle.kts file from shared module

val commonMain by getting {
    dependencies {
        api("com.arkivanov.mvikotlin:mvikotlin:2.0.0-rc3")
        api("com.arkivanov.mvikotlin:mvikotlin-main:2.0.0-rc3")
        api("com.arkivanov.mvikotlin:rx:2.0.0-rc3")
       //other deps
    }
}

Can someone help me to figure out what was the problem ?

Hi everyone. Is it normal to use labels to do something in the view (like navigation for example) ? from the scheme it is not right. but sometimes we can’t use the state for it.

For one-shot events in Jetpack Compose (with MVIKotlin + Decompose) is the best way to fire two Intents/Labels? The first setting a flag in the Model, second undoing it? I can't figure out how to get Compose to recognize the same event twice otherwise but I see issues down the line with this workaround.

Hi. Sqldelight allows you to keep track of database changes via flow. But how should i integrate this flow with store? And most importantly, should i? For small feature - list of something that user can add/delete it seems like a good idea. Best i can think of is subscribing to flow in bootstrapper and spamming actions to update stores inner list. Feels like I'm missing some point. Thanks

FYI if upgrading to newest Canary 13 while using Decompose the mpp/compose workaround needs to be updated to reflect the new compose compiler location refactor:

project.dependencies {
        composeCompiler "androidx.compose.compiler:compiler:$compose_version"
    }

Hey, I’ve recently started using mvikotlin with decompose in a project, and run into an issue when using any

Bootstrapper

, but

SimpleBootstrapper

After configuration change this exception occurs on application launch:

java.lang.IllegalStateException: Value is already initialized: Function1<Action, kotlin.Unit>
        at com.arkivanov.mvikotlin.utils.internal.AtomicExtKt.initialize(AtomicExt.kt:7)
        at com.arkivanov.mvikotlin.extensions.coroutines.SuspendBootstrapper.init(SuspendBootstrapper.kt:26)
        at com.arkivanov.mvikotlin.main.store.DefaultStore.<init>(DefaultStore.kt:58)
        at com.arkivanov.mvikotlin.main.store.DefaultStoreFactory.create(DefaultStoreFactory.kt:21)

Although this is easily avoided by using

SimpleBootstrapper

, I’m wondering is this behaviour intended or is there something that we have to do to prevent the exception from happening? The issue can be reproduced in decompose or mvikotlin sample app by replacing the

SimpleBootstrapper

by

Suspend/ReaktiveBootstrapper

@Arkadii Ivanov how do you feel about a similar plugin functionality in Decompose as badoo/Ribs? I'm looking to extend the component context functionality to include an authorization component and I'm waffling between tweaking decompose internals or investigating the plugin route

Does MVIKotlin have a file template as well? similar like badoo here

I'm looking into applying MVI pattern and this project looks great. Do you see any issue with utilizing libraries like FlowBinding with it? https://github.com/ReactiveCircus/FlowBinding

Hi there. Does MVIKotlin have something like a MVICore's post processor. Or do we need to send a Label which will send Intent to the same Store?

Hi! Can I ask a quastion?  How I can correctly display a dialog using Label without using a State? For instance. I check some condition in Executor in SimpleBootstrapper and according to result of the condition I decide to show user some dialog.

I have set up my app using clean architecture. Thereby, I have UseCase-classes which have an Input and transform it in an Output-flow or a single value. I want to hook this up with this framework. MVIKotlin should only know about the state of the application. I think the executor should therefor make decisions to start/stop a Use-case? I think using a sealed class

Task

which the binder then connects to the real use-cases is the best way? The output of the use-cases should then be dispatched to the reducer. Probably using the binder too? Intents that only need simple updates (which don't need suspending) can be dispatched by the Executor itself. The other alternative would be to give the Use-case classes all to the executor (which is a SuspendingExecutor after all), but I think this approach is way cleaner. The Task-class could be implemented using Label with a lambda to dispatch. Is this the way to go, or is there a better one?

Hi! I have someStore (MVI store) that save in instanceKeeper, I call someStore.dispose(), and store go to state isDisposed = true, how I think I can't work with this store anymore, but why instance of store saved in instanceKeeper? Can I do something with disposable store? @Arkadii Ivanov

@Arkadii Ivanov Hi. Can I ask about transfer some events from one feature to another? For example: by clicking on the back button on screen A, I gonna go to the previous screen B, and the item list should be updated on screen B. Something like eventbus comes to mind. Create some SharedFlow, emit event from Store A and collect it in Store B. But where I should collect it? In custom Bootstrapper in Store B? How do you recommend implementing such logic?

MVI approach is all solid and gr8 and leaves no place for unintended behaviour/things to happen or atleast we can say it minimises it to gr8 extent! However i have been developing most of my projects in MVVM and as now i am trying out to port the same projects to MVI , i feel like MVI requires more effort or you can say its more time-consuming . I also feel MVI is more clean and descriptive ! Anybody else feels same? If yes is that extra effort worth it ? , and is MVI your goto choice for large scale apps?

Hi, I was wondering how to cancel a request in MVI? Lets say an intent starts a network request but another intent must cancel it?

Hi i was wondering which project would you recommend at this stage if we want the most clean way of MVI. Would you recommend MVIKotlin or MVICore both to me looks great and the implementation feels good. I still want to do my own implementation over it. But a little confused which one is looking better at this stage to me. In a way i prefer the MVIKotlin more. To me both look very very good. I am asking from the point that soon i will be starting a new project that might turn out to be a multi platform one and there will be new people that i might need to introduce the MVI implementation. I would like them to be able to grasp it quicker and was curious for your input. Thank you

Hi @Arkadii Ivanov, in a multiplatform project (mobile) with MVIKotlin, is it feasible to adopt JetpackCompose on Android side, forgetting about fragments and lifecycle? Any hint on how to trigger recomposition on state updates?

hello is there also a beginner tutorial. for MVI I am a new. something like MVI pattern with just Input field and output text. witch jetpack compose.

Hello, what should I do when my

store

is too big to be persisted? Until today, I reflected in my

state

object, which

data

I should query. This is important because my

data

can be too big for my

savedStateHandle[android]

to restore. The problem I am facing with this approach is that sometime my

state

depends on the

data

and sometime the

data

depends on my

state

. Any suggestions/articles that address that

state != data

and can help me find a better approach that solves the issues I am facing?

I've been working through the samples for my own project. At the moment my view doesn't appear to access the data from the model on Ios/SwiftUI at least from the preview screen. I'm a little confused where the ViewModel and ViewEvents come from on IOS. Are they generated? For instance, from the example:

import Foundation
import TodoLib

class TodoListViewProxy: BaseMviView<TodoListViewModel, TodoListViewEvent>, TodoListView, ObservableObject {
    
    @Published var model: TodoListViewModel?
    
    override func render(model: TodoListViewModel) {
        self.model = model
    }
}

Where is the TodoListViewModel generated? If I set up a preview here and there was data being accessed from the model (using sqldelight in this case), would we expect the preview to show the data?