Vibe-coded MVP worked great, then real users broke the admin dashboard
by•
Spent the last few weeks building three connected apps and shared microservices with Lovable/Cursor. The first 80% went shockingly smooth, the demo-stage stuff always does. Then real usage started, and the integration between services and the admin dashboard started throwing constant sync errors. A few different AI coding tools could patch individual symptoms but never quite nail the root cause.
For anyone who's taken an AI-built app past the demo stage: what was the first thing that actually broke once real users or data hit it, auth, data consistency, service integration, something else? And did you end up digging into the code yourself, or bring in outside help to sort it out?
14 views
Replies
I've been there, and it completely changed how I validate new features. I can click through every screen perfectly because I know the product inside out, but real users don't think like I do.
@new_user___090202674ab6e030a7a9c52 For me, moments like this are frustrating but incredibly valuable. I've learned that dashboards often make perfect sense to the person who built them, yet feel overwhelming to everyone else.
@new_user___090202674ab6e030a7a9c52 @mathew_chang I've learned the hard way that real users always find paths I never imagined. For me, that's when the real product starts
@new_user___090202674ab6e030a7a9c52 Had the same experience. I thought my admin flow was straightforward, but real users exposed assumptions I didn't even realize I'd made. What issue surprised you most?