Blog

You built an app from a prompt. Here's what it takes to launch it

2 min read
You built an app from a prompt. Here's what it takes to launch it

It has never been easier to make an app. Describe it in a sentence, and an AI app builder hands you screens, buttons and a working demo a few minutes later. People call it vibe coding, and a lot of good ideas now start this way.

We think that is great. We build OwnSites, which drafts a whole website from a short description, so we are fans of starting from a prompt. But a prototype that works on your laptop is not yet an app your customers can rely on. Here is the work that sits between the two.

1. Security

A prototype usually assumes everyone using it is friendly. A real app cannot. Logins, password resets, who can see which records, rate limits, and keeping secret keys out of the code all have to be done properly. These are also the parts an AI builder is most likely to skip, because the demo works fine without them.

2. Real data

Demo data is small and tidy. Real data is large and messy. The app needs a proper database, backups you have actually tested, and screens that still work with ten thousand records instead of ten. If you handle health, payment or personal data, there are rules about where it lives and who can see it.

3. Store rules and devices

If your app is going on phones, Apple and Google each have review rules, privacy forms and technical requirements that change regularly. It also has to work on old phones, small screens and slow connections, not just the one you built it on.

4. Upkeep

Launch day is the start, not the finish. Libraries need updating, operating systems change, and customers ask for things. An app with nobody looking after it starts to break within months.

Keep the prototype. Build on it properly

None of this means your prompt-built prototype was wasted. It is often the best possible brief: it shows exactly what you want, faster than any document. When people bring us one, we use it as the starting point, keep what works, and build the parts that make it safe to launch.

If you have a prototype and are not sure what it needs before real customers use it, tell us about it. We will tell you plainly what is ready and what is not.