MISSION FILE // STG-01 · MOBILE APP
A Flutter app built by the person you talk to — in both stores, with a build on your phone every Friday while it happens.
00 / TELEMETRY
The currents worth steering by — and what they change about how this mission gets flown.
Flutter now ships to iOS, Android, web, and desktop from one codebase, with rendering the platforms can't tell apart. The old trade-off was write twice or feel cheap. It's gone, and budgets built for two native teams are quietly funding one.
Apps that ship fixes weekly keep their ratings; apps that ship quarterly answer every 1-star review with 'fixed in the next release.' One pipeline, CI from week one: a bug fixed Monday is live everywhere Friday.
Users expect the smart part inside the product: summaries, search, assistants. Flutter plus a typed API makes wiring model calls into real screens a normal feature.
00 / WHY THIS PAD
The person who scopes your app writes its code. Weekly demo, direct chat in between, decisions in days — no account manager translating in both directions.
You hold the app while it's built. Course corrections happen when they cost an afternoon, not a milestone.
Store listings, review submissions, crash reporting, analytics — wired before launch, not after the first bad review. You own the repo and the store accounts.
One codebase means one bug list and one release train. That's the honest math behind the price, and it keeps being true after launch.
00 / FLIGHT PLAN
T-4DISCOVER
A 30-minute call, then a one-page mission brief: scope, risks, timeline, price.
T-3DESIGN
Flows into a clickable prototype. You react to screens, not promises.
T-2BUILD
Flutter against a typed API. CI green from week one, a Friday build on your phone.
T-1SHIP
Store submissions, monitoring, docs, handover. Your repo, your keys, support window after.
00 / QUESTIONS
Because two native codebases cost roughly double to build and maintain, and for almost every product the difference is invisible to users. Where a mission truly demands native, Swift is on the table. That's an honest scoping conversation.
A typical MVP flies in 6–10 weeks. The mission brief gives you the real number, with the risks that could move it, before you commit.
Yes — Flutter Web can share the same codebase when that's the right call. Sometimes a separate Next.js site is the better tool; you'll get a straight recommendation, not an upsell.
The app is yours — repo, store accounts, CI. Some founders keep a small monthly retainer for updates; others take it fully in-house. Both are normal, neither is required.
00 / COMMS
Send two sentences about the app. The mission brief comes back free.
