There's a moment in almost every app project where the client asks, "so once it's built, it's in the App Store, right?"
Not quite. Building the app is the part everyone plans for. Getting it into people's hands involves a road that nobody warns you about, with tolls, checkpoints, and a customs inspection run by Apple. I've shipped apps through this gauntlet, so let me draw you the actual map. No horror stories, just what the road looks like so none of it surprises you.
Stage one: the build (the part you expected)
This is the part people picture: designing screens, writing code, connecting the database. With modern tools, one codebase can produce both the iPhone and Android versions, which roughly halves the old cost of going mobile. For a focused small business app, this stage is measured in weeks, not the quarters it used to take.
What matters most here isn't speed, it's ruthlessness about version one. The apps that ship are the ones that start small. The ones that die in development are the ones where version one tried to do everything.
Stage two: the paperwork nobody mentions
Before anything reaches a store, you need developer accounts. Apple charges $99 a year, Google a one-time $25, and both involve identity verification that can take days, longer for businesses than individuals. You'll also need the unglamorous supporting cast: an app icon in a dozen sizes, screenshots for multiple device sizes, a written description, and a privacy policy page, which the stores actually check.
None of this is hard. All of it is a week of calendar time if you start late, or zero if you start it in parallel with the build. Guess which one people do.
Stage three: TestFlight, where apps grow up
Before the public sees anything, the app goes to real phones through beta testing, TestFlight on iOS. This stage is where the app meets reality: the button that's too small for actual thumbs, the screen that's confusing to everyone except the people who built it, the crash that only happens on older phones.
Every hour spent here is repaid at launch. An app that skips a proper beta ships its bugs to customers and its bad first impressions to the app store reviews, which are permanent.
Stage four: review, the customs checkpoint
Then you submit, and Apple reviews your app. A human at Apple opens it, pokes at it, and decides. Usually this takes a day or two. Sometimes they reject, and the rejection reasons range from legitimate (a broken flow they found) to bureaucratic (a guideline about how you worded a button). Rejection isn't failure, it's a revision note. You fix, resubmit, and typically pass on the next pass. Google's review is similar and generally faster.
Plan for review to take a week of calendar time, and be pleasantly surprised when it takes two days.
Stage five: alive, and staying alive
Here's the part that separates real app projects from abandoned ones: launch is the start of maintenance, not the end of work. Operating systems update yearly and occasionally break things. Users find edge cases. Small fixes can often ship instantly through over-the-air updates without another store review, which is a genuine gift, but bigger changes go back through the checkpoint.
Budget for a living thing, not a monument.
The realistic timeline
Idea to App Store for a focused small business app: two to three months, with the build being weeks of it and the pipeline being the rest. Anyone promising the whole road in two weeks hasn't walked it.
Thinking about an app and want the map applied to your specific idea? I'll walk you through it straight, including whether your idea should even be an app. Book 30 minutes at ctfdesigns.com/book. Bring the idea, I'll bring the potholes.