An idea with no brand, no screens, and no developer account, taken to a published Google Play listing. Here is every artifact that got produced along the way, in the order it got produced, so you can see what an app engagement actually hands you.
Sleep sound apps are a crowded category and almost all of them run on subscriptions, accounts, and tracking. The gap was a paid-once app simple enough for someone in their seventies to operate half asleep in a dark room. No one had built that, so we did — on our own money, which is the part that matters here.
Four stages. The same four we run on client work. This is the deliverable list, not a narrative — what you would receive, and roughly when.
Before a single screen. Who it is for, what already exists, and what it should cost.
Brand and screens, built as a working prototype rather than a slide deck.
The working app, plus the production pipeline behind it.
The paperwork and the assets. Usually the part nobody warns you about.
Not every artifact, but the ones a client asks to see before signing anything.
A sleeping crescent with a wave, built to stay legible at 48 pixels on a home screen and at 512 in a store listing. Adaptive and monochrome Android layers shipped alongside the primary mark, and the palette was fixed as tokens before a single screen was designed.
Five screens, no more. Each one was tested against a single question: could somebody operate this half awake, in the dark, without having seen it before? That constraint is why there is no settings screen, no onboarding carousel, and no account.
The part most people discover two weeks after they thought they were finished. Feature graphic, icon at every required size, captioned screenshots taken from the shipping build, and every console declaration answered — data safety, content rating, category, health-app scope, and the foreground service permission with its demo video.
Built before launch, not after. Three channels, chosen because they suit a paid app with no ad budget.
Title, short and full description, and screenshot captions written against the terms the audience actually searches — not the terms the category uses. The listing opens with a plain statement that it is not a medical device, which keeps it out of a regulated classification and reads as honest rather than defensive.
The buyer is frequently not the user. Adult children and caregivers choose apps for parents, and they read different publications, in different places, with different criteria. Targeting them directly is cheaper than competing for the general sleep-app keyword.
One designer, no mobile experience, an AI-assisted build documented start to finish. That is a story press and communities will run, and it carries the app with it. The book is the long form of the same story, and each one sells the other.
The app is live, the purchase works, and it survives the thing a sleep app has to survive: running all night, screen locked, without being killed or draining the battery.
The decisive finding. With the screen locked, Android suspends the app’s JavaScript. Native audio keeps playing, but shutoff timers never fire — so a thirty-minute timer played past thirty minutes and only stopped when the phone was unlocked. Nothing in a simulator shows you that. It took sleeping with the app to find it, and a rebuild on a foreground service to fix it.
Same four stages, same deliverables, your idea instead of ours. Three things worth knowing before you start.
Google requires twelve testers and a fourteen-day closed testing window before you can apply for production. Nobody gets under it. What we can compress is everything either side — and that is where projects normally lose months.
Approving the direction after discovery, reacting to the prototype, and signing off the store listing. Between those, you are not in meetings. Most of our own build happened without a single status call.
Source code, design files, prototype, brand assets, store account, and the listing. Published under your name or your company’s. No retainer required to keep it running, though we are happy to.
This page is the what and the in what order. Prompt to Play Store is the how — every prompt, every console field, and every failure, written up so you can run it yourself. Simply Rest is the app the book builds.
Tell us what you have and who uses it. We come back with what is wrong, what it is costing you, and what fixing it would take. If nothing needs fixing, we say that too.
Request an auditGet told when the book lands, when a console section gets re-checked, and when a prompt in the library stops working. No other email, ever.
Join the list