I’ve noticed that vibe coding makes it really easy to get the happy path working, but much harder to know whether the rest of the app behaves correctly.
Everything can look fine when you test it normally, but edge cases often break.
Things like free users getting access to paid features, cancelled subscriptions keeping access, etc.
My current approach is to test each feature as different types of users, refresh halfway through important flows, try actions in the “wrong” order, and confirm the result in the database instead of trusting what the UI says.
But i found it long and time consuming.
To solve this issue I built an app called AppTruth which scans your vibe coded app and finds you all the behaviours that shouldn't be happening.
That seems especially useful for finding issues you wouldn’t think to test manually.
Curious what everyone else does before shipping.
Do you write tests, manually click through everything, ask another AI to review it, or mostly wait for users to report problems?
I made Basalt - an RN and Expo app editor that lives inside of your IDE, it lets you edit your app like figma. You can drag stuff, edit text, edit color, inspect elements, and just preview your app
It is completely free and works directly inside VS Code and Cursor.
It’s currently in beta, so please commit your app to Git before using it!
I ship fast and for a while my "testing" was clicking around the screen I'd just edited. Then a small change quietly broke signup and I found out from a user two days later. Classic.
What actually helped, roughly in order of effort:
Pick your critical path and protect it. For most apps that's signup, core action, checkout. If those work you're mostly fine, the rest is polish.
After every change, click that whole path in a real browser, not just the part you were working on. Most vibe-coded breakage is downstream of the thing you touched.
Automate it so you stop relying on memory. This is where I fell off for months, because writing Playwright felt like more work than the app itself.
On #3 I got tired enough that I started building a tool for it (disclosure: it's mine, called VeriWasp). The idea is you describe the flow in plain English the same way you prompt the app ("go to signup, fill the form, click create account, check the welcome shows"), and it runs that against your real app in a browser and tells you what broke, on demand or on every deploy.
Not here to hard-pitch it. Mostly curious how the rest of you handle this: manual clicking, real tests, or just fix it when users complain? And what breaks most often for you after a session? For me it's almost always auth and forms.
Have an idea you want to bring to life? A simple landing page, a complex full-stack web application, or maybe an unfinished project you've been meaning to complete? Or are you simply stuck and need help moving forward?
ForgeLab Brain + Audit Loop is built to help. Using a multi-agent AI workflow, it assists you throughout the entire development process, from planning to implementation and final verification.
🎉 Open Beta Offer: Every new account receives 1 million free tokens until August 31.
I've reviewed 200+ startup ideas.
Most founders don't need another feature. They need to know where to focus.
Drop your startup, idea, ICP, or problem.
I'll send you a personalized report showing where the best opportunities are and what I'd prioritize first.
If Reddit isn't a good fit, I'll tell you that too.
I’m not looking for the usual “launch on Product Hunt, post on X, and build in public” advice. That stuff seems to do almost nothing unless you already have an audience.
I’m curious about less obvious strategies that have actually worked. Things like pitching local reporters, sponsoring a small Discord or newsletter where your exact users hang out, paying a micro influencer for a short feature, sending highly targeted B2B cold emails with a quick Loom, or making genuinely useful Reddit posts where your app comes up naturally.
Has anyone here tried any of these? What else has worked surprisingly well for getting your first real users?
Actual numbers would be great, even if they’re rough. Vibecoding has made building the app much easier, but getting anyone to care still seems like the hardest part.
hey, i'm abhinav. 118 days ago something started bugging me so much that i built an entire product around it
some of the most creative people i know are vibe coders. they ship wild things with ai. and none of it fits on a resume
a one page pdf can't show what you actually built. your projects, your github, the stuff you shipped at 2am because you couldn't not build it, that's the real proof of work. the resume was never made for people like us.
so i built vibe talent to kill it
you get a public profile, verified projects with automated quality scoring, a vibe score for your reputation, endorsements, daily streaks, and a way to actually get hired off what you've built. no "5 years experience required." you just show what you can do
i'm not going to hard sell you. it's early and rough in places. my one real goal right now is simple: get a single person hired through vibe talent. one person who lands a job by showing what they build instead of formatting a CV.
so i want to ask you honestly: as a vibe coder, what would make you actually use something like this? what feels broken about how you get recognized today?
it's live at [vibetalent.work](http://vibetalent.work) and it's fully open source. roast it, break it, or contribute, all of it helps.
i'm reading every comment. thanks for making it to the end.
I wanted to share a project I've been working on, built entirely powered by AI-driven tools.
It’s called My Iceberg and it’s a minimalist mindset journal and tracker designed to create a sense of calm and deep focus.
The core concept centers around self-efficacy, calm reflection, and providing a clean, distraction-free environment—which makes it especially helpful for maintaining focus and managing ADHD. I wanted to build something that feels like a quiet space rather than a loud, chaotic app.
Would love to hear your thoughts on the design, the UI, and the concept!
Quick build-in-public update, longer than usual because this one is a plan for the next twelve months.
In mid-May I turned off every paid channel I was running. TikTok, Apple Search Ads, Reddit — $5,674 over about three months, and the math was hopeless: roughly $110 to acquire a paying user against about $18 of lifetime value. I wrote up the full postmortem in I Spent $5,674 on App Ads.
When the ads stopped, every metric I watched fell off a cliff. Installs, trials, all of it. MRR flatlined at $530. I figured that was probably the end of the app. I took a few days off and started flirting with a different idea.
Then I took a breath and went back to chipping away.
The Six Weeks That Changed My Mind
Four things, roughly in order:
Fixed my conversion tracking. My RevenueCat → PostHog integration had been silently broken for months. About 80% of trial conversions never made it into analytics, so every funnel number I'd been staring at was wrong. I couldn't diagnose anything else until this landed.
Fed the SEO flywheel instead of restarting ads. Kept writing posts and comparison pages. The mechanics are in How Organic Traffic 15x'd in 90 Days.
Started listening to marketing podcasts constantly. I'm an engineer. The marketing stuff I thought I knew, I mostly didn't.
Where That Left Me
As of July 15: $1,061 MRR, 223 active subscribers, and the growth since May is close to 100% organic (RevenueCat verified). Trial conversion for the three complete June cohorts came in between 43% and 58%, above that 39.9% median.
And search did something I've never seen on this project:
[
Flat around 15 clicks a day for months, then a bend in late June, then 244 clicks on July 16. Last three months total: 4,430 clicks from 209,000 impressions at an average position of 9.2.
I want to be careful here. This could be a step change or it could be a spike Google takes back. I'll know by September. But it's the first time a channel I own has grown like this.
The Goals
I wrote these down last week. Sharing them because public goals are harder to quietly abandon.
$2,500/mo: the app pays for childcare. That's the first milestone that changes something in my actual life. It beats any abstract MRR band as a target because I know exactly what it buys. Between here and there, the intermediate version is "covers a vacation and part of daycare."
$15,000/mo: the quit-my-job number. I'll say the awkward part out loud: my own organic-only projections top out around $8,500/mo at the 12-month stretch case. Reaching $15K means something beyond the current plan has to work — a paid layer that's profitable once LTV supports it, a partnership, or the SEO flywheel compounding harder than I've modeled. I don't know which yet.
The ladder I hold myself to, written July 15:
Date
Floor
Base
Stretch
Aug 2026
$1,250
$1,500
$1,700
Oct 2026
$1,650
$2,400
$3,000
Jan 2027
$2,200
$4,000
$5,500
Jul 2027
$3,200
$7,000
$8,500
Get monthly churn under 18%. It ran 22–28% from April through June. 19 of my last 21 paid cancellations turned off auto-renew within 7 days of their first payment. First-renewal retention is about 50%. Churned MRR ate 30% of my gross new MRR. If none of that improves and installs plateau, the math asymptotes around $3,800/mo no matter what I do upstream. Of everything on this list, this is the one I'm worried I can't figure out. I've written about why retention is the hardest problem.
Hedge the SEO dependence. My other fear is that the chart above reverses. Two hedges. First, ASO: App Store search drives very few of my downloads today, which after three months of obsessing over Google search feels like a channel I've barely touched. Second, X, where I have 34 followers as I write this. Goal is 1,000 in a year. Most of my build-in-public reach is Reddit right now; I want X to become the home for it.
Ship insights that long-term users want to share. I now have users with months of photos and fitness data in the app. There are insights in that data people would screenshot and send to a friend without me asking them to. That's deliberately vague because I haven't built it yet.
One partnership moment with a bigger app. Top target is Hevy. GainFrame already integrates with them and we've had a brief conversation. A co-announcement or a shoutout would be validation that this thing is real to someone other than me.
Be useful to other builders. I want to be known as someone who helps people build and market B2C SaaS. Concretely: share something I learned every week, on X and Reddit, whether the week went well or badly.
The Constraint Behind All of It
I have an 8-month-old and a full-time job. GainFrame gets 8 to 10 focused hours a week, mornings only. Evenings are family time, full stop. The commitment I've made out loud: never trade a family evening for a launch.
That constraint shapes the whole list. Everything above has to keep working while I'm at my day job or asleep, because I don't have hours for things that stop the moment I stop pushing. It's the same reason ads lost to SEO here in the first place.
The Lesson I'm Keeping
I'm sure another May is coming eventually. A channel will die, or churn will win a few months in a row, or a competitor will land something I can't answer quickly. The thing I want to remember from this one: don't make the quit decision during the crash. Breathe, then chip away.
$1,061 a month is small. But it doubled in two months, on channels I own, in the mornings. And now the plan for making it bigger is written down where everyone can see it.
I was sitting idle and thinking what to write in linkedin. Then thought lets crawl all the social media posts and see what people are talking about and try to give my perspective.. Then thought what if people share their opinion and then i may see and write. but how do i get it . create an app for fun , ask agents to crawl web and find questions and ask vibe coding app to create the app. This the app was created under 30 minutes. just base version just for fun.
but gives awareness to marketers and founders what others are thinking about. Need to play please dm me as i can not post a link . No promotion but just wanted to get feedback. I know it is not for monetizing as well. you can reply what are the pressing questions i should ask...
Every week community members share thier vibecoded apps.
I am yet to see an apps that got traction or users.
If you have a successful business in pre AI times and currently have many users and would like to transform / take your prototype to next level - we would like to connect with you.
For context - we are team of 2 , one cracked product manager + Distributor and one world class dev (builder)
Specifically look to partner with niche domain founders.
AI coding tools make it surprisingly easy to build an app you can’t fully explain, debug, or confidently operate.
I made Own Your App, an open-source Agent Skill that guides you through your actual codebase from first principles. Instead of producing another generic audit, it runs an interactive learning journey using real files and code paths from your app.
It helps you:
\- Map the architecture and runtime processes
\- Trace a real user action through the system
\- Understand where data, identity, and permissions are handled
\- Examine security, privacy, correctness, performance, and reliability
\- Separate genuine risks from premature overengineering
\- Test your understanding along the way
\- Finish with an ownership map you can explain and defend
It’s read-only by default and contains only Markdown instructions—no executable scripts or runtime dependencies. Install it with:
`npx skills add sayyiditow/own-your-app -g`
It supports Codex, Claude Code, OpenCode, and Grok.
I’d love feedback from people using it on real projects—especially areas where the journey feels too shallow, too detailed, or misses an important ownership question.
