The 12-week cohort

How students build

Students do not build throwaway exercises. They work alongside the program’s own production apps, contributing features, testing, design, and content under adult review, using modern AI-assisted app-building tools with instructors and volunteer mentors.

Enrollment details such as age range, class schedule, meeting location, and the date of the first cohort will be posted here once they are set. If you want to be notified, contact the office.

The curriculum is organized in four phases. The week ranges below describe a typical 12-week cohort.

Phase 1 · Weeks 1–3

Launch Pad

Students learn digital foundations, laptop care, online safety and privacy, and responsible AI use. They practice design thinking and interview real users — musicians, families, and others — so the work starts with a human problem, not a blank screen. Students leave able to explain a user’s problem and sketch a solution.

Phase 2 · Weeks 4–7

Build Lab

Ideas become working prototypes. Students use AI-assisted app-building tools, edit code locally, keep version history with GitHub, work with simple databases, and shape visual design. Students leave able to build and save a working prototype with version history.

Phase 3 · Weeks 8–10

Mission Control

Students contribute to a production app such as Center Stage HQ or another Year 1 app: features, testing, accessibility, code review, and deploying updates. Students leave able to ship a reviewed change to a live app.

Phase 4 · Weeks 11–12

Liftoff

The cohort ends with Demo Day for families, musicians, mentors, and sponsors; a personal portfolio; and career exploration with Nashville tech professionals. Students leave able to present their work and name a next step in education or a career.

Moonwalkers Crew

Returning students may join the Moonwalkers Crew, a continuing team that maintains the apps, mentors new cohorts, and takes on more advanced work. This mirrors the cycle of giving back at the heart of the nonprofit’s mentorship program: young people who were once new to the work become the people who help the next class find their footing.

A typical session

Sessions are designed as two-hour blocks:

  • Check-in, snack, and a goal for the day (about 10 minutes)
  • A mini-lesson or guest mentor spotlight (about 20 minutes)
  • Build time in pairs or small teams, with mentor support (about 70 minutes)
  • Show-and-tell and peer feedback (about 15 minutes)
  • Saving work, a commit to version control, and a short reflection (about 5 minutes)

Youth safety, privacy, and responsible AI

  • Supervised access. Several AI tools set a minimum age of 18 for individual accounts. Students will use program-managed accounts under adult supervision. We will confirm each vendor’s age terms, and any written agreements those terms require, before a tool is used in class.
  • Consent. Parent or guardian consent is required for every student under 18, including consent for photos and for any work shown in a public demo.
  • Adults. All staff and volunteers complete background checks and youth-protection training. No adult is alone with a student.
  • Data. Student work is published only with consent. Apps are reviewed for privacy before launch, and no student’s personal data is placed in a public app.
  • Ownership and credit. Production apps belong to the nonprofit. Students are credited for their contributions and keep their portfolio work, under a student-work policy the board will approve.