Tutorials
Ark MVP tutorials
Build complete presentation features around one UseCase, several UseCases, or an independent application state manager.
The tutorials use the same ModelBinding, Presenter, ViewState, and MvpView contracts. The first three vary the business boundary behind Model; the fourth composes the wider ArkTelos stack.
Before starting, read Model and ModelBinding and Presenter as the adaptation boundary. A tutorial assumes that the business object already exposes a synchronous current snapshot, one or more change signals, and named operations.
Choose a scenario
- One UseCase demonstrates direct binding, lifecycle-aware business state, localization, and a one-time limit effect.
- Several UseCases combines independent loading and saving snapshots into one coherent screen without inventing a coordinating UseCase.
- Application state manager proves that Ark MVP is not coupled to UseCase Forge and demonstrates context-based binding.
- Full task app runs a complete Flutter feature with data, DI, UseCase execution, MVP, typed navigation, and opt-in diagnostics.
Each guide identifies ownership, composition, adaptation, rendering, and teardown separately. The complete runnable sources remain linked from the page header.
What stays the same
| Concern | One UseCase | Several UseCases | State manager |
|---|---|---|---|
| Business owner | Feature composition | Feature composition | Application composition |
| Model | One complete immutable feature snapshot | One aggregate of current independent snapshots | One application-state projection |
| Presenter | Adapts Model to ViewState | Combines presentation policy across snapshots | Adapts manager state without framework coupling |
| View | Receives ViewState and Presenter actions only | Same | Same |
| MVP ownership | MvpView owns Presenter | Same | Same |
If several business operations must succeed atomically, coordinate them in the business layer. Combining their current snapshots for one screen does not make Ark MVP a transaction coordinator.