An MVP is useful when a mobile experience can test a clear user outcome with a small number of screens and actions. The first release might focus on account access, one core task, a useful status, and a simple support path.
The goal is not to release something unfinished without a plan. Define what success means, how feedback will be collected, which technical risks must be tested, and which features are deliberately outside the first release.
For practical planning, make one important mobile journey work reliably first: sign in, find the right information, complete the main action, and understand what happens next. Test loading, network interruptions, permissions, accessibility, and support before adding more screens so the first release is useful and future features have real evidence behind them.