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.

Genuine question for makers who've launched here.

I browse PH almost daily. I upvote stuff, sign up on launch day, leave comments. Then 3 days later I want to use a tool and can't remember the name.

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.

My quarter wasn t as successful as I had hoped.

Health issues arose, and most of my plans for work and improving my life together fell through.

Hey everyone,

After a week of getting decent views but almost no downloads, I finally saw a new user pop up in my PostHog dashboard. I was ecstatic.

Then I watched the session log in real-time.

17:29: AppStarted
17:29: AppStarted
17:30: AppStarted

Despite their immense popularity in China, SuperApps (multifunctional platforms that combine services like messaging, payments, shopping, and more into a single app) have yet to gain significant traction in the United States. This discrepancy raises intriguing questions about cultural differences, technological infrastructure, and consumer behavior.

One key factor is the fragmented nature of the United States' financial and tech ecosystem. Unlike China, where Alipay and WeChat Pay dominate the market due to a unified financial system and government support, the US has a diverse array of payment gateways, banks, and fintech solutions. Integrating these into a single SuperApp is not only logistically challenging but also requires navigating complex regulatory landscapes.

Moreover, american consumers have grown accustomed to niche apps tailored for specific tasks: such as Venmo for peer-to-peer payments or Paypal for digital purchases.
The US market has also been slower to adopt all-in-one platforms, reflecting a cultural preference for specialized solutions over overarching ones.

Planning to open source Voiden (https://voiden.md/) soon.

This isn t a maybe someday idea anymore, it s a deliberate step we want to take in the coming weeks.

China's new top paid app doesn't help you find a ride, order food, or socialize with friends. It just asks you whether you're alive.

The app, which translates to "Are You Dead Yet?" the presence of the "yet" suggests the developer probably isn't on the Bryan Johnson "don't die" train...yet) requires you to log in daily and click a button to show you're alive. Miss two days in a row and the app will notify your emergency contact. That's it. That's the app.

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?

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?

There's a popular narrative on social media right now that AI can build software so quickly and cheaply that SaaS is dead (or will be soon).

Why pay for Linear when AI can build a project tracker in an afternoon? Why pay Stripe $30k/year when you can vibe code your own billing system in a weekend? The cost of building software has collapsed to near zero, therefore the value of selling software has collapsed to near zero. QED, SaaS is dead.

The funny thing about building an AI product right now is that the hard part keeps changing.

A couple years ago, I was obsessed with offline evals. They felt clean. You write a test, you run it every time you change something, and you get a number you can trust. If the number goes up, you ship. If it goes down, you fix it. It s the kind of engineering loop that makes you feel like you re in control.

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.

Our team pushes code constantly - multiple deploys per hour some days. The problem? Nobody can keep up with what's changing. You check the repo in the morning, grab coffee, come back and suddenly there are 47 new commits.

Good luck understanding what actually matters or how it affects your work. We built Doculearn to solve this with automated flashcards. Here's how it works:

Every vibe-coding session starts the same:

Here s the context again
Here s what I already tried
Please don t repeat this

That friction killed my flow, so I built Blocpad (CLI).

It keeps context with the project, not trapped in chat history tasks, decisions, notes, all local.
AI reads the state. No re-prompting.

Hey everyone, been a Product Hunt visitor for years but never signed up, so I thought I'd start by sharing some recent learnings that hopefully other builders will find useful.

For context, we're building FanBase Copilot, an AI assistant for content creators that learns their voice and context over time. The memory layer is critical. It's what makes the AI actually useful after the first conversation.

This was a deliberate experiment inspired by my CTO. I wanted to test a simple question:
Can a Product Manager ship a real website end-to-end today without handoffs?

Here s the stack:

• @Figma structure, hierarchy, & visual components

• @Adobe Illustrator brand consistency & visual components

• @ChatGPT by OpenAI positioning, copy angles, objections

• @Lovable iterate layouts before committing

• @Cursor turn ideas into real UI fast

Building my app with AI tools, zero coding background. The magic part - I can ship features in hours. The scary part - I have no idea if the code is actually good.

Right now my "QA process" is:

- Does it work when I tap around?

- Did anything break that worked before?

Reddit has been my main growth channel for the past 6 months and I've been consistently getting 100+ high-intent visitors every week.

Here's the exact system you can copy:

See this?

Step 150 of debugging why a payment does not get saved to a database. Two days on this one bug. And there are plenty more. If you can build somehing that will do the back-and-forth, the "now try this and tell if it... no? Okay, le's do this thn, and this, and that..." Do what Claude Opus 4.5 is tellling me to do, the tens of hours, to get to the solution. Automate that and you have a winer - becuase there are 100K full-stack devs who will do all this more effienctly themselves, yes. but there are 10M non-developers who love what they built, but are getting killed in the debugging, the last 5%.

Digg is back.

The onetime news aggregator relaunched Wednesday as a Reddit competitor, with founder Kevin Rose and Reddit co-founder Alexis Ohanian at the helm.

AI and no-code tools are evolving insanely fast right now. Every few weeks there s a new tool that changes how quickly you can go from idea to product.

I ve been experimenting a lot with different vibe coding platforms lately, trying to find the right balance between speed, control, and flexibility. What s surprised me most is how far you can go today without a traditional engineering setup.

For context, I recently built @Sendrise , an all-in-one cold email outreach platform, using a no-code + AI stack. I used @Lovable for building the product flows and UI, combined with AI tools for writing, automation, and logic. What started as an MVP quickly turned into a fully working product with lead management, campaigns, CRM, and analytics.

I have been cranking out apps for the past few years and loving it.  Then one morning a week or 2 ago I got a little ambitious and decided to build a desktop email client because outlook was so-so and superhuman was ridiculously expensive.  

Is this a big mistake?   Am I wasting my time ?