"What should version one include?" It sounds like a planning question. It is really a budget question, and it sits underneath every app quote you will ever request.
Our answer: version one should contain the shortest path to the single outcome your first users came for, plus the plumbing that outcome needs to work reliably (sign-in, data, billing if you charge). Everything else is a second release. Below are the follow-up questions that come after that answer, in the order they usually arrive.
What counts as the one outcome?
Write it as a sentence a user would say: "I scan the label and know if it is safe for my kid." "I speak the plan and it lands on the family calendar." If your sentence needs the word "and" twice, you have two products.
On KIN, a FungeeLLC product we built, the outcome was turning a spoken sentence or a photographed flyer into one correct event. Transcribing speech and reading text off a photo were the quick parts. Turning "next Thursday" into the right date was the work. A team that spent its first weeks on themes, widgets and sharing settings would have shipped a pretty calendar that got dates wrong.
What goes in version one besides the feature?
The unglamorous parts that make the feature trustworthy. Most founders leave these off their feature list, then meet them in the quote as line items they did not expect.
- Authentication that survives real conditions: expired sessions, shared devices, a user who changes phones.
- Your existing backend, connected and stable, if you already have a web product.
- Billing, only if you charge on day one. A free beta needs none.
- Crash and error reporting, so you hear about failures before a review does.
- A path through App Review: privacy labels, a working demo account, and a clear reason the app exists.
Authentication is the one that bites. On SOAPNoteAI, API integration took one week against a two-week estimate, while the login flow we had estimated at three days took significantly longer. The web product already used OpenID Connect, and native iOS made us rebuild assumptions the browser had been handling silently. Nobody puts "sign-in" in the headline of a product vision, and it was the longest single item.
What can safely wait until version two?
Anything whose absence will not stop a user reaching the outcome. In our experience the usual candidates are:
- Social features, sharing, referrals and invites.
- Settings screens beyond the two or three that change behaviour.
- An admin panel. Use your database console or a scripted tool for the first months.
- A second platform. Pick the one your first users carry.
- Personalisation, themes and onboarding variations.
The test we use: if a user never saw this, would they still complete the outcome? If yes, it is a version-two candidate. If your gut says "but investors will want to see it," that is a pitch-deck problem, and a slide is cheaper than a screen.
How much does a focused version one cost?
We have published our ranges in the mobile app development cost breakdown: a focused single-platform MVP sits around $12k to $20k, a serious product build with design, integration and QA runs $30k to $50k, and multi-platform, regulated or AI-heavy builds start at $80k.
The point for this question is that scope moves you between those bands far more than screen count does. Adding a second platform, billing, and an AI feature to the same list is how a $15k idea becomes an $80k one without anyone deciding it should.
What does the version-two list do for me?
It turns a cut into a sequence. Keep a written list of everything you removed, ordered by the user feedback that would justify building it. When early users ask for the same missing thing three times, it moves up. When nobody mentions it, you have saved the budget and learned the feature was a preference of yours rather than a need of theirs.
This also changes how you read a quote. A phase-one scope that names what is excluded is a better sign than a long feature list, because exclusions are where disputes start.
How do I know my version one is too big?
Three quick checks. If you fail any of them, cut before you ask for quotes.
- The sentence test. Can a new user describe what the app does in one breath after a two-minute demo?
- The demo test. Can you show the whole outcome on a real iPhone in under three minutes, without apologising for missing screens?
- The dependency test. Does any core flow depend on a third party you have not integrated before? If so, test that dependency first, in isolation, before committing the rest of the budget.
The strongest counter-argument is that cutting too hard ships something thin that reviewers and users dismiss. Apple does reject apps that offer little beyond a repackaged website; its App Review Guidelines list minimum functionality as a reason. Narrow does not mean shallow. It means one outcome, done properly on the device: native capabilities such as the camera, microphone or notifications are often what make a small app worth installing.
Who decides what makes the cut?
You do, with the agency pushing back. A good partner will argue for the cut list, because every extra feature is risk they also carry. If an agency agrees to everything on your list without a single question, treat it as a warning. A real scoping conversation includes pushback.
One limitation worth stating: a narrow version one is not free of cost. You will hear "where is X?" from early users, and some will leave. That is the price of learning in weeks instead of quarters, and it is usually cheaper than learning the same thing after building X.
FAQ
What features should an app MVP include?
An MVP should include the shortest path to the one outcome your first users want, plus the supporting basics that outcome depends on: reliable sign-in, stable data access, billing only if you charge, and crash reporting. Social features, admin tools, extra settings and a second platform can usually wait for version two.
How do I decide what to cut from my first app release?
Ask whether a user who never saw the feature could still complete the core outcome. If yes, cut it. Also cut anything that adds a platform, a new third-party dependency, or billing without being essential. Keep a written version-two list so cuts feel like sequencing rather than loss.
How much does an app MVP cost?
Eightinity Technologies sees focused single-platform MVPs at roughly $12k to $20k, serious product builds with design, integration and QA at $30k to $50k, and multi-platform, regulated or AI-heavy builds from $80k. Scope and integration risk move the price more than the number of screens does.
Can an MVP be too small for the App Store?
Yes. Apple's App Review Guidelines include minimum functionality, and apps that merely repackage a website can be rejected. A small app passes when it does one useful thing properly and makes real use of the device, such as the camera, microphone, notifications or on-device processing, not just a wrapped web view.
Have a feature list and a quote that do not match? Send it over on a free 30-min call and we will mark what belongs in version one →
