Do not start with a home page. Start with the smallest useful flow.
For a first mobile app, I would do this in order:
Write a one-page spec before opening any builder:
Who is the exact user?
What painful thing are they trying to do?
What do they do today instead?
What is the single action your app must make easier?
What result would prove the app worked?
If you cannot answer those five, a home page will only hide the uncertainty.
Draw only three screens first:
start screen: what the user sees when they open the app
action screen: the main thing they came to do
result screen: what success looks like after the action
No settings, profiles, dashboards, social feeds, or payments yet unless they are essential to the main action.
Prototype before coding.
Use Figma, pen and paper, or a quick Lovable/Replit prototype. Show it to 3-5 people who would actually use the app and ask them to do the task without explaining it. Watch where they get stuck.
Build the MVP with a boring stack.
For mobile, I would use Expo / React Native so you can ship iOS and Android from one codebase. Use Supabase or Firebase for auth/database/storage. Add PostHog or simple event logging from day one so you can see whether people complete the main flow.
Seven-day starter plan:
Day 1: define user, problem, and main action. Day 2: sketch the three-screen flow. Day 3: test the sketch with real people. Day 4: build clickable prototype. Day 5: test again and remove confusing parts. Day 6: build only auth + main action + result screen. Day 7: put it on TestFlight / internal Android testing and give it to 5 users.
After that, improve based on where people failed, not based on features you imagined before testing.
If you reply with the actual app idea, I can reduce it into a first MVP spec and the first three screens.
Do not start with a home page. Start with the smallest useful flow.
For a first mobile app, I would do this in order:
If you cannot answer those five, a home page will only hide the uncertainty.
No settings, profiles, dashboards, social feeds, or payments yet unless they are essential to the main action.
Use Figma, pen and paper, or a quick Lovable/Replit prototype. Show it to 3-5 people who would actually use the app and ask them to do the task without explaining it. Watch where they get stuck.
For mobile, I would use Expo / React Native so you can ship iOS and Android from one codebase. Use Supabase or Firebase for auth/database/storage. Add PostHog or simple event logging from day one so you can see whether people complete the main flow.
Day 1: define user, problem, and main action.
Day 2: sketch the three-screen flow.
Day 3: test the sketch with real people.
Day 4: build clickable prototype.
Day 5: test again and remove confusing parts.
Day 6: build only auth + main action + result screen.
Day 7: put it on TestFlight / internal Android testing and give it to 5 users.
After that, improve based on where people failed, not based on features you imagined before testing.
If you reply with the actual app idea, I can reduce it into a first MVP spec and the first three screens.