BettaDev
App design studio · iOS, Android, Web · Remote, worldwide
BettaDev is an independent app design studio. Strategy, interface and production code stay with one principal from the first call to the store listing — which is why only two engagements run at a time.
Selected work · Studio release
Scoped, designed, built and shipped end to end by one person: the flows, the piece physics, the art direction and the store listing. It is the studio’s own first release, which makes it the clearest available answer to what an engagement here actually produces.
What the studio does
How engagements workDiscovery, user flows and a prototype you can actually hold. You use the product before a line of production code is written.
Type, colour, motion and components — delivered as a system that lives inside the codebase instead of drifting away from it.
SwiftUI, Kotlin, React Native and TypeScript. Store submission, review handling and release management are part of the work, not an extra.
How it runs
Typical engagement · 6–10 weeks
Week 1
An intro call, then a written scope: who it is for, what it must do, what it will cost. Fixed before anything is built.
Week 1–3
Flows, screens and a visual direction. You sign off on a clickable prototype before engineering starts.
Week 3–8
A build in your hands every week — TestFlight and Play internal testing. Real software, not status reports.
Launch
Store submission, review handling, monitoring through the first weeks, then a clean handover of code and accounts.
Notes
All notesapp-ads.txt has one requirement everybody misses: the crawler will not follow a redirect. How that happens by accident on Cloudflare.
Authentication error [code: 10000] against an account ID I no longer had access to. The credentials were never the problem.
The studio
The person who reads your brief is the person who designs it, builds it and ships it. Nothing is translated between a designer, a developer and an account manager, because there is no chain to translate it along — and that is the reason two engagements is a limit rather than an ambition.
Why a betta
A betta is small, precise and completely in command of the water it occupies. That is the shape of this studio: no growth targets, no bench to keep busy — just a short list of projects done properly.
Source, repositories, developer accounts and design files transfer to you on delivery.
Scope and cost agreed in writing before work starts. No surprise invoices.
A hard limit on concurrent projects, so yours is never queued behind five others.
Send a short brief. It is read by the person who would do the work, and answered personally within 48 hours — never routed into a queue. If you would rather see how engagements are shaped and priced first, start here.