Planning Your First App: An MVP Checklist for Small Businesses

The short answer

A minimum viable product (MVP) is the smallest version of your app that solves a real problem for your customers well enough that they will use it. For a small business, that usually means one or two core jobs — booking, ordering, loyalty, account access — done properly, rather than ten features done halfway. Planning an MVP means deciding the scope, preparing store accounts and content, writing a privacy policy, testing on real devices, launching carefully, and budgeting for maintenance.

Use the checklist below to work through each stage.

1. Define the problem before the features

Start with your customers, not a feature list.

• Who will use the app? Regular clients, members, trade customers, staff?
• What do they do repeatedly with your business? Book, reorder, check status, collect rewards?
• What frustrates them today? Phoning during opening hours, forgetting appointments, losing paper cards?
• What frustrates your team? Repeated phone calls, manual reminders, no-shows, double entry?

Write a one-sentence purpose. For example: "Our app lets regular clients rebook their usual appointment in under a minute and reminds them before they come in."

2. Choose the MVP scope

List every feature you can think of, then sort them into three groups:

• Must have for launch — without these the app does not fulfil its purpose.
• Should have soon — valuable, but the app is useful without them.
• Could have later — nice ideas you will revisit once real customers use the app.

Questions that help:

• Does this feature serve the one-sentence purpose?
• Will customers notice if it is missing at launch?
• Does it require a complex integration that could delay everything?

A typical small-business MVP might include: branded home screen, services or products, booking or ordering, account and history, notifications with consent, and contact details. Loyalty tiers, referral schemes and advanced personalisation often wait for version two.

A note on "website in an app"

Apple's App Review Guidelines (section 4.2, minimum functionality) discourage apps that are simply a repackaged website. Your app should offer something that benefits from being an app — such as accounts, booking, notifications, offline access or device features.

3. Check your existing systems

Most business apps connect to something you already use.

• Booking software, e-commerce platform, till/POS, CRM, membership system.
• Does each system offer an API, and does your plan include access?
• What can the API do — read only, or create and update?
• Who manages the account, and who can generate API keys?

Integrations often drive both cost and timescale, so answer these early. If a system has no usable API, it is better to know before you commit.

4. Set up store accounts in your business's name

To publish, you need:

• An Apple Developer Program membership — Apple charges an annual fee. Organisations generally enrol with a D-U-N-S number; Apple's enrollment pages explain the requirements.
• A Google Play Console developer account — Google charges a one-off registration fee and requires identity verification.

Check current fees and requirements on the official pages. Create the accounts in your business's name, then invite your developer. This keeps ownership of the app, listings and reviews with you. Allow time: verification can take a while.

5. Prepare content and store listing materials

Apps need more content than people expect.

• App name and subtitle — check availability and avoid trademarks you do not own.
• Description and keywords — honest and specific; no claims you cannot back up.
• Screenshots for the required device sizes.
• App icon following each platform's guidelines.
• In-app content — service descriptions, prices, photos, opening hours, terms.
• Support URL and contact email.
• Age rating questionnaire answers.

Tip: your existing website is a good starting point for in-app content, but text written for a desktop page usually needs shortening for a phone screen.

6. Privacy, data and legal basics

• Privacy policy. Both stores require a link. It should describe what the app collects, why, who you share it with and how long you keep it.
• Store data disclosures. Apple's privacy "nutrition label" and Google Play's Data safety section must match what the app and any third-party tools actually do.
• Account deletion. If customers can create an account, Apple expects them to be able to start deleting it from within the app; Google Play has similar requirements.
• Consent for marketing. Keep marketing opt-in separate, especially for push notifications, email and SMS. UK PECR and UK GDPR apply in the UK.
• Terms of use and any refund or cancellation policies.

This is general guidance, not legal advice; take advice for your specific situation.

7. Design for real people

• Follow platform conventions so the app feels familiar on iPhone and Android.
• Make tap targets large enough and text readable.
• Support system text sizes and dark mode where possible.
• Aim for accessibility: good contrast, labels for screen readers, no information conveyed only by colour. WCAG 2.2 is a widely used reference for accessibility.
• Keep the number of steps to complete the main task as low as possible.

Seeing a realistic concept before development makes design decisions much easier — which is why Apptavio offers a free interactive concept based on your website.

8. Testing

Plan testing as a phase, not an afterthought.

• Internal testing by the developer on real iPhones and Android phones, including older and smaller devices.
• Beta testing with your team and a few trusted customers. Apple's TestFlight and Google Play's testing tracks are designed for this.
• Scenarios to test: sign-up, sign-in, password reset, booking or ordering, payments (in test mode), notifications allowed and declined, poor connectivity, account deletion.
• Content check: prices, opening hours, names and spelling.
• Accessibility check: larger text sizes and screen readers.

Collect feedback in one place and decide what must be fixed before launch.

9. Submission and launch

• Submit to Apple and Google with complete, accurate information and test credentials if reviewers need to sign in.
• Approval is not guaranteed and timing varies. Apple and Google make review decisions; reviewers may ask questions or request changes.
• Avoid fixed launch events that depend on approval by a specific date.
• Consider a soft launch: tell existing customers first, in person and by email, before wider promotion.
• Prepare your team: how to explain the app, handle questions and report problems.

10. After launch: measure and maintain

Measure

Decide in advance what success looks like — for example, the share of rebookings made through the app, or the number of loyalty members. Use privacy-respecting analytics and only collect what you need.

Maintain

An app is not "finished" at launch.

• Operating system updates. Apple and Google release new versions every year and update technical requirements for store submissions.
• Library and security updates. Frameworks and dependencies need regular updates.
• Store policy changes. Requirements for privacy disclosures, permissions and account handling change over time.
• Bug fixes and small improvements based on real use.

With React Native and Expo, some JavaScript-level fixes can be delivered as over-the-air updates through EAS Update, within the platforms' rules; native changes still require a new store submission.

Budget for maintenance from the start. Apptavio offers ongoing maintenance plans; the cost depends on the app's complexity and how much new work you want each month.

Cost: what to expect

The cost of an MVP depends on screens, features, integrations, backend requirements, authentication, payments, notifications, native capabilities and maintenance. Apptavio builds production apps with React Native, Expo and TypeScript, so one codebase serves iPhone and Android. Custom apps start from £1,499 as an indicative starting price; we quote after agreeing scope, and explain what drives each part of the price.

The full checklist

• One-sentence purpose written
• Features sorted into must / should / could
• Existing systems and APIs checked
• Apple and Google accounts created in your business's name
• Store listing content, icon and screenshots ready
• Privacy policy, data disclosures and account deletion planned
• Design reviewed on real devices, accessibility considered
• Internal and beta testing completed
• Submission prepared, launch plan flexible
• Success measures defined
• Maintenance budget agreed

Start with a concept

If you are unsure what your MVP should include, start by seeing it. Apptavio can create a free, personalised, interactive app concept from your existing website so you can tap through a possible version of your app in your browser. It is a concept rather than a finished app, it is reviewed by a person before we send it, and there is no obligation to proceed.