Vibecoding
Build for the vibe, debug later
Start new thread

What was the very first project you vibecoded with AI?

by
•

On Product Hunt, I can see many people launching their products using "vibe-coding tools" like , , or

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 by

– 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)

4.3K views

Add a comment

Replies

Best

The first thing that i ever vibecoded was creating a telegram bot that sends me daily updates and news about AI. I remember how happy i was when I first did it and it worked! For context, Im not a technical person at all and having vibecoding tools is such a game changer for me! I haven't earned any money since the goal was to try vibecoding tools and create something of my own by myself. For this task I used

Vibe coded QuickAnswer in Google Ai Studio, in result try connect firebase, and start learning backend, in the end understood QuickAnswer idea market not profitable and discovered cursor.

Somebody there started vibe coding with Google Ai Studio?

Vibe coding is genuinely powerful, especially if you're technical and want to ship faster. But it gets dangerous the moment you stop supervising it.

Learned this the hard way. When vibe coding first came out I jumped in, over trusted it, and ended up breaking work that was already done. It doesn't just slow you down, it can set you back.

Vibe coding is great. The blind trust is the problem.

I built an LLM-powered surveying app, for a couple reasons:

  • They're expensive for reasons I've never understood

  • A static survey tool isn't the best way to get contextual answers to a research question

It turned out to be the perfect first vibe code app for the same reason video gen is so good at creating cat videos. There are petabytes of examples online.

mine was SAAL, . you write a letter to your future self and it gets mailed back to you in 1, 2, or 3 years as an actual physical handwritten letter.

i am not a developer at all. like have minimal coding knowledge outside of SQL. i used to get the first version running, then Claude Code to build out the real thing with a proper backend, payments, Stripe, email delivery, API integrations for the physical letters, the whole thing.

the most difficult part was honestly not the code. it was learning enough to know when the AI was doing something wrong. you can vibe code yourself into a corner real fast if you're just accepting every suggestion without understanding what it's doing.

did i earn money? stripe is live and not in sandbox but not yet... 🙂 still pre-launch but people have found it.

the wildest part is i now genuinely understand how the codebase works. i couldn't have told you what a webhook was 3 months ago.

The first project was a projection-mapping of giant eyes for an art installation.


Eventually, I vibe-coded a presentation on vibe-coding and told it to go off the rails.

First thing I vibe-coded was ClipScript - a tool that takes YouTube transcripts and actually does something useful with them. Repurpose a video into a blog post, Twitter thread, email, whatever. Started as a quick experiment and ended up being the most useful thing I've built. Check it out if you're sitting on a pile of transcripts going nowhere:

The problem is that current tools weren't made for non technical users....Why? Because the people that built them are VERY technical. Software experts...Why would you expect technical developers to know the hardships of non technical people?

They always talk about how "Easy" their products are, or how "simple..." But in reality what may seem like baby food to them is actually Overcooked steak for average non engineers. It is possible for vibe coding to be for non-technical. It just needs to be something that doesn't have the fancy jargon, but instead words that 5 year olds can understand with technical resolution workflows that even grandma's and grandpa's can use.

I'm non-technical, but built this out for my wife and I to build SaaS products quickly...maybe might launch it one day haha.

P.s. It didn't take 19m tokens for this one app...I've made maybe 12 total apps and that's the toa from all of my projects.

I work with spatial data, GeoJSON, Shapefiles, SQL, and other formats which led me to building a browser tool that converts between them. Including SQL INSERT statements, WKT, and database-ready geometry formats.

Started as a little utility for myself, ended up becoming my first shipped project.

Actually have had over 1k conversions but no buyers, just going to make it free for anyone to use once I get a minute to update the site.

We have found the most effective way to vibe code is to pair our 12 years experience in technology being surrounded by developers, database analysts, infrastructure experts, QA technicians and to to channel those into the best vibe code prompts to create and deliver a working, safe, efficient product.

We let Claude do the coding because we knew we couldn't, but we made it code the way we needed it to, not let it run free and have no idea how the platform was built. Now we know every part of it from setting up AWS, Render, Supabase, launching Android and iOS apps.

Sure, we couldn't write code, but we've delivered it and I think that's the best way to vibe code!

First
Previous
•••
131415
•••
Next