W20: Shipping, and What Comes Next

A cake that never leaves the kitchen feeds nobody. Until it is on a plate, in front of someone, it is not finished. Software is the same. Many people can make an app work on their own computer. Fewer put it in other people's hands, explain how to use it, and keep it alive. That is shipping, and it is a skill you can learn.

What Shipping Means

R16: Shipping is a Skill says it plainly: many can code, fewer can ship. Shipping means someone else can find your app, understand it, and use it without you standing next to them.

The Checklist

Before you send the link to anyone, go through it. Most items are one request to Pi, or one command.

It works - uv run pytest passes. uv run pyright passes. No task left "Not verified" without a reason you understand. - You used every page yourself, as a new user would, at phone width and on a big screen (W06). - You read every page in Japanese too, and asked a Japanese speaker to check the words (W10).

It is safe - No secrets in any file or in git history (T43). - If other people use it: logins, ownership checks and HTTPS (W17). If not, it is shared only with tailscale serve. - The data is backed up somewhere other than this computer, and you have restored a backup once (W08).

People can use it - It is online the right way for its kind (W16), and installable on a phone (W13). - A README that says what the app is, who it is for, how to run it, and what it does not do yet. Ask Pi: "Write a README for a person who has never seen this app." Then read it as that person. - Known limits are written down, not hidden. "Works offline for reading only" is honest and fine.

You can find your way back - Everything is pushed to GitHub (W12). - A version name for this moment. A git tag marks it: git tag v1.0 then git push --tags. Next month, "what changed since v1.0?" has an answer.

Present It

Three sentences go a long way: what problem it solves, one screenshot, the link (R16's last section says more). Watch the person it is for use it without helping. Every place they hesitate is your next request to Pi.

Keep It Simple, So It Keeps Running

R07: Keep Things Super Simple and R21: Tech Entropy warn that code rots: dependencies break, services change, and you forget how your own app works. The stack was chosen to slow that down:

Libraries do get updates, and htmx 4 is young. Pi Workbench will do this step for you soon: updates to the kit's pinned libraries delivered to existing projects, one deliberate step at a time.

Keep Learning Along the Way

You learned this course by building. Keep doing that, and when an idea comes up, go to its lesson. The school has three tracks:

And ask Pi: "Explain what you just did and why, for a beginner" turns any request into a lesson.

Give Back

This Week's Exercise

  1. Go through the whole checklist for your app. Write down every item that is not done yet, and do them one request at a time.
  2. Ask Pi for the README, then give it to a friend and watch them run or use the app from it.
  3. Tag the version with git tag v1.0 and push it.
  4. Send the link to one real person who might use it. Write down their first question.

Key Takeaways

  • Shipping means someone else can find, open, understand and use your app without you there
  • Check it works (tests, types, both languages, two sizes), is safe (no secrets, logins if shared, backups), and is usable (online, installable, a README)
  • Tag versions so "what changed since v1.0?" has an answer
  • Simple, pinned, plain-text choices keep an app running for years; the paperwork is the note to your future self
  • Keep learning from the Tech, AI and Theory tracks, and give back with issues and in Discord