A first App Store release is a legal and operational event. You pick a bundle ID, a privacy label, and a version that strangers can install. The process question is not “are we agile.” The question is whether version one is a contract or a learning loop. This article is about that choice. It is not a guide to going faster. For bottlenecks and calendar pressure, read time to market and roadblocks and from idea to market.

Use fixed scope when version one must pass review with a known job. Use agile when you are still discovering that job. Do not mix the two without writing the rule.

What does fixed scope mean for version one?

Fixed scope means the first store binary has a written list of screens and a written not-now list. Change goes to version 1.1. The team can still work in weekly slices. The store gate is not a moving target.

This fits products where review will ask hard questions: payments, health-adjacent copy, or a detective fiction that must not look like real surveillance. Spylie is a narrative game. The store listing has to say that clearly. A weekly rewrite of the promise would be a review risk, not a virtue.

When is agile the better contract?

Agile is better when the first job is still unknown and you can ship to TestFlight without pretending the public listing is stable. You still need a kill rule. “We will not add a second tab until ten testers finish the first job” is a rule. “We will see” is not.

1. Write the first job in one sentence.
2. Write the smallest UI that finishes it.
3. Write the change that would force a new store version versus a silent TestFlight.

Consumer apps we ship, such as YourStyle, still needed a store-shaped version one. Discovery happened around outfit logic, not around inventing a new category every sprint. Category positioning is a different essay: the ASO playbook on positioning.

How do you write the hybrid without lying?

If a client wants agile language and a fixed date, pick one as the contract. The other becomes a wish. Selecting a studio that will say this out loud is covered in how to choose an iOS studio.

What belongs in the version-one cut?

The first job, empty and error states, and the privacy text. Not a second product. Feature creep is how first releases miss review windows. See feature creep and the step list in from idea to App Store.

What mistakes look like process?

• Sprint theater: standups with no increment that a tester can feel.
• Fixed-price, infinite backlog: that is not a scope. It is a dispute.
• Changing the privacy nutrition label in silence: that is a store event.
• Skipping localization until “after launch”: if the market needs Turkish and English, it is version one. See localization.

Studio: Croncode. People: Goktug Unver, Yusufhan Sokur. Index: Journal.

Write the review risk in one paragraph before you pick a process. Payments, location, and anything that could look like surveillance raise the cost of a moving promise. A chauffeur app and a found-phone game fail review in different ways. Name the risk, then choose fixed or agile. If you cannot name it, you are not ready for a date. You are ready for a TestFlight and a written kill rule. Quote materials still apply: what to send for a quote.

Frequently asked questions

Can I be agile after a fixed version one?

Yes. That is the usual path. Lock the first listing. Learn in 1.1. Do not learn by rewriting the public promise every week.

Does Apple require agile?

No. Apple requires a binary, a listing, and truthful metadata. Your internal process is your problem.

What if stakeholders keep adding screens?

Put them on the not-now list with a date. If the list is empty, you do not have a process. You have a queue of wishes.

Should AI features be in the fixed list?

Only if you can evaluate them and explain them on the listing. Otherwise they are TestFlight. Briefing help: how to brief an AI app studio.

Where do I start the build sequence?

Use the realistic build sequence, then pick the contract style on this page.