Vibe coding seems to be everywhere right now, people are building apps just by prompting AI.

But I m curious if anyone here has actually made money from something they vibe coded, especially people who didn t come from a coding background.

I think one of the interesting things about vibe coding is how quickly you can end up with something that works.

As a product designer, I used to spend more time figuring out how something should work before seeing it in action.

Now I can build a working version with AI much earlier in the process.

But there s something I ve started paying more attention to.

I've been building my app for 8 months now, and i ended up having 5 repositories

• nextjs app

• databases

• customer facing API

• node-sdk that wraps the api

• react-sdk, for both reusing shared component and customer facing components

So i thought, it's gonna be great if i create a mono repo with submodules. But it was terrible. I realized that turborepo does not like external packages, and as i tried to reuse my own customer facing libs, the DX became terrible. It was very time consuming to ship a feature. Even when i wanted to use Codex or Cursor 3, it was not able to show git diff properly, also i was not able to use Cursor's cloud agents properly to ship complex features.

Non-technical founder here, built my whole product with Claude Code. Everyone in this forum keeps saying the same thing UI and analytics get the "looks fine, ship it" treatment, but billing and auth get the paranoid line-by-line review. I've lived that.

Here's the twist though: my product IS the billing edge case. It's a tool that recovers failed subscription payments, so the entire thing lives in the messy world of declined cards expired cards, insufficient funds, bank 3-D Secure/SCA challenges that all look similar in the data but need completely different handling. Vibe-coding something where a wrong branch means someone gets emailed "your card was declined" when it actually went through was genuinely terrifying. I couldn't just trust the vibes.

I have used a few products to vibe-code my applications. The first one I used was Chatgpt. From this, I created my first application and it had a very average UI. I was using nextjs for frontend and backend, so for me, the backend part took time but it was decent.
The second product which is good enough for me currently is Gemini. This creates a very good UI and backend at the same time. The first time I used it, it was a super upgrade in the UI. I also used Lovable to create one practice project, but I don't know why I did not used again.

I also heard people's suggestion of using different AI's like claude, cursor etc. but moving in to a different platform has some friction.
What AI is most used or easiest to build an application? I recently heard of a new AI called Emergent, which creates the whole application with a single prompt.

I'm a big fan of voice dictation apps. In fact, I'm using one right now to write this very post (you'll have to wait till the end to see which one I'm using )

The two main products I've used in this space are @Aqua Voice and @Wispr Flow. From talking to others, these are the two that I typically hear people mention using. In general, I hear a lot more people talk about using Wispr Flow.

I've got a function in one of my projects that's been "temporary" for about 4 months now. It works, it's covered by tests, and it's ugly enough that every time an agent touches that file it asks if I want it cleaned up.

Every time I say yes, I regret it a little. Not because the refactor is bad, usually it's genuinely cleaner, but because now I've burned review time on code that wasn't broken, and there's a small chance the agent introduces a subtle behavior change I won't catch until it's in prod.

AI dev tools are moving stupid fast. Every few weeks, there s a new must-use. Some stick. Most don t.

Some vibe coders are developing full products with @ChatGPT by OpenAI+ @Replit. Others swear by @Cursor + @Claude by Anthropic . A few are mixing @Lovable , @v0 by Vercel , and @bolt.new . New and shipping way faster than expected.

I ve been refining my own vibe stack lately.
Building with @Google Antigravity at the core. It keeps the flow clean when things get messy.

Share your current Vibe Stack:

English isn t my first language, and I ve noticed something odd while vibe coding: I get better results when I prompt in English, but I think more clearly when I write in my own language.

A few things I ve run into:

• When I describe a UI or a bug in my native language, the AI sometimes picks up the intent fine, but gets technical terms wrong or mixes languages in the output.

• Prompting in English feels safer for code, but I lose nuance, especially when I m explaining what a feature should feel like rather than what it should do.

• Translating my own thoughts before every prompt adds friction, and I catch myself writing shorter, vaguer prompts just to avoid it.

So I m curious how others handle this:

not talking about the obvious stuff like "don't rm -rf prod", more the gray area tasks where the agent is probably right but you still want eyes on it before it goes out.

for me it's anything that changes a pricing table or a billing calculation. I'll let an agent refactor half my codebase overnight, but the second a PR touches how much someone gets charged, I read every line myself even if the diff is three characters. one off-by-one there and it's not a bug report, it's a support ticket and a refund.