
Academy track
Ship an app without a dev team

One sentence the app has to earn, a data model, a generated build, doors the database locks, and one real person using it without you.
- 5 steps
- 6 hours 45 minutes in total
- A check you run at the end of every step
Step one is open to everyone, in full. No account, no card.
The other 4 steps are included in Membership, £79 a month.See Membership
By the end of this track you will have
- Step 1One sentence, one named person who needs it, and a written list of what your app will refuse to do.
- Step 2Every entity, every field and every relationship written down on one page, before a single screen exists.
- Step 3A working app and a written list of every way you broke it, each one fixed or knowingly accepted.
- Step 4Every entity has rules the database enforces, and a second account proves it cannot read the first account's rows.
- Step 5One real person will have used your app without your help, you will have notes on where they stopped, and one change will be shipped because of it.
The running example
Every worked example follows one invented case from the first step to the last: a three-chair dog-grooming salon.
Who it is for
You have an app your business needs, no developer, and the patience to build it with an app builder yourself.
Who it is not for
Not for you if you want a phone app in the app stores by Friday. This ships a web app one real person uses.
The steps
Each one ends with a check you run yourself. The box is yours to tick when it passes.
0 of 5 steps ticked, kept in this browser
- Step 1.Write the one sentence the app has to earn45 minutesOpen to everyone
Done means
You have written down what the named person said back, and you have marked each of your four slots present or absent against it. Four present is a pass. A slot they never mention is not in the sentence yet, and a slot they add that you never wrote is where the sentence leaks.
- Step 2.Model your data before you generate a screen90 minutes
Done means
You can trace one real record end to end through every link and land back on the owner, and no field name appears in two entities except the link identifiers. If you find the same fact stored twice, fix it now, while it still costs ten minutes.
- Step 3.Generate it, then break it on purpose120 minutes
Done means
Your break file has at least twelve entries, and every entry is either fixed or marked known with a reason you would say out loud to a user. Zero entries means you did not try. Twelve is normal for a first build.
- Step 4.Lock the doors before anyone walks in90 minutes
Done means
Account two asks for account one's record by identifier and gets nothing back. Not an empty screen. Nothing. Run the same check on every entity you have, including the ones you think hold nothing sensitive.
- Step 5.Put it in one real person's hands60 minutes
Done means
Your note file has the total run time and a timestamp against every pause, and you have marked the longest one. A run with no pauses is a pass, and you write down the total time instead. A run where you spoke does not count, and you do it again with somebody else.
I keep this tick in this browser and send it nowhere. It goes when you close the browser.
Included in Membership
The rest of this track is included in Membership.
Step one is open to everyone, in full. Every step after it opens on a member account.
Included in Membership — £79/month.
What comes next
If you built it on Base44, next is the same work inside Base44 itself, every table locked and every key behind a function that checks who asked.
See all the tracks