v4.0.2

• Common module flow API: #11
• Multiplatform machine lifecycle moved to the separate artefact: #12

Potential breaking change:

The view lifecycle MachineLifecycle)
implementation is moved to the separate multiplatform library:

dependencies {
    // View lifecycle implementation
    implementation "com.motorro.commonstatemachine:lifecycle:x.x.x"
}

v3.3.0

Library updates 2026-01

v3.2.2

• Kotlin 2.2.10
• Library updates 2025-08

v3.2.1

Kotlin 2.0, library updates

v3.2.0

Added generics for multi-machine states to be able to process view-state updates based on some common UI state
Migration:

Add common gesture/ui-state types

Was:

internal class MixedState : MultiMachineState<MixedGesture, MixedUiState>() {

}

Now:

internal class MixedState : MultiMachineState<MixedGesture, MixedUiState, Any, Any>() {

}

Change signature for gesture processing

Was:

override fun mapGesture(parent: MixedGesture, processor: GestureProcessor)  {

}

Now:

override fun mapGesture(parent: MixedGesture, processor: GestureProcessor<Any, Any>) {

}

Change signature for ui-state processing

Was:

override fun mapUiState(provider: UiStateProvider, changedKey: MachineKey<*, *>?): MixedUiState {

}

Now:

override fun mapUiState(provider: UiStateProvider<Any>, changedKey: MachineKey<*, out Any>?): MixedUiState {

}

v3.1.0

Machine composition - running parallel machines (#7)

v3.0.2

Kotlin 1.9.10, Compose 1.5, AGP8

v3.0.1

v3.X Breaking change

To be able to get the current UI state of the state-machine and to get rid of inconsistency of the UI state is not yet defined (no updates of UI state happened) the FlowStateMachine and the ProxyMachineState now require to pass initial UI state in constructors.

v2.1.4

Library updates

v2.1.2

Library updates