Why You Must Publish
Between "it opens on my computer" and "there's a link other people can open" lies the step where most people give up. Only after publishing do you hit the real problems: buttons too small on a phone, a blank page for someone else, data gone after refresh. None of these ever show up on your own computer.
More importantly, a link is something you can show anyone. Week 2's mini app is the same: when it's done it runs on a phone, not in a simulator.
Publish for Free, in Five Minutes
Static pages (which is what your index.html is) have plenty of free hosting: Cloudflare Pages, Vercel, and GitHub Pages all work. Pick one, sign up, then let Claude Code walk you through it:
「把这个项目发布到 Cloudflare Pages。我已经注册了账号。一步步告诉我要点什么、要在终端跑什么，每一步等我确认再进行下一步。」It will guide you: push the code to GitHub (or upload the folder directly) → connect the repo on the hosting platform → wait a minute or two → get a link like xxx.pages.dev.
Three Checks After Publishing, and Submitting the Assignment
Once you have the link, do three things. Skip none of them:
1. Open the link in your phone's browser, not on the computer.
2. Add two to-dos, refresh, and check they're still there.
3. Send the link to a friend and have them open it and send you a screenshot.
All three pass, assignment done. Submit the link plus three screenshots (opened on phone, after refresh, friend's screenshot) as this week's assignment.
自测 · 学完检查一下
想真正动手做题、记进度、攒连胜？到互动课里练。
Zhou's to-do list runs perfectly on his own computer, so he thinks the assignment is done. What's this lesson's view?
答案：Not done. Without publishing there's no real-world verification and nothing you can show anyone
The assignment is defined as "a link someone else can open". Running locally only proves the code has no syntax errors. A real phone, someone else's browser, data after refresh: you only find out after publishing. Docs and tests aren't acceptance items for this lesson.
When asking the AI to help publish, why add "wait for my confirmation before each next step" to the instruction?
答案：Publishing involves your accounts and public actions outside the project, so check each step before letting it through
This is Lesson 1's permission test in practice: pushing code and deploying are outside the project folder and not easy to undo. Confirming step by step isn't slow. It's seeing the consequence of each step clearly.
After publishing, Chen opens the link in the browser on his own computer, everything works, and he submits the assignment. Which check did he skip that's most likely to expose a problem?
答案：Opening it on a real phone. Working on a computer doesn't mean the buttons are big enough or the layout holds on a phone
Lesson 2's acceptance criteria included "no horizontal scrolling in phone portrait mode", and that can only be checked on a real device. Viewing source, screenshots, and redeploying won't expose layout problems.
True or false: a friend opens the link and says "the page is blank", but it works fine when Chen opens it himself, so it's the friend's phone and can be ignored.
答案：False
"Works for me" is the most common illusion: maybe the cache is showing you an old version, maybe your friend's browser doesn't support something in the code. If someone else can't open it, it's a real problem. The right move is to get a screenshot and hand the exact symptom to the AI to investigate.