How to write a one-page product brief
One page forces you to choose. We suggest five blocks: problem (one sentence), people (who specifically), today’s solution (how they cope now), first version (three to five features), success criterion (what you will measure a month after launch).
If a block will not fill in, it is not failure but a hint about what to discuss with potential users.
What a first version is — and isn’t
A first version is the smallest product that lets you test the main assumption with real people. It need not be a small copy of the “full” product. Often it is one scenario taken all the way through.
Signs of an overloaded first version: more than five must-have features, several user types at once, an admin panel more complex than the product itself.
Web or mobile app?
Web is the faster road to people: a link, no install, no store review. A mobile app is justified when you need the camera, background location, notifications, offline mode, or the product is used several times a day.
A compromise is to start with web and build mobile once user behaviour is understood.
App-store publishing checklist
Before submitting, check: the developer account belongs to the right entity; a privacy policy is published; listing and screenshots match real functionality; each permission is explained; reviewers have test access if there is a sign-in; data and age-rating questionnaires are completed.
Store rules change, so always check current official Apple and Google documentation.
Minimum accessibility for a first version
Sufficient text contrast, a minimum tap area of about 44 pixels, labels for form fields, keyboard operation on the web, alternative text for meaningful images. It is not an “extra option” but part of quality.
Short glossary
Prototype — a clickable model without real logic. Build — an installable app version. Release — a build published to everyone. Regression — a bug in something that used to work. Backlog — an ordered list of future work.
