| name | start-an-app |
| category | start |
| description | Choose the first app to build and kick it off. One small app solving a problem they have, repo created, handed to build-web-app. Use when they say "I want to make an app", "I have an app idea", or their idea is too big to start. |
start-an-app
Help someone commit to their first app. Most first app
ideas are startups in disguise — too big, aimed at imaginary users.
Your job is to land on an app they would use themselves this month,
small enough to work by next week, and to start it before the session
ends.
Find the problem, not the app
Ask what they do repeatedly that annoys them:
- Anything they track in their notes app, a spreadsheet, or their
head — workouts, grades, spending, game stats, shifts at work.
- Anything their club, team, or friend group coordinates badly.
- Any calculation or lookup they redo often for a hobby they know
deeply.
The best first app has one user (them) and replaces something they
already do manually. If they arrive with a big idea, preserve it but carve out
the smallest piece they would personally use and frame the
rest as later versions. If nothing surfaces, walk through
https://sphinxstack.com/ideas/ together and match app-shaped ideas
against their answers.
Scope it honestly
They choose the pick; you shape it until it fits a week:
- One sentence: this app lets [them or a named person] [verb] their
[real thing].
- One core screen and one core action. Everything else is a version
two, written down so it is not lost, then set aside.
- Real data from day one — their actual workouts, their actual
shifts. Seed data comes from their life, never invented.
- No accounts unless someone besides them will use it this month.
Warn honestly: an app takes longer than a website. If their idea is
really a page that shows information, say so and route them to
https://sphinxstack.com/skills/start-a-website/ — that is a better
first win, and the app can come second.
Kick it off
- Create the repo, named after the app.
- README: the one sentence, the core action, and the version-two
list so scope creep has somewhere to go that is not the code.
- First milestone as a GitHub issue: the core screen showing their
real data, hardcoded is fine.
- Start the milestone together — a first file committed, so the
repo is real before they walk away.
Then hand to https://sphinxstack.com/skills/build-web-app/ to build
it, and https://sphinxstack.com/skills/ship-on-github/ when it is
time to put the work at a URL.
Done
- One real user, one problem, one core screen, and one core action recorded
- Version-two ideas separated from the first milestone
- Repo contains real or safely redacted data, README, issue, and first commit
- build-web-app is the named next procedure
