Hey Product Hunters!

When my wife Noa and I heard that MTV was officially shutting down, it felt like the end of an era. As 90s kids, we missed that specific "linear" experience the joy of just turning on the TV and being surprised by a music video without an algorithm getting in the way.

Hi ProductHunt community,

This term has been coined by someone and there are already more than 80 products that you could put in this category. Looking at the numbers, it's growing pretty fast.

Hi, I m an app developer who s shipped many projects the old-school way (hand-coding) for over a decade. Recently AI tools have exploded - speeding up my production like crazy.

What s happening:

- Idea to MVP: Creators focus on ideas while AI writes most of the code.

I've been vibe coding for a few months as a non-coder and I'm still annoyed with the fact that I can't understand what's happening under the hood.

I've got a decent understanding of code but I can't actually write it and I don't know the best practices for stuff like architecture and security which apparently aren't baked into most vibe coding tools. So my question is...

The shift toward "Vibe Coding" feels like we ve finally moved from being construction workers to being conductors. We are spending less time fighting syntax and more time sculpting the "intent" of our software.

However, as I ve been leaning into this AI-native workflow, I ve noticed a recurring tension that I d love to get the community s take on:

1. The "Black Box" Debt: When we "vibe" our way through a feature in 20 minutes that used to take 4 hours, are we unknowingly inheriting technical debt that will haunt us when the "vibe" inevitably breaks?

Hey everyone,

I don't actually like using the term "vibe coding". We've been software developers for over a decade ,are not one-shotting features, and have a very opinionated and strict dev process.

Hey everyone

No CS background. Started vibe coding 3 months ago.

16+ hours daily. 15 billion tokens later I'm still learning.

I was using a Claude Code leaderboard service made by another dev.
Submitting my daily stats became my end-of-day ritual. It was my fuel for vibe coding.

I've never coded. Not a single line. But I m tired of just watching cool ideas fly by. So here I am turning a wild idea into something real with AI

as my co-pilot.

My toolkit? ChatGPT, Cursor, Replit.

I am a product designer, not a coder, and so "lowcode" code editors leave me lost. It simply takes too long to ask Claude to step-by-step me through anything I want to do.
I have projects in the works in Lovable.dev and Medo.dev, Anything and Dazl - but yet to get things to work after migrating them to Vercel breakl out of the co-branding that these app-builders like to sneak in (notice the rainbow you see here and there on Lovable-built sites, even whn they use their own domain...?)
Gemini's suggestions:
AI code generation is prone to the "90% Problem," where the final 10% of polish requires significant manual intervention.  

• Bolt.new: Users report that while blazing fast (app skeleton in 20s), it often "shits the bed" when projects get complex, leading to massive token consumption to fix errors .

• Lovable: Praised for UI aesthetics, but its 7-message memory limit leads to "recency bias," causing the AI to get "drunk" on different approaches during long debugging sessions .

• Tempo Labs: While it provides excellent planning features (PRDs and diagrams), some users have reported that its export to GitHub is unreliable, providing only "fragments of code" rather than a full app .

• Blink.new: Emerging as a smoother alternative for full-stack builds, handling authentication and backend integrations with fewer breaks than Bolt .

Strategic Implementation Path

1. Selection (Phase 1): Use Dyad.sh or Anything if you want the most stable backend/auth foundation .

2. Generation (Phase 2): Build your MVP on the Pro tier for 1 month (~$19-$25). Use Discussion Mode to plan changes without burning credits .

3. Sync & Export (Phase 3): Sync your project to a private GitHub repository immediately .

4. Deployment (Phase 4): Connect the repo to Cloudflare Pages for free, unlimited bandwidth or Coolify on a $5 VPS for total control .

5. Refinement (Phase 5): Use Cursor (locally) for further edits. It provides a full IDE environment with better project context for $20/month, allowing you to maintain your "clean codebase" without builder overhead .
   I then asked, about a cheap solution starting with Baidu's Medo.dev - because Medo gives us many credits to start, 100 more/day free, 20 more for 20 clicks on other's projects... So you can build a lot, download, but then have to sort out login and other backend problems. Possible, but takes some doing.
   Gemini's response:

   1. In Supabase Dashboard: Go to Authentication > URL Configuration. Change the "Site URL" from http://localhost:3000 to your actual production domain (e.g., https://your-app.com).

   2. In Vercel Dashboard: Go to Settings > Environment Variables. Add a new variable called NEXT_PUBLIC_APP_URL and set its value to your domain. This tells the backend where to send users when they click the email link.

   3. In Cursor: If the error persists, open your project in Cursor and ask the AI: "Search for all instances of 'localhost:3000' in the authentication logic and replace them with the environment variable for the site URL.".
      But what about you? What is your process if you are no-code building and shipping?