The first seven days: start the clocks that run without you
I am an esthetician. I built my app between clients, with no prior tech background, and got it into both app stores. The thing I would most like to go back and tell myself has nothing to do with code.
It is this: in week one, you are not really building. You are starting clocks.
There are two kinds of time and they behave completely differently
Work time is time that passes because you are working. Screens get built, text gets written, bugs get fixed. If you stop, it stops. Put in twice the hours and you get roughly twice the progress.
Wait time is time that passes whether you are working or not. A form sits in somebody's queue. A verification goes off to be checked. A review period has to elapse. Your effort has no effect on it at all. The only thing you control is when it starts.
Almost everyone starting their first app spends week one entirely on work time, because work time is the fun part. You can see it happening. Wait time feels like admin, so it gets pushed to the end, which is exactly when it hurts most.
Why the order matters so much more than the effort
If you start your waits on day one, they run underneath everything else. You build, and while you build, the clocks tick. By the time you are ready, several of them have already finished without you noticing.
If you start them in week six, they run end to end, one after another, with you sitting there refreshing. Nothing you do makes them faster. You have turned background time into foreground time, and the only thing you can spend on it is patience.
That is the same number of total days, arranged two different ways. One arrangement finishes a month earlier.
This is the single biggest reason I think the order is the hard part now, and not the code. The code is genuinely solved. AI writes it. Nobody can write you a shortcut through a waiting period.
How to spot a clock
You do not need a list of them memorised. You need one question, asked of every task:
Does this finish because of something I do, or because somebody else gets round to it?
If the answer is "somebody else," it is a clock, and it should be started as early as you can possibly start it, even roughly, even before you are sure what you are building.
Three shapes come up again and again:
Anything that verifies who you are. Registrations, identity checks, business lookups. These involve a third party confirming something about you, and they take as long as they take. They also do not care in the slightest whether your app exists yet.
Anything with a queue. Reviews, approvals, submissions. There is a person or a process at the other end and you are in line.
Anything that needs other human beings. This is the one people never see coming, because it does not look like paperwork. If a step requires real people to do something over a period of days, you need those people lined up before the step starts, not after. Finding them is work time. Them doing it is wait time. The one that cost me the most is in its own post, because it is the clearest example of a rule that costs a month if you meet it late.
The part that feels wrong and is not
You can start most of these before your app does anything.
That feels premature. It feels like getting a business card printed before you have a business. But a registration does not inspect your progress. It processes your paperwork. Filing on day one and filing in week six produce the same outcome, five weeks apart.
I want to be fair about the exceptions, because there are some. You cannot submit something that does not exist yet, so the final submissions genuinely do belong at the end. And a few of these have fees attached, so starting early means paying earlier and possibly paying for a stretch where you are not using the thing yet. That is a real cost and you should go in knowing it. I wrote about what the whole thing actually costs separately, and the honest version is that it is small and knowable rather than free.
Also worth saying plainly: requirements change. The rules I planned around during my build are not guaranteed to be the rules this month. Fees get updated, review times move, testing requirements get revised. Before you rely on any specific number, go and read the current policy page yourself rather than a blog post, including this one.
What week one actually looks like
Not "build the home screen." More like: sit down with what you intend to make, work out which parts of getting it live depend on other people, and start every single one of those today, badly if necessary.
Then go and build, with the clocks already running.
That reframing is most of what separates a build that keeps moving from one that spends its last month waiting, and it costs nothing to apply. If you want the ordered version, with what to file, in what sequence, and what each one blocks, the free walkthrough of the first steps is here.