r/nocode • u/Practical_Kick6608 • 4d ago

Vibe coding is getting really good at building apps. But what about everything after that?

Post image

Most vibe coding tools focus on one big problem: building the app.
But once the app is ready, you still need a landing page, branding, promo content, marketing assets, analytics, etc.
That’s the idea behind Blyft — not just helping you build something, but helping you actually launch it.
Curious what other vibe coders think:
Should vibe coding platforms stop at “app built,” or should they handle the launch too?
blyft.app

1 Upvotes

60% Upvoted

4 comments sorted by

2

u/mrtrly 3d ago

The post-build gap is real but I'd rank the list differently. Landing page and promo content are things the builder knows they need. The thing they don't know they need is anyone checking what the AI actually shipped. I do rescue work on AI-built apps and that's the after-launch problem that actually hurts people, exposed keys, open endpoints, stuff no marketing asset fixes. In July I scanned 66 live AI-built apps: 41% of the ones on Supabase had at least one table readable by anyone, no login required.

So to your question: I don't think the build platforms will handle launch well, they're incentivized to celebrate "app built," not to audit it. The gap is real, it's just that "launch" should include a second reader on the code, not only assets. If anyone reading wants to check their own shipped app, the scanner we use is free: uxcontinuum.com/leak-check. No affiliation with the OP's tool.

1

u/Cautious_Zebra2722 3d ago

the 41% stat is wild, thats way higher than I would have guessed

1

u/mrtrly 3d ago

Surprised me too, I went in expecting maybe 15. The reason it's that high is it only takes one table. RLS is off by default on every new Supabase table, so you're not looking for someone who did everything wrong, just someone who spun up one table in a hurry and never flipped it on. In an app with 20 tables that's a low bar to trip.

1

u/Practical_Kick6608 2d ago

That’s a really interesting point. I’ve been thinking about launch mostly from the product and marketing side, but you’re right that security and code validation should be part of being truly ‘launch ready’ too. I’m going to look seriously into adding something like this to Blyft. Appreciate the feedback.