LESSON 1 OF THE COURSE IS LIVE
A class by Jeremy Heydon. One sentence becomes a working app, then gets a repository, a real database, secrets handled properly, a deploy, and a live domain. Every prompt, reply, and command is the real transcript, replayed on a screen that looks like the real thing.
Who does what: Claude writes and changes the code. GitHub stores it and keeps every version. Supabase is the database. Vercel builds and hosts the app. You press Next. Nothing advances on its own. Each step plays the way it happened: the prompt types in, Claude thinks, commands run one at a time, the answer streams, and the Mac on the left shows whatever was on screen at that moment.
The app is asked for in plain words. The first version exists in minutes. Every later change is a sentence a user would say.
Claude tests in a real browser, finds a phone-layout bug on its own, names the cause, fixes it, and shows proof at the same size.
Commit, push to a private repo, run a schema in Supabase, pipe secrets into Vercel without ever printing them, deploy, buy and attach a domain.
The right side is a mock of the Claude Code desktop app. The left side is a Mac: menu bar, Safari, Terminal, the editor, a dock. When Claude creates the project, the window minimizes by itself and the folder appears on the desktop. When the schema runs, you see the exact Supabase screens Jeremy saw, including the row-level-security prompt.
One real build per lesson, replayed from the transcript, on a screen that looks like the screen. Lesson 1 is live. The rest are being built the same way: each one is a thing Jeremy actually did with Claude, recorded as it happened.
Describe it, react, verify on a phone, commit, GitHub, Supabase, secrets, Vercel, a domain, a handoff. 14 steps.
A contact that answers with Claude: the API, a key kept as a secret, a cost cap, and what it actually costs per message.
Coming soon
Add to Home Screen, push notifications, and what it takes to get the same app into the App Store and Google Play.
Coming soon
Remote Control from your phone, cloud sessions, and what a sleeping Mac can and cannot do.
Coming soon
Why every change is written down in the same commit, how Claude reads it first, and how it saved this project more than once.
Coming soon
Reading a deploy log, a permission wall, a secret with a newline in it. Judgment, limits, and what you still check yourself.
Coming soon
Thirteen are the verbatim transcript of October 10, 2026. One, the build log, was added at Jeremy's request so students see the habit that keeps a project coherent across sessions.
People who have an idea and no engineering team. Students, clinicians, small business owners, founders. No code is written by hand in this build. The skill being taught is how to describe, react, verify, and ship, and how to keep a written record so the work survives between sessions.
A Mac or PC, a Claude subscription with Claude Code, and free accounts on GitHub, Supabase, and Vercel. The domain is optional.
A working messaging app you built, live on the internet, wired to a real database, with a build log you can hand to the next person.
Every step is labeled. Verbatim means it happened exactly that way. Nothing is staged. The bugs and the blocked commands are in the replay because that is what building looks like.
Founder of Recovery Transparency Technologies LLC in Wilmington, North Carolina. Builds and ships production software with Claude: a recovery accountability app on both app stores, an outreach tracker, a study-guide platform, and this class. Psychology student at UNC Wilmington.