Maps to: SYSTEM.md Phase 1 (app-research) Goal: leave this lesson with one clear paragraph describing an app you're actually going to build.
Why this phase exists
Every app in this system starts here, whether it's built in Swift or (like this course) React Native — market/idea validation doesn't depend on what code the app is written in. SYSTEM.md Phase 1 shares the exact same app-research skill as the native Swift system for this reason: a good app idea is a good app idea regardless of stack.
What makes a good beginner app idea
- A real frustration, not a hypothetical. "I keep forgetting to drink water" beats "an app for productivity" every time — specificity is what makes the next 8 lessons concrete instead of vague.
- One core feature, not five. You will build ONE thing that works well. Everything else is a "maybe later."
- No account system required. Login/signup adds real complexity (Phase 7's account-deletion requirement, for one) that isn't worth it for a first app. Local-only apps are completely valid.
Worked example: the Habit Tracker
This course demonstrates every lesson on one running example: a Daily Habit Tracker. The one-paragraph concept:
"An app where I can add habits I'm trying to build (like 'drink water' or 'read 10 minutes'), and each day I tap a habit to mark it done. The app shows a streak count for each habit so I can see how many days in a row I've kept it up. No accounts, no login — just habits and streaks, saved on my phone."
Notice what this paragraph does: it names the ONE core feature (mark a habit done, see a streak), explicitly rules out scope creep (no accounts), and describes something a real person would actually use. Every lesson from here on builds this exact app, one phase at a time.
Validate the idea with Claude Code
Ask Claude Code to use the app-research skill (it's shared with this system's native-Swift portfolio — see docs/course/05-skills-reference.md Part 3) to check: are there similar apps already? What do they do well or poorly? This isn't about avoiding competition — plenty of great apps have direct competitors — it's about knowing what you're building relative to.
Try this prompt:
I want to build a simple daily habit tracker — add habits, tap to mark done each day, see a streak count. No accounts. Use the app-research skill to check what similar apps exist and what I should know before I start.
Deliverable
One clear one-paragraph app concept — the exact deliverable 04-workflow-course-overview.md Module 1 asks for. If you're following along with the Habit Tracker, you already have it (above). If you're building your own idea, write your paragraph now, in the same shape as the example: what it does, what the ONE core feature is, and what you're explicitly leaving out.
Apply to your own idea
Write your own one-paragraph concept using the same three rules above (real frustration, one core feature, no account system needed). Run the same app-research prompt with your idea substituted in. Don't move to Lesson 2 until you have this paragraph written down somewhere you can copy from — you'll need it verbatim when you scaffold your project.