Skip to content
James GodwinProduct design & full-stack development
← All essays

· 2 min read

The app is the visible part

James Godwin

A small red app screen stands at the entrance to a vast dark maze, with a lone person looking on.

A friend once told me he wanted to vibe-code the next Airbnb.

He had watched a tutorial where someone built an Airbnb clone with Codex, Supabase and Stripe. Listings, a booking screen, a map, a working checkout. It looked like most of the product, and in a sense the tutorial was honest. You really can build that part quickly now.

What I kept thinking about was everything the screens don’t show. Who holds the money between the booking and the stay? What happens when a guest disputes the card payment after the host has already been paid? Who checks that a listing is real, or decides what happens when a stay goes wrong? How do you find the first hosts when there are no guests, and the first guests when there are no hosts?

Someone also needs a way to manage properties and listings, change bookings, handle refunds and follow up when something goes wrong. The back-office screens might be straightforward to build, but deciding how that work should happen, and who is responsible for it, is part of the product too.

The demo doesn’t show you how all of that fits together. There are policies, support tools, payout arrangements and trust to work through. That is where a fast-built product can stall. Not because the builder did anything wrong, but because the visible app was always the smaller part.

I don’t want to discourage anyone. Tutorials like that open the door to far more builders. The more useful conversation starts after the demo works. What does this product need before a stranger can trust it?

That is the part of the work I find most interesting. Helping someone see the whole system behind what they’ve built, protecting what is already good, and carrying it over the line.

If you’d like future essays and notes in your inbox, subscribe by email ↗.

Get in touch →