What was the very first project you vibecoded with AI?

Gramms - personalized bedtime stories for kids - vibecoded it over a weekend! - Gramms.ai

mine was speakeasy — an ios app that converts article urls into audio so u can listen while commuting or doing dishes

stack: expo + react native for mobile, fastapi backend, inworld tts (with openai as fallback), icloud for storage

hardest part was honestly the audio chunking. inworld has a 2000 char limit so i had to split at sentence boundaries and stitch the chunks together cleanly. lots of edge cases

earned money? yeah its live on the app store with a subscription, getting traction now. shipping with ai is just... different. i wouldve taken 6x longer without it

I have no technical knowledge and for the last few weeks I have been working on a mini project in my spare time juggling work and family. I built a tool that allows you to compare salaries across different cities and neighborhoods helping you understand how far your salary will go around the world, factoring in cost of living, taxes, even family status. Take a look here - https://salary-converter.com/

Built mostly with Claude Code and a bit of Grok and Perplexity (mostly for side research and when I run out of tokens). Still working on this but would love feedback. There's also a free embeddable widget people can use to add the widget on their websites here: https://salary-converter.com/widget

This is a great question! For me, 'vibecoding' was the bridge that let me finally build Agentfarm.se 🚜

The Project: I’m building a sovereign AI agent hub. The Tool: I used Claude Code to help me navigate the complexity of local LLMs, but the 'vibe' was definitely more 'industrial' than 'web-app.' The Hardest Part: Getting everything to run on bare metal AMD GPUs with ROCm. 🛠️ It wasn't just about the code; it was about making the hardware and AI play nice together without relying on the big cloud providers. The Money: Not yet, but I'm launching on Product Hunt tomorrow to find out! 🚀

I think vibecoding is a superpower for developers who want to focus on the architecture and the 'why' rather than getting stuck in syntax.

If you're into local AI and sovereignty, check out the farm here: agentfarm.se

The first project I built was TweeReader. I didn't know I was vibecoding at the time
I just wanted to ship something before the hackathon, so I took help from ChatGPT, and ended up becoming the second runner-up

In my experience, vibe coding makes things quicker for me, but if I understand the codebase, it makes the feedback loop shorter.

My first vibe-coded project was actually an early prototype of Tomosu — an iOS app that locks all apps by default for digital wellbeing. Used Cursor + Claude heavily for the SwiftUI parts I wasn't confident in. The hardest part: making "nothing happening" feel intentional rather than broken. AI was great at writing the code, but teaching it the UX philosophy took a lot of back-and-forth 😄 Just launched today on PH!

@busmark_w_nika My first vibe-coded project was a todo webapp — classic entry point 😄

But the one I'm most proud of came later: Claudine, a kanban board for Claude Code. Built it because I kept losing track of which agent conversations needed my attention vs. which were still running.

• Tool used: Claude Code itself (meta, I know)

• Most difficult part: Auto-detecting conversation status from raw JSONL files — inferring "is this waiting for me?" is surprisingly tricky

• Earned money? Not directly — it's free & open source, but it's saved me tons of time managing parallel sessions

If you're deep into Claude Code and want to keep your vibe without losing the thread: claudine.pro

Curious — did anyone else end up building tools for their AI workflow after their first project? Feels like a whole category emerging 👀

#thanks-for-upvotes!

This resonates so much! I’m in a similar boat, I spent my career in HR and Operations advising executives, not in a code editor. I’ve always known how organizations should run, but I lacked the "hands" to build the infrastructure to fix it.

As someone managing ADHD, I was drowning in 'app fatigue', constantly switching between five different tools for journaling, habit tracking, and task management. Nothing talked to each other. I built the first iteration (originally called DoersSecretAI) using CO.dev over a few intense nights. It was raw, and I must have reverted the build 15+ times trying to get the logic right, but I ended up with a 'planner-meets-wellness' hybrid that I actually used every single day for nine months.

I never intended to sell that early prototype. It was my personal lab. But after using it consistently until mid-December, I realized that the 'operating system' I built for my own focus was exactly what was missing in the executive world. That personal 'itch' is what evolved into the professional-grade suite I’m beta testing now.

The first thing I vibecoded was a Chrome extension for Copus, our content curation platform. I had the core web app built traditionally, but needed a browser extension that lets people save articles, videos, and links from anywhere on the web with one click.

Tool: Claude Code (Anthropic's CLI). Honestly it was a game-changer for extension development specifically because you can just describe the Chrome APIs you want to use and it handles all the manifest.json, content scripts, background workers complexity.

Hardest part: Getting the extension to work nicely across different websites. Every site has different DOM structures, so the "save this page" feature needed to handle edge cases everywhere. AI was great for iterating fast on those edge cases.

Did it earn money? Not directly from the extension itself, but it is the main acquisition channel for Copus — people discover articles through the extension and join the platform. So yes, indirectly.

map with mapbox - it was soooo beautiful