The @v0 by Vercel team recently dug into industry trends to publish the first State of Vibe Coding report.

My key takeaways:

1. Everyone can build: 63% of vibe coding users are non-developers, generating UIs (44%), full-stack apps (20%), and personal software (11%).

2. Adoption is everywhere, with significant adoption rates in APAC (40.7%), Europe (18.1%), North America (13.9%), and LATAM (13.8%).

3. 92% of US developers use AI coding tools every day

4. 30% of new code at @Google is generated by AI

5. 25% of @Y Combinator startups rely on AI-generated code

6. Rapid expansion has a cost. Vibe coding apps keep hitting vulnerabilities: exposing secrets, access misconfigurations, hardcoded credentials.

7. The future: going mainstream or hitting its sweet spot in working MVPs, the vibe coding trend is here to stay, and it's happening now.

Apple is reportedly pushing back on AI vibe coding apps like @Replit and @Vibecode App, tools that let users create apps just by typing prompts.

The issue isn t a new rule. Apple is enforcing an old one:

• Apps must be self-contained

• They can t download or run new code that changes functionality after review

I m noticing something weird happening in solo dev land.

We used to compete on:

• remembering docs

• knowing frameworks

• being a better coder

Now it feels like the real edge is:

Vibe coding tools have been making huge improvements, but things can always get better.

What blockers are you still running into? What has no one solved yet? What do you wish you could do, but can't yet?

Hey PH family.

Been part of this community for years now, and if there's one place to talk with builders, this is it.

Live Feb 28th, 9am PT - drop your questions!

Hi everyone,
CEO of Bolt here! Super excited to open up about our journey and offer any learnings and stories I can to help other makers on their journey. Within a span of 2 months we've grown to $20M in revenue and were recently featured in NYT as paving the way for vibe coding.

The real founder coding vibe:

• You ship a small fix break 3 things

• You deploy confidently production crashes

• Local works perfectly Vercel says nah

• You spend 1 hour coding 4 hours debugging

• Slack notifications hit instant anxiety

Founders know the pain:
You re coding, marketing, fixing bugs, writing docs, and answering customer emails all at the same time.

What s your funniest or most painful founder-coding moment recently?
Let s vibe in the chaos

I keep seeing the same pattern across early-stage teams:

the MVP works until it really doesn t.

For many founders, the hardest part isn t getting something online
it s everything that comes after:
infra that cracks under real users
code that no dev wants to touch
rewriting the whole stack
AI-built projects no one can maintain
the moment you realize your prototype isn t a product

Hey p/bolt-new community,

I recently started building Couples Hub (https://coupleshub.io/) a React-based application and Next.js based landing page using Bolt.new. Couples Hub is a product of my hobby brand "MD Meets Techie" which I've run for the past four years, creating digital products specifically for couples. Given my technical background, diving into Bolt.new was kind of a fun experiment (esp given how drab and boring my day job is). I noted several challenges along the way and I thought I'll share a few tips on what I've learned thus far. 

I've been pretty impressed at the amount of products people (including myself) have been able to create which got me curious... do vibe coders or AI-primary builders have a place in a company or team?
My thinking is the more technically adept would work on the core-focus while vibecoders can assist with other tasks that shouldn't be the main devs focus...like a potential feature add, minor changes, or even exploring different ways of modifying the existing product.
I'm curious what you all think, would you hire a vibe coder?