# FlowMVI

> Architecture Framework for Kotlin. Reuse every line of code. Handle all errors automatically. No boilerplate. Analytics, metrics, debugging in 3 lines. 50+ features.

FlowMVI is a Kotlin Multiplatform MVI (Model-View-Intent) framework built on coroutines.

This documentation is optimized for AI assistants and LLMs.

Quick navigation:
- For getting started, see quickstart section
- For platform integrations, see integrations section
- For state management, see state section
- For plugins system, see plugins section

GitHub: https://github.com/respawn-app/FlowMVI

## Table of Contents

- [Get Started with FlowMVI](https://opensource.respawn.pro/FlowMVI/quickstart.md): import Tabs from '@theme/Tabs';
- [FlowMVI](https://opensource.respawn.pro/FlowMVI/README.md): Architecture Framework for Kotlin. Reuse every line of code. Handle all errors automatically. No boilerplate. Analytics, metrics, debugging in 3 li...
- [Use FlowMVI with AI Agents](https://opensource.respawn.pro/FlowMVI/integrations/ai-agents.md): We publish `llms.txt` and `llms-full.txt` at the documentation root so agents can index the full docs quickly.
- [Use FlowMVI with Android](https://opensource.respawn.pro/FlowMVI/integrations/android.md): There are multiple options on how to organize your code when working with Android.
- [Compose Integration](https://opensource.respawn.pro/FlowMVI/integrations/compose.md): ![Maven Central](https://img.shields.io/maven-central/v/pro.respawn.flowmvi/core?label=Maven%20Central)
- [Dependency Injection](https://opensource.respawn.pro/FlowMVI/integrations/di.md): DI is mostly out of scope of the library, however, setting up your own injection is very easy and can be done
- [Essenty Integration](https://opensource.respawn.pro/FlowMVI/integrations/essenty.md): The library integrates with Essenty (Decompose) to support lifecycle and retaining store instances across configuration
- [Testing with the FlowMVI Test DSL](https://opensource.respawn.pro/FlowMVI/integrations/testing.md): import Tabs from '@theme/Tabs';
- [Contributing](https://opensource.respawn.pro/FlowMVI/misc/CONTRIBUTING.md): * To build the project, you will need the following in your local.properties:
- [FAQ](https://opensource.respawn.pro/FlowMVI/misc/FAQ.md): The library's minimum JVM target is set to 11 (sadly still not the default in Gradle).
- [More Resources](https://opensource.respawn.pro/FlowMVI/misc/resources.md): On this page you can find additional resources and projects to be inspired by or get practical examples
- [Creating custom plugins](https://opensource.respawn.pro/FlowMVI/plugins/custom.md): Plugin is a unit that can extend the business logic of the Store.
- [Remote Debugging](https://opensource.respawn.pro/FlowMVI/plugins/debugging.md): FlowMVI comes with a remote debugging setup with a dedicated Jetbrains IDEs / Android Studio plugin and a desktop app
- [Decorators = Plugins for Plugins](https://opensource.respawn.pro/FlowMVI/plugins/decorators.md): :::warning[Experimental Feature]
- [Composing Stores](https://opensource.respawn.pro/FlowMVI/plugins/delegates.md): Stores can be nested in each other, and delegate some of their responsibilities to other Stores.
- [Metrics Plugin](https://opensource.respawn.pro/FlowMVI/plugins/metrics.md): FlowMVI ships a metrics plugin that instruments the store (or plugin) pipeline and periodically
- [Getting started with plugins](https://opensource.respawn.pro/FlowMVI/plugins/prebuilt.md): FlowMVI is built entirely based on Plugins!
- [Persist and Restore State](https://opensource.respawn.pro/FlowMVI/state/savedstate.md): The `savedstate` artifact contains plugins and API necessary to save and restore the state of a store to a place
- [Managing State](https://opensource.respawn.pro/FlowMVI/state/statemanagement.md): State management in FlowMVI is slightly different from what we are used to in MVVM.