app-concept

Every screen later borrows from this page. If the concept is vague, the opening is vague, the story is generic, and the paywall sells features instead of a result.

Produce one page with exactly these parts

1. The angle, in one sentence. What the app does differently, said as a result for a person. Not a category ("a time tracker") and not a feeling ("be more productive"). Good: "It tracks your workday for you, so you see where the hours went without starting a timer."
2. Who it is for. One person, their day, the moment the app matters to them.
3. The promise. What is true for them after a week. Measurable if possible.
4. The hero object. The one visual that carries the brand through the flow (a candle, a plant, a ring). It will appear on the first screen and the last.
5. The feature map. Every feature as one line: what it does for the person. Mark which three carry the promise; those are the only ones the opening shows.
6. What it is not. The two or three things people will confuse it with, and why it is not those. This line stops later screens from selling the wrong product.
7. Proof the numbers are honest. Any figure the onboarding will show (hours lost, money saved) and the formula behind it. Exaggerate the scale (a decade, a year), never the facts.

Rules

• Write it in the reviewer's words. If they said "it's not a blocker", the page says so.
• If two features compete for the opening, the one that is unique wins; the other goes to the story.
• The concept page is re-read before every new section of the flow.

Anti-patterns

• A tagline instead of an angle ("Your time, reimagined").
• A feature list without the person in it.
• Promises the app cannot keep in week one.