What "Shipped" Means

You have had this feeling: you built something cool — a game, a playlist generator, a poem bot — and then it just sat on your laptop. Nobody used it. Nobody saw it. It stayed a draft forever. That gap between "I made something" and "people can actually use it" has a name in the tech world. Crossing that gap is called shipping.

Shipped vs. Finished

Finished and shipped are not the same thing. Finished means you stopped adding features and the thing works as intended. Shipped means you released it — posted it, published it, deployed it — so that someone outside your own machine can reach it and benefit from it. A game you complete but never upload is finished. A game someone else can actually play online is shipped. Shipping is the act that turns your work into value for other people. Until something is shipped, it only has value to you, and only on your device.

Consider Mateo, a seventh grader who built a quiz app using an AI assistant. He spent three weeks adding features, fixing bugs, and making it look great. Then school ended and the app never left his Downloads folder. Compare that to Priya, who built a simpler quiz app in four days, put it on a free hosting site, and shared the link with her class. Students used it the same week. Priya shipped. Mateo did not. Priya's version had fewer features. But it created real value — students studied with it — while Mateo's more polished version created none. Shipping wins.

Why Shipping Is Hard

Shipping feels scary for a few reasons. First, once something is public, other people can see its flaws. That vulnerability is real, and every builder feels it. Second, the last stretch before shipping — deployment, writing a README, sharing a link — involves unfamiliar steps that feel less creative than building. Many builders skip those steps indefinitely. Third, perfectionism. There is always one more thing to add. Experienced builders learn that "good enough to be useful" beats "perfect but never released" every time. In this module, you will learn the skills to close that gap: planning, building in slices, testing, getting feedback, and releasing responsibly. Each lesson builds toward one goal — getting your work into the world.