What was the very first project you vibecoded with AI?

minimalist phone: creating folders

•10mo ago

On Product Hunt, I can see many people launching their products using "vibe-coding tools" like @Lovable , @bolt.new , or@Replit

I reckon many people who created something with them are usually developers who didn't have enough time for building a side idea before, but with AI, they could make it happen.

I am not very technical (know some coding/programming basics), but without the help of a tutorial or ChatGPT, I would hardly build a whole project.

Question not only for developers (but also tech newbies):

What was THE FIRST THING YOU VIBECODED?

Feel free to share the link or the picture
What tool did you use?
What was the most difficult part?
Did you earn any money with that?

Here is mine:
– It was supposed to be a directory of Bluesky tools
– I used v0.dev by @Vercel
– The most difficult parts were to define something + It also rewrote good parts of the code, so it was kind of a mess for me.
– I haven't earned any money because I haven't published the project. (I abandoned it. :D)

2.5K views

Replies

Best

My first vibecoded project was TokenBar. I was paying for Claude Pro, ChatGPT Plus, Cursor, and hitting a bunch of APIs on top of that. Checked my credit card one month and realized I had spent $340 on AI tools without noticing, because each provider has its own dashboard and I never checked any of them regularly.

So I built a macOS menu bar app that shows token usage, credits, and billing across 20+ AI providers in one glanceable spot. Used Swift and Claude to build it. The hardest part was dealing with all the different API formats for usage data. Each provider returns it differently.

It is live now at tokenbar.site if anyone is curious. $5 one-time, everything runs locally on your Mac. No subscriptions, no cloud sync.

Report

4d ago

That’s a great question! For those of us who "vibe-code" daily, it’s less about the syntax and all about the momentum.

Here is my honest take:

My First Vibe-Coded Project

The Project: A custom Chrome Extension that summarizes long technical threads into 3 bullet points using a local LLM.
The Tools: I used Cursor paired with v0.dev for the UI components.
The Hardest Part: Handling the "infinite loop of fixes." Sometimes the AI would fix a CSS bug but accidentally break the background script. I had to learn when to stop "vibing" and actually read the code to point the AI in the right direction.

Did I make money? Not directly from the tool, but it saved me about 2 hours of reading every week, which I traded for more freelance work.

My honest advice: Vibe-coding is a superpower, but you still need to be the "Architect." If you don't understand the logic of what you’re building, you’re just a passenger in a car with no brakes!

What’s the most complex feature you’ve managed to "vibe" into existence so far?

Report

4d ago

i used lovable to build my website. The most difficult part of the changes at that time were not very specific and precise. It seems with new AI models we have much better control over different features/functions.

Report

3d ago