Hey folks, quick pulse check. What’s the biggest bottleneck slowing down your current VIBE coding workflow? Is it tooling, context-switching, messy repos, slow reviews — or something even wilder? I’m looking for real blockers, not the polite ones we tell our managers. Drop the pain points, the annoyances, the “why is this still a thing?” moments. If it kills your vibe, breaks your flow, or drains your sanity — I want to hear it. Let’s surface the friction so we can fix it fast.

Hey guys, I’m starting a vibe coding co-op for creators people who want to learn and customers who want access to the products that are created. Take a look at what I’m building and let me know if you wanna be a part of it to join the waitlist. https://joinvibehub.com/join/creator If I get enough people to sign up as creators I will launch it. For now, I’m testing if there’s enough interest or not. Thanks in advance!

Hey everyone, I’m reaching out to gather some insights and feedback. I’ve worked with a few recruiting and staffing companies in the past, and one thing that always stood out was the huge amount of time spent reviewing job applications. So, I started thinking why not automate this with AI? I’m curious: Do you think an AI-driven service that helps screen and filter applicants would be valuable for recruiters and staffing professionals? Is this a pain point something you think people in the space feel strongly enough to invest in? Just looking for that starving crowd rn. Looking forward to hearing your thoughts!

Hey everyone 👋 I’m pretty new to vibe coding but been messing around with a few tools lately. I’ve already launched two small personal apps one with Lovable and one with Emergent and I’ve been playing around with Cursor too. Where I’m still trying to level up is the backend side (Supabase, GitHub, all that stuff) and figuring out the easiest setup for managing multiple projects without it getting messy or expensive. I’ve got a bunch of random domains I’ve collected over the years, and now I’m finally ready to start building out those ideas fast more in that “just vibe and build with words” kind of flow. I also tested 10Webb since it’s got the WordPress admin built in and can clone sites, but I found it clunky — not as smooth or conversational as I’d hoped. Curious what everyone’s using right now — what combo of tools or platforms feels like the best, most efficient vibe stack for building multiple sites quickly and keeping it fun?

From 0 to Revenue: How I Built a Monetizable AI App This Week—No Code Link: https://www.onspace.ai/?via=vibecoders Hey everyone, I’m Alex. This week I went from zero to a fully shippable, monetizable app—Invoice AI—without writing a single line of code. I used natural language + OnSpace’s agentic builder to recreate a production-grade app end to end. Here’s exactly how I did it, what worked, and what I’d improve next. What I built - Invoice AI App: A clean, focused invoicing experience with AI assistance. - Fully no-code: All instructions were written in plain English. - 1:1 replication: Layouts, flows, and micro-interactions closely matched the reference. - AI features: Smart field suggestions, auto-fill, and context-aware templates. - IAP ready: In-app purchases integrated for subscriptions and upsells. - Cross-platform: iOS, Android, and Web via our React Native + Expo stack (handled by OnSpace under the hood). My best-practice workflow (fast and repeatable) 1) Capture the source app clearly - I mirrored my iPhone to Mac using QuickTime Player. - I recorded and screenshotted every key screen and transition. - Why: this gives the model exact visual context and helps me map app logic cleanly. 2) Define the core structure up front Most “template-style” apps share a familiar skeleton: - Onboarding Page - Subscription Page (paywall) - Main Function Page My build order for speed: 1) Main Function, 2) Onboarding, 3) Subscription. 3) Write a plain-English first prompt - I described every main user path in simple language. - I attached the first screenshot for each path. - Goal: get the model’s first version structurally correct. Then iterate. - Next passes: for each branch/sub-flow, I added detailed screenshots and notes to refine UI logic and edge cases. 4) Rebuilding motion and onboarding polish - Tip: break complex animations into discrete frames. - I provided separate images and short descriptions for each state/transition.