About this course
AI App Building treats a student's project as a product rather than an exercise. Eight weeks that begin with the question most courses skip — who is this for, and how will you know if it works — and end with the app in the hands of real users. Students design, build, deploy, watch strangers use the thing they made, and then fix what those strangers broke. It is the middle rung of the pathway: more independent than Vibe Coding, less demanding than the bootcamp's terminal-first workflow. Students finish with something portfolio-ready, which for this age means an app with actual users and a write-up explaining the decisions behind it.
Is this the right fit?
- Who it’s for
- Students aged 12–17 who have built something small and want to build something people actually use.
- Prerequisites
- Comfort with a basic build-and-deploy loop. Our Vibe Coding Course covers this; so does prior self-taught work.
- Tools students use
- Replit, GitHub + Copilot (13+), ChatGPT/Codex (13+ with consent)
- Where it leads
- Most students go on to Claude Code Bootcamp.
What students walk away with
- A launched app with real users, not a portfolio screenshot
- The ability to scope a product — deciding what not to build is most of the skill
- User testing: watching someone struggle with your app without explaining it to them
- Handling accounts, data, and the parts of an app that break under real use
- A written product case study covering the problem, the decisions, and the results
What a session looks like
- 0:00
Metrics check
Who used your app this week? What did they do? What went wrong?
- 0:10
New technique
The week's product or engineering skill, taught live.
- 0:30
Guided build
Students implement against their own product while the coach circulates.
- 0:55
Explain-back
Each student defends one decision they made this week — not just the code.
- 1:05
Build lab (optional)
A 45-minute open work block with a coach on call.
Curriculum
Week 1 — Who is this for?
Picking a real problem and a real person who has it. The scoping week.
Week 2 — Design before build
Sketching screens and flows before generating a line of code.
Week 3 — Build the core
The one thing the app must do, done well, deployed live.
Week 4 — Accounts and data
Logins, storage, and keeping one user's data away from another's.
Week 5 — First users
Handing the app to five real people and watching them use it silently.
Week 6 — Fix what they broke
Turning observations into a prioritised list, then working it down.
Week 7 — Polish and performance
Mobile, loading, and the details that decide whether people come back.
Week 8 — Launch and case study
A public launch and a written case study of the whole build.
What’s included
- 8 live small-group classes, capped at 6 students
- 8 optional build labs with a coach on call
- Weekly explain-back assessment with written feedback to parents
- Deployment, hosting, and a custom domain for the student's app
- A student showcase entry and a written product case study
How to join
- Book a free consultation. We learn about your child, answer your questions, and recommend a starting point — no commitment, no pressure.
- We recommend a course and an age band after the call, based on your child’s experience and goals rather than a form they filled in.
- Reserve a seat when enrollment opens. Classes are capped at six, so bands fill in the order consultations are booked.
Questions first? Email hello@redwoodacademy.ai and a coach will reply.
Frequently asked questions
How is this different from the Vibe Coding Course?
Vibe Coding gets a first app deployed. This course treats the app as a product: real users, real feedback, and the decisions about what not to build. Students who have finished Vibe Coding usually take this next.
Who are the real users?
People the student recruits — friends, family, a club, a team. We coach them through running a proper test session, which mostly means watching in silence rather than helping.
Does my child need a good idea before starting?
No. Week one is scoping, and plenty of students arrive with nothing or with an idea that gets replaced. Arriving with a problem they genuinely care about does make the eight weeks better.
What counts as portfolio-ready?
A live app with a public URL, real usage, and a written case study explaining the problem, the decisions, and what happened when people used it. That combination is what admissions readers and internship reviewers respond to.