Poster №4 · Guides
What we explain to clients most often — written down and free.
Half a page beats twenty. Describe: who the user is, the one task they solve, what already exists (site, API, brand), constraints (date, budget range, platforms) and how you will know the release worked. Do not describe buttons — describe situations: "a driver wants to see in 10 seconds whether a space is free".
A cross-platform stack (React Native, Flutter) is sensible when the interface is similar on both platforms and speed matters. Native fits when you need deep system features: background work, widgets, complex camera, AR, strict energy limits. The question is not "what is trendy" but "what will your product do in a year".
1) A crash during review — test on a clean install. 2) No demo account to sign in. 3) A permission prompt without explanation. 4) The privacy form does not match SDKs in the build. 5) The description mentions features that do not exist. All five can be closed before submitting — see the Readiness board.
A quick self-audit: turn on VoiceOver/TalkBack and walk the main flow with eyes closed; raise system font to maximum; check body-text contrast (≥ 4.5:1); complete a web form by keyboard only. Each finding is a backlog task, not a "someday".