MVI (Model-View-Intent)
Also written as MVI, Model-View-Intent, Unidirectional Data Flow
A way of organising app code, popular on Android with Jetpack Compose, where each screen has one single 'state' object and every user action (an 'intent') flows in one direction to produce a new state. The screen simply redraws whatever the current state says. Note: an MVI 'intent' is just a user action, not the Android system feature also called an Intent.
Think of it like
A restaurant where every order goes through one ticket rail and the kitchen only ever cooks from the current ticket, so nobody shouts changes across the room.
Junior or senior?
Often compared with MVVM, and many teams mix the two.
Senior sounds like
Can say why their team picked MVI over MVVM, and what got harder (more boilerplate, very large state objects).
Ask them
“Why did your team choose MVI over MVVM, and what was the downside you ran into?”
Reading MVI (Model-View-Intent) on a resume
- Common
- MVI (Model-View-Intent) narrows the field but doesn't prove depth on its own. The junior-versus-senior contrast above is what separates one candidate from another.
Sourcing for MVI (Model-View-Intent)
Every way it's written
("MVI" OR "Model-View-Intent" OR "Unidirectional Data Flow")Paste into LinkedIn Recruiter, Naukri or your ATS. Combine with a job title and location.
Job titles to search alongside it
Mobile Engineer · Android Developer · iOS Developer · Mobile Application Developer · React Native Developer
Where this talent works in India — Mobile Engineering
Target companies with a large installed base and frequent releases — consumer fintech, food and quick commerce, streaming and gaming. App-agency experience looks similar on paper and behaves very differently at scale.
For example: PhonePe, Swiggy, Eternal (Zomato, Blinkit), CRED, Dream11, JioHotstar, Truecaller, Paytm.