Module 1 was the setup and the win. The rest of the course builds the app and then ships it. Module 2 gives it shape. A file in the app folder is a screen; three tabs that work; a form that looks like an app rather than a tutorial. Plus the lesson no competing course has: what to do when the agent itself is the bug. Module 3 makes the data survive. Entries still there after a restart, a history you can search and edit, and the airplane-mode test. Module 4 is the phone's own hardware. A photographed receipt, an evening reminder, your own icon and name — and Claude screenshotting your running ap

What you just learned

The full cost map, up front: nothing through module 5, twenty-five dollars once for Play, ninety-nine a year for Apple, both optional. Claude Code has no free tier, so the free lessons were designed around it rather than pretending otherwise. Node, Git for Windows and Claude Code are the whole toolchain, and a physical Android phone replaces the emulator entirely. npx create-expo-app@latest then npx expo start puts a real app on a real phone, with --tunnel as the fallback when a firewall blocks the local network. Project instructions live in AGENTS.md, which CLAUDE.md imports, and a change to

Nagbabasa ka bilang guest — sa device na ito lang nase-save ang progress.

Mag-sign up nang libre para mapanatili ito

Module 1 recap

Libre3 min basaLesson 6 sa Ang app mo sa phone mo ngayong gabi

Two minutes to fix what you now have: an app on your own phone, a toolchain that works on a Windows laptop with 8GB of memory, and a full, unhidden picture of what the rest of the course costs.

An hour ago you had a laptop and a phone. You now have a project that runs on the phone, updates itself when you save, and answers to plain English.

The order matters. You saw the money first — every charge in the course, both optional, both at the end, and the one nobody else mentions: Claude Code has no free tier, so lessons 1 to 3 were built to need no paid account. Nothing later can surprise you on a bill, because you have already seen the bill.

Then the toolchain, and one decision inside it that will save you an afternoon: no emulator. An 8GB Windows laptop cannot run Android Studio and a virtual phone without swapping to disk, and there is a public report of four hours lost to exactly that. Your phone is the test device, and it is the thing you can hand across a table, which no emulator has ever been.

Then the win. npx create-expo-app@latest, npx expo start, a QR code, an app in your hand — and --tunnel in your pocket for the Windows firewall that stops a good number of people at precisely that step.

And then the part almost nobody knows about yet. create-expo-app wrote AGENTS.md, CLAUDE.md and .claude/settings.json for you, because directing an agent to build a mobile app is now the supported workflow rather than an experiment. You added four rules describing your actual machine, started Claude inside the project so it read them, and changed a screen by asking.

Where this goes next

Module 1 was the setup and the win. The rest of the course builds the app and then ships it.

Module 2 gives it shape. A file in the app folder is a screen; three tabs that work; a form that looks like an app rather than a tutorial. Plus the lesson no competing course has: what to do when the agent itself is the bug.
Module 3 makes the data survive. Entries still there after a restart, a history you can search and edit, and the airplane-mode test.
Module 4 is the phone's own hardware. A photographed receipt, an evening reminder, your own icon and name — and Claude screenshotting your running app and tapping on it, which is the answer to "the model cannot see the phone".

Pagsasanay

Buksan ang Claude Cowork sa sarili mong computer at subukan ito sa totoong mga file. Nagtatapos ang bawat module sa isang checkpoint kung saan isusumite mo ang ginawa mo.

Buksan sa Claude

SusunodA file is a route

Module 1 recap

Where this goes next

What you just learned

Progress sa Pag-aaral0%

Sa module na ito