How do I build an app with AI?
Pick one AI app builder, such as Lovable, Bolt or Replit, connect a database and login early, and add one small feature at a time. Getting a working demo is the easy part. What breaks is what a demo never tests: who can read which data, payments, emails and the move to your own domain.
Escape scanned more than 5,600 public apps built on vibe-coding platforms and found more than 2,000 vulnerabilities, over 400 exposed secrets and 175 cases of exposed personal data. Most of the issues could be reached without logging in.
From my work
At Itmatched, after we fixed and migrated the legacy code, new ideas came in: gift cards, promotions and analytics pages, all outside the MVP. I suggested we ship the core first and build the rest after launch, so the product would not stay stuck in the MVP loop. We agreed on that, and we went to production on time.
That was not an AI project, but AI builders make the same trap easier. A new feature is one prompt away, so it is tempting to keep adding instead of launching.
Pick one builder
They all write real code for you. They differ in how they charge and in what you can take with you. I would look at the second before the first. Prices as seen on each pricing page on 17 Nov 2026:
- Lovable: Pro is $25 a month and Business $50, each with 100 credits. The free plan gives 5 credits a day, up to 30 a month. Custom domains and code download start on Pro. Git sync is on every plan.
- Bolt: Pro is $25 a month for 10 million tokens, and unused tokens roll over. The free plan has 1 million tokens a month with a 300,000 daily cap, Bolt branding and no custom domain.
- Replit: Core is $20 a month, or $18 billed yearly, and Pro is $100. Agent work is billed by effort, so a large change costs more than a small fix.
- Base44: Starter is $16 a month billed yearly. GitHub sync, which exports the full source to your own repo, starts on Builder at $40 a month billed yearly.
Steps that work when you build an app with AI
- Write down the one thing the app must do for a user to pay. Build that first and nothing else.
- Turn on GitHub sync on day one, so the code lives in a repo you own.
- Set up the database and login before you build screens. Screens are cheap to change. Data rules added late are where leaks come from.
- Ask for one change per prompt, then test it. Ask for five things at once and you will not know which one broke the login.
- Keep a second database project for testing, so a bad prompt never touches real users.
- Before you publish, search the code for words like secret, service_role and sk_live. A match in front-end code means the key is public.
What breaks after launch
- Row-level security that is off or too open, so one user can read another user’s data.
- Stripe payments that succeed while the app still shows the free plan, because the webhook fails.
- Password reset emails that link to localhost or the preview URL.
- Login loops and CORS errors after moving to your own domain.
- An AI fix for one bug that breaks a flow nobody tested again.
Signs you should stop prompting
- The same bug comes back after you have fixed it more than once.
- You are spending more credits on fixes than on new features.
- The AI suggests turning off a security rule, or using a secret key, to make an error go away. The error does go away, the way a smoke alarm goes quiet when you take out the battery.
- You can’t tell whether a change touched payments or user data.
When not to build it yourself
If the app moves money between users, or holds data that law or a contract makes you protect, start with an engineer. The builders can still make the first version. Someone has to own the rules around it.
Where my offer fits
I sell this, so read it with that in mind. When the app works in the builder and you are close to launch, my 14-day Trial, $995, is the next step. I read the repo and the backend by hand, send findings ranked by risk in the first 5 business days, then fix what can be fixed in the 14 days. It ends with a written plan for the rest and a walkthrough call. You keep building in your tool. I fix in the same repo.
Read next
Sources
- Lovable docs, Subscription plans, seen 17 Nov 2026
- Bolt pricing, seen 17 Nov 2026
- Replit pricing, seen 17 Nov 2026
- Replit docs, AI billing, seen 17 Nov 2026
- Base44 pricing, seen 17 Nov 2026
- Escape, How we discovered over 2k vulnerabilities in vibe-coded apps, 29 Oct 2025