What are the benefits of the Bootstrapper component? Mostly curious about the rationale behind having a dedicated component instead of having a set of initial `Intent`s that get passed to the Store?

That is to make the initialization automatic and implementation details, not a public API. Another reason is that the Bootstrapper can produce different

Actions

, that are handled separately in the

Executor

. This makes the

Executor

implementation more deterministic and readable. It also allows

Actions

logging and time-traveling. You can use Intents if you like. There are no strict rules here.

I guess I'm having a hard time trying to figure out a use-case for `Action`s that would be more appropriate/idiomatic than having a

Set<Intent>

as a constructor argument on the

Executor

(which would keep this an internal implementation detail as well). I'm asking because we are currently using our own mvi framework that isn't KMP ready and thinking of proposing that we use MVIKotlin for viewmodels in KMP and trying to understand the use-cases for `Action`s. We currently have a

Set<Intent>

as a constructor param on the

ViewModel/Store

that get passed to

Executor

and it seems to work well

Sure, I will explain it further. • Having Set<Intent> in the constructor makes the corresponding intents part of the public API of the store. E.g. you will likely have

Intent.Init

, which is the public API of the store. So the store will use its own public API, which is not quite clean from the code perspective. And also you are technically able to send

Intent.Init

from outside, which kinda goes against the encapsulation. • In the

Bootstrapper

you can do async jobs. E.g. you are able to subscribe to network or database events, and emit an

Action

for every such event. The

Executor

will handle each such emission separately. Each such

Action

can be logged, and time-traveled if desired.

I see. So one of the benefits is that something like

Intent.Init

cannot be called multiple times. We do currently have to handle this logic manually to ensure that

Intent

doesn't get called multiple times. I'm not sure if the added complexity is worth it for us. It's great that MVIKotlin is flexible and the

Bootstrapper

is optional! Thanks for the explanation and writing this awesome library!

Please note that you can just define your Action type as Unit, and use SimpleBootstrapper(Unit). https://github.com/arkivanov/MVIKotlin/blob/a5afc57f523207c51bba660acdf86ebdf02179e4/sample/coroutines/shared/src/commonMain/kotlin/com/arkivanov/mvikotlin/sample/coroutines/shared/details/store/DetailsStoreFactory.kt#L33

ah! Thanks for the pointer