Hey folks

I ve been building a product that involves a mix of AI-driven matching + dynamic user experiences (can t share exact details yet). The idea is to create something that feels alive and adapts to each user s vibe.

But here s my dilemma I m torn between focusing first on core UX feel (smooth, immersive flow) or AI logic depth (smarter matching + personalization).

For those who ve shipped vibe-heavy or AI-integrated products what worked better for you early on?

I don t get it, honestly.

I ve made a bunch of actually useful web apps recently using lovable.dev and v0.dev, and here s the thing:
I don t know how to code. At all.
No CS background. No tech degree. Just a regular person scrolling through tools and products like everyone else.

But around 3 months ago, I gave v0.dev a try... and I was genuinely shocked.
Not just by how well it worked, but by how fast it s improving.
It s kind of scary in the best way.

Sure, it can t build a full app from start to finish yet...
But take a second to think about it
This kind of thing didn t even exist 2 years ago.
At the pace it s moving?
Give it 1 year and solo builders will be able to do some absurd stuff.

For the past couple weeks I've been on my #indiehacking coding grind

All the tools out there to go from just vibecoding to actually launching can be quite overwhelming when just starting out

I'm a freelance consultant. Tried Folk, Attio, HubSpot free, Google Sheets. Never stuck with any of them. The problem wasn't the features, it was that I never went back to the tool.

So I built a CRM inside my AI assistant (Claude + MCP server + Supabase). Six contact lists, email drafting, a Chrome extension that scrapes LinkedIn profiles at $0.001 each. Total cost: $10.

The whole thing lives where I already work. That's why I actually use it.

I'm a UX designer and Product strategist. Not a fullstack developer.
And I just shipped a full SaaS product.
Here's how I did it.
I work as a UX and Product SaaS strategist and also run a remote digital agency Koylabs.
I always had product ideas but never the engineering background to build them myself. That changed this year when I started seriously experimenting with AI tools and vibe coding.
I picked a real problem I kept seeing with clients they wanted Google reviews on their website and every existing solution was clunky, complex and a bit dated. Simple problem. Clear market. So I decided to build the solution myself.
The stack:
Next.js + Supabase for the backend
Stripe for payments and subscriptions
Cursor as my AI coding environment
Vercel for hosting
What surprised me:
AI is incredible at boilerplate and repetitive logic
The hard parts were still hard embed systems, iframe height communication, Stripe webhook edge cases
Product thinking was my biggest advantage.
Knowing exactly what to build and what to leave out saved weeks
Vibe coding is real but you still need to understand what you're building
What I actually shipped:
Full auth and multi-tenant architecture
Stripe subscriptions with trials, webhooks and billing portal
A custom iframe embed system that works on Framer, Webflow, WordPress and any platform
Automated review sync
Four widget layouts
Start to launch: a few weeks.
The result is Review OS a simple clean way to show your Google reviews on your website. One embed code, done in under a minute. Only $9/month.
If you or someone you know needs this try it free for 7 days at www.reviewos.co 7 day free trial
And if you're thinking about building your own project follow along.
Give this tool a try and share your thoughts I'm looking forward to your feedback.
My next post will be a full playbook on how I did it, tools, process, mistakes and all.
What are you currently working on? Drop a comment would love to know.
Launching on Product Hunt this Wednesday would love your support

Do any of the more experienced coders ever feel like closing the loop in vibecoding is a bit too much control to let go off? I'm not sure if I can categorize myself as an experienced coder. I'm been mainly self-taught and been doing it for almost a decade now, so I have strong opinions about what I consider best practices. (I actually love refactoring, because it feels like order is once again restored in the codebase).

However, with AI becoming so good at so many parts of the product development, I'm starting to feel like a project manager, or god forbid, scrum master... On the one hand, it's nice that I get to spend most of my time thinking about the problems themselves rather than the implementation of the solution. But on the other hand, I think my coding style is a bit like trying to find a way out of a dark room by running into the wall repeatedly as opposed to planning a way out. And I kind of missing running into the wall to be honest. Now, I'm enviously looking at AI hitting the wall.

Over the last year, I ve been experimenting more with local-first patterns , apps that prioritize offline functionality and sync later instead of depending on constant server calls.

What used to feel experimental now feels surprisingly stable. Faster UI, fewer loading states, and a smoother user experience overall.

I rebuilt a small side project recently with a local-first approach, and the difference in responsiveness was noticeable. But it also introduced new challenges around conflict resolution and state consistency.

It makes me wonder:

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 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 ?