Lesson 6 of 6
You have a working local app
Recap what you built with Claude Code, learn what deployment means, and get notified when the deployment course launches.
By the end: You know what you accomplished in this track and how Course 3 will help you put the app on the internet.
What you can do now
Working through this track you:
- Installed Node.js and the Claude Code CLI, and signed in from your terminal.
- Gave Claude its first task and read the plan before approving file changes.
- Learned how the read, propose, and edit loop works against real files on disk.
- Connected an MCP server and saw how new capabilities arrive as new permissions.
- Asked Claude to add tests, ran them with
npm test, and read the output.
That is a full local loop without leaving the terminal: idea, change, read, test. Many paid prototypes never get that far.
What "deployment" means
Right now your app runs on localhost, which means "this computer only." Deployment means putting the app on a server with a public URL so other people can open it in a browser, the same way they visit any website.
Deployment also brings new questions: custom domains, HTTPS, databases, environment variables, and backups. Course 3 will walk through those topics in the same step-by-step style.
Course 3 preview
Course 3: Getting to production is available on the Learn hub. It walks you from the app you built in this track to a public URL, environment variables, a custom domain, and HTTPS, with a troubleshooting path when a deploy goes wrong. If you built a mobile app, the same course includes a separate mobile deployment track (App Store and Google Play) from the Course 3 page. Open Course 3
If you ship anything that connects to real systems (a database, GitHub, payments), revisit the MCP lesson before you do. Production access is not the place to discover that an agent has more permission than you meant to grant.
Keep building here
Until Course 3 ships, keep practising the loop: instruct, review, test. Small apps teach faster than big ones. Pick the next annoyance in your terminal-based workflow, describe it the way you did in Lesson 2, and let Claude prove the concept.
You can always return to the Claude Code track hub to revisit a lesson or mark lessons complete for your own sense of progress.
Your progress saves in this browser only. Clearing site data will reset it.
You finished Build with Claude Code. How was it?
Your feedback is anonymous unless you provide an email.