Mobile product development

How to scope an Android and iOS MVP

Choose the smallest useful mobile release and account for interruptions, stores and ownership.

Illustration for How to scope an Android and iOS MVP

Checklist

  1. Describe the action users need on a phone
  2. Decide which states work offline
  3. Test the core task on representative devices
  4. Prepare distribution and app ownership

Example

A field technician loses reception while uploading a visit photo. Test whether the draft survives leaving the screen, whether retries duplicate the visit, and how the user can confirm submission.

What to bring to your review

Target devices, sample data, failure states, API credentials owners, store accounts.

Worked example: capture a field visit offline

Agree what a visit needs to contain when the technician presses Save. A location, selected customer, note and image may have different upload behaviour. Decide what appears immediately in the worker’s task list and what should wait until the server confirms the visit.

Try the task while connected, then retry with airplane mode on. Leave the screen and reopen the app before submitting. Check whether the draft survives and whether each attempt has a clear state. Reconnect while making a second change and confirm the app does not create another visit by accident.

Test the handoff to office staff with a realistic delay between capture and upload. Check whether the staff member can tell when work was performed and when the record arrived. Set support responsibilities for a device without available storage or an account that loses access halfway through the task.

How to put the checklist into practice

Choose the first repeatable action

Identify a useful result the customer should reach twice without assistance. In a booking app, that might include checking availability, changing a booking and understanding confirmation. Interview the people who will support the workflow on launch day.

Include the operations behind the app

List which staff actions must exist so the complete journey works. A technician's completion record might need approval from a manager, along with a way to request a correction. Decide which actions belong in an admin interface.

Prototype difficult device states

Try the journey on representative phones and network conditions. Test denied permissions and lost connectivity using real content. Decide which pending changes are visible after the app is closed and reopened.

Use pilot evidence to decide the next release

Agree what usage or feedback would justify another feature. Record failed and incomplete steps alongside completed tasks. Include adoption, support effort and the time staff spend working around limitations.

Booking MVP acceptance

  1. Show a confirmed date and reference
  2. Handle two users selecting the last slot
  3. Recover an interrupted payment or confirmation
  4. Verify cancellation in the staff calendar

Need help putting this into practice?

Share what you are working on and where you need input.

Discuss this project