An MVP is the smallest product that finishes a job. It is not the smallest zip file you can upload. The App Store is a public shelf. Reviewers and strangers will judge a binary, a privacy label, and a screenshot. If any of those is theater, the MVP is too thin. This is the gate we use at Croncode. It is not a request to add twenty tabs.

An MVP is too thin for the App Store when a stranger cannot finish one job, privacy text does not match the binary, or the listing sells a second product. Small is fine. Hollow is not.

What must version one finish?

One job, empty and error states, a support path, and a privacy story that matches SDKs. If you have accounts, a deletion path. If you have a paywall, restore and honest copy. If you have AI, a timeout the user can survive. Related pages: empty states, deletion, honest paywalls, fail-safe AI.

Process: fixed scope vs agile. Sequence: idea to App Store. Design QA: design QA.

Which “MVPs” fail review or fail users?

1. A wrapper around a website with no iOS job.
2. A chat window with no object. Catalog stance: what Croncode builds.
3. Screenshots from Figma that the binary does not match.
4. A placeholder name and a lorem listing. Naming: naming before the store.

Consumer jobs we consider complete enough to list: a closet look, a structured choice, a playable case, a planned journey. YourStyle, Numira, Spylie, Luviport. We do not claim they were “minimum” in a marketing sense. We claim they finish a job.

When is staying in TestFlight the honest move?

Thin is not the same as ugly. Plain chrome can ship. Hollow chrome cannot. Trust onboarding: trust onboarding.

How do you cut without going hollow?

Write a not-now list of five items. Keep the object. Cut the second platform. Cut the loyalty program. Cut the AI flourish if you cannot evaluate it. Feature creep: feature creep. Android wait: Android after iOS. No-code vs custom: custom vs no-code.

Founder: Goktug Unver. Co-founder: Yusufhan Sokur. Shipping: how we ship.

What mistakes hide inside “we will iterate in the store”?

• Using public users as crash testers: that is a reputation event.
• A landing page that overclaims the MVP: store landers.
• Skipping localization because the MVP is “global later”: if the market needs Turkish, it is version one. onboarding localization.
• No owner for Apple: account ownership.

Quote the first job and the hollow risks: quote packet. Choose a studio: choose an iOS studio. Hire: hire. Custom: custom software. Contact: contact. Journal: /en/journel/.

What should a sprint demo prove before you submit?

A stranger on a small phone finishes the job. Restore works if you sell. Deletion works if you have accounts. Screenshots are from the binary. Demo script: sprint demo. What we refuse: will not build. Team: Ozgur Ismet Ozkan.

If the “MVP” is really a marketing site, ship the site and wait: when Elementor is enough. A site can collect a waitlist without pretending it is a utility. An App Store listing cannot. Write the difference in the brief so the first increment is not a wrapper with a badge.

Frequently asked questions

Will Apple reject a simple app?

Apple rejects apps that do not do enough, or that mislead. Simple and complete can pass. Simple and empty often does not. We cannot promise a review outcome.

Can I launch with only English?

Yes if that is the market. No if you already promised Turkish users a product. Write the language list in the brief.

Is a waitlist app an MVP?

A waitlist is a marketing object. It is not a job. Do not list it as a utility unless the binary is the utility.

Should I add a second tab so it “looks like an app”?

No. A second empty tab is thinner, not thicker. Teach with empty states on the first job.

How does Croncode say no to a thin brief?

We write the missing job or we decline. Start with the studio and the packet in the quote article.