How a Finished App Reaches You
Here we are, friend — nearly the end of the tour. We've walked every room of the restaurant: the dining room you touch, the kitchen that works, the waiter carrying notes back and forth, the pantry where the data sleeps. But a finished restaurant with the doors still locked feeds nobody. The last real job is to open up so people can actually come in.
So today's question is simple: how does a finished app reach you? There are two main paths, and which one an app takes depends on where it lives.
Path one: a web app goes live on a server
Remember the server — the computer that stays on all the time, waiting to hand its files to anyone who asks. Think of it as a kitchen that never closes.
To send a web app out into the world, builders publish it — they copy the finished app's files onto that always-on server and give it an address (the kind of web address you type into a browser). The moment those files land, the app is live.
Here's the everyday picture. Publishing a web app is like a restaurant flipping its sign to "Open" on a busy street. The doors unlock, the lights come on, and anyone walking by with the address can step inside — no invitation, no waiting. They just visit the link, and they're in.
That's the gift of a web app: nothing to install. The person opens a browser, types the address, and the server hands over the app on the spot.
Path two: a phone app goes through the app store
A phone app reaches you a different way. It isn't simply published to an open address — it's submitted to an app store (like the ones built into your phone) and listed there for people to download.
An app store is a guarded marketplace. Picture a big indoor food hall where every stall had to apply to get a counter. The hall's managers don't let just anyone set up shop — each new app is reviewed first. Reviewers check that it works, that it's honest about what it does, and that it's safe before they put it on the shelves.
Only after it passes that review does the app appear in the store, where anyone can find it and tap "Get" to install it onto their phone. That review step is slower than flipping a sign — but it's the price of the trust that comes with a guarded marketplace. 🔦
Updates: the restaurant keeps changing its menu
Sending an app out isn't a one-time event. Apps get fixed and improved constantly — that's an update.
For a web app, an update is quick: the builder publishes new files to the server, and the next person to visit simply gets the newer version. No one has to do anything.
For a phone app, an update is submitted to the store, reviewed again, and then offered to people who already installed it (that little "Update available" nudge you've surely seen). Same guarded path, every time.
The whole voyage, one clean line
Step back and look at everything we've toured. Here's the full journey an app takes:
- The front end gives you something to see and tap.
- The back end does the real work behind the door.
- The data rests in storage, ready to be looked up.
- The two halves talk through requests and responses.
- It's shaped as a phone, desktop, or web app.
- And finally, it reaches you — going live on a server, or listed in an app store.
Front, back, data, doorway, delivery. That's the whole restaurant, from an empty building to a plate in front of a guest.
Your turn
Pick one app you opened today. Trace its journey home to you:
- Did it reach you as a web app (you typed an address or clicked a link, nothing to install) or a phone app (you downloaded it from a store)?
- If it's a phone app, picture the review it had to pass before landing in that guarded marketplace.
- When did you last see it offer an update — the menu quietly changing?
If you can name its delivery path, you've now followed an app the entire way — from the screen in your hand all the way back to where it was made.
Next is our final lesson, and it's the fun one. In Putting It Together, you'll take everything you've learned and sketch a one-page blueprint of your own app idea. I'll keep the light on for you. 🐙
Stuck or curious?
Ask Pip about this lesson — tap the porthole bottom-right.