Google asks for something simple, worded in a way that scares people: before you can apply for production, your app must have gone through a closed test with at least 12 testers opted in continuously for at least 14 days.QuestionAnswerWho is affected?Personal developer accounts created on or after 13 November 2023Who isn't?Organization accounts, and personal accounts created before that dateHow many testers?12 minimum, at the same timeFor how long?14 days, consecutiveWhat breaks the counterA tester who leaves the program. If they come back, their 14 days start overWhat unlocks the next stepThe Apply for production button on the Play Console dashboardHow long Google takesUsually seven days or lessSource: Play Console Help — App testing requirements for new personal developer accounts, checked 11 September 2026.Two clarifications that save a lot of anxiety. First, the counter tracks your testers' opt-in, not your builds: shipping a new release to the closed track during the 14 days resets nothing. Second, it really is 12 Google accounts — not 12 devices, not 12 five-star reviews.

Imagine a course app. A new learner arrives because they want a short lesson on a specific subject. Before they can begin, the app presents five introductory screens, asks them to register, requests notifications and opens on a generic news feed. Every screen may be well designed, yet the first session has failed: the learner still has not found a lesson.Mobile app onboarding is the journey from first launch to an initial useful result: the first value. Completing the action that delivers it is activation.TermWhat it describesExample in the course appOnboardingThe whole route from first launch to first valueOpening the app, finding a lesson and starting itFirst valueThe initial useful result the user came forReaching a lesson that matches the learner’s goalActivationThe observable action that indicates first valueStarting that lessonOnboarding is often reduced to the walkthrough shown on first launch, but the two are not equivalent. A walkthrough is one possible way to support the journey: a short sequence of introductory screens that provides essential context before users enter the app. In GoodBarber, the App Walkthrough extension lets you create that introduction; whether you need it depends on what stands between a new user and first value.Do not begin by deciding which introductory screens to create. Start by asking what a new user should be able to achieve. That objective defines the onboarding journey and determines whether a walkthrough, contextual guidance or direct access is the most appropriate pattern.Apple’s onboarding guidance recommends making an app understandable through use and keeping any onboarding flow brief and optional. A walkthrough helps when it removes uncertainty; otherwise, it delays the product.

What app design really costs, how long it takes, and the six decisions behind an app that looks professionally designed. A guide for people who are not designers.

Your GoodBarber app is in the Claude connectors directory: search GoodBarber, sign in, and run your app by conversation. ChatGPT and Codex too.