Tag: Web development
-

Vibe-Coded App Backups: You Don’t Have One Until You’ve Restored It
“Do you have backups?” has a trick in it. The real question is when you last restored one. What a backup has to mean for an AI-built app — automatic, point-in-time, off-site, files and config included — the quarterly restore drill, and what to do right now if the AI already dropped the table.
-

How to Add Tests to a Vibe-Coded App That Has None: The Five Flows That Matter First
Every rescue guide says “get a test suite.” This is the how, for a founder who’s never written one: pick the five flows that would end your week if they broke, write them as Playwright end-to-end tests, wire them to run on every change — a day’s work that catches most “the AI broke something…
-

Authentication in Vibe-Coded Apps: 8 Holes Around the Login That Works
Login is the part of an AI-built app that always works. The holes are around it — unverified accounts, reusable reset links, sessions that survive a password change, no rate limits, client-editable roles, duplicate accounts, deletion that doesn’t delete. Eight two-minute checks and the fix for each.
-

Firebase Security Rules for Vibe-Coded Apps: Why “Signed In” Is Not “Authorised”
AI-built app on Firebase? The rules probably say allow if true, or if request.auth != null — which means any signed-up user can read everyone’s data. The 60-second check, the owner-only rule set every app needs, and the deny-all catch-all the AI forgets.
-

Case Study: Rebuilding GO Car Rental Georgia for Search, AI Assistants and Direct Bookings
How we took a Tbilisi car rental site off its page builder, rebuilt 78 URLs as clean HTML, added a scripted booking assistant and first-touch attribution, and set up a weekly SEO loop driven by Search Console and GA4 data.
-

Supabase RLS for Vibe-Coded Apps: The Policies Your AI Forgot to Write
If your AI-built app uses Supabase, every user can probably read every other user’s data — because Row Level Security is off or the policy says true. The 60-second check, the four policies every table needs, and the prompt that gets the AI to write them properly.
-

I Leaked an API Key in My Vibe-Coded App: What to Rotate, In What Order, and How to Stop It Happening Again
A secret key in your deployed bundle or git history is the most time-sensitive problem an AI-built app can have. Rotate first, investigate second, fix the code third — the exact order, which keys matter most, and the tripwires that prevent a repeat.
-

My Vibe-Coded App Got Slow at 50 Users: The 5 Fixes (Before You Upgrade Anything)
Instant with three test users, unusable at fifty real ones. AI-built apps slow down at a predictable point for predictable reasons — N+1 queries, filtering in the browser, missing indexes, request waterfalls, refetch-on-keystroke — and almost none of them need a bigger server.
-

Vibe-Coded App Not Showing Up on Google? The Technical SEO Fixes for AI-Built Sites (2026)
You built the site with AI, launched it, and Google can’t see it. The eight technical SEO problems almost every vibe-coded site ships with — client-only rendering, missing metadata, no sitemap, blocked crawlers, slow Core Web Vitals — and the fix for each, in the order that gets you indexed fastest.
-

From Lovable, Bolt or Replit to Production: How to Move a Vibe-Coded App Off the Prototype Platform
Your Lovable, Bolt.new, v0 or Replit app has real users and you’ve hit the platform’s ceiling. When to migrate, what to take with you, the six steps to a proper repo and deploy pipeline — and the parts that are worth having an engineer do.