Personal software is here, and you can build yours this week. Grab the setup guide: two routes, four files, every account.

A guy in Amsterdam got tired of not knowing when his ferry would actually show up. He’d already built himself an app off the published timetable, and it worked right up until he learned what every regular on that route knows: the ferries run late, they get cancelled, and the timetable is decoration. Real-time ship positions are sold commercially for hundreds of euros a month. Then he found out ships broadcast their own position every few seconds, in the clear, because the law requires it so they don’t hit each other. An antenna and a Raspberry Pi to listen in cost about €200. He bought the kit.

Around the same time, Josh Pigford shipped an app built for one house. His. It knows the appliances, the plants, the yard. It writes the jobs the house needs that week. Show it a photo of something broken and it helps diagnose the repair.

Neither is a startup. Neither needs a second user. Both are aimed at something no product on the market was ever going to solve for one household.

We have entered the era of personal software.

You know there’s a recurring part of your life that works badly. The school bus never shows up when the schedule says it will. The history of your house lives across appliance manuals, text messages, photographs, and your own imperfect memory. Good luck finding any of it. A spreadsheet at work has become a small country with its own laws. Or your parents need a way to do one thing without clicking through six menus.

We all know that AI coding is faster. What matters is that now the average person living next to a problem can finally do something about it. What’s been missing is the route from “I wish this existed” to something running on a phone, a laptop, or a small box in the house.

That route has a few places where people get hurt, and they’re all early. Choose a native phone app when a link would have done, and you’ll pay the App Store tax before you ever find out whether your spouse likes the thing. Let the builder pick where your data lives, and you’ll find out later that moving it means copying it across by hand. Every record, every photo, every user account. Hit publish thinking a link nobody knows is a link nobody can open, and you’ve put your household records on the open web.

None of that requires you to become an engineer. It requires you to make a handful of decisions on purpose instead of by accident: what shape the thing is, where the data lives, who can open it, and how small the first version should be.

So here’s the recommendation up front: if you’re nontechnical and building your first personal web app, start with Lovable. It’s the shortest path I know from an ordinary description to a working interface you can open, change, and publish. It strips out enough setup that you find out whether the thing helps you before you spend a weekend assembling a development environment.

Here’s what’s inside:

• Build the App: the setup guide, plus the skill. The step-by-step companion that runs both routes, the fast one through Lovable and the assemble-it-yourself one through a coding agent, and tells you which your project wants. Plus the skill that makes your agent write instructions a human can follow.

• Start with the change you want. Seven plain-language questions that pull the technical shape out of your idea before you touch a single tool.

• The five kinds of personal software. Local tool, web app, native app, background service, hardware project, and how to tell which one your wish honestly is.

• Lovable vs Replit, Bolt, Codex, and Claude Code. The conditions that send you to one of the others, or to Expo or a Raspberry Pi, so you leave for a reason and not out of FOMO.

• Database, authentication, and hosting explained. The seven parts you need to be able to name, in English, so you can hear when a builder is making a decision that costs you later.

• The four files that make an AI show its work. Plus the standing instruction to paste into your builder on day one, so choices about data, cost, access, and deployment land in front of you instead of inside the code.

Bring one wish with you. The rest of this is the route from that wish to something running.