Login

u/ryan_almasu

r/vibecoding r/startupaccelerator r/vibecodingcommunity r/saasinvestors r/google_antigravity
▲ 16 r/saasinvestors+2 crossposts

Drop your SaaS — especially if you’re struggling with engagement or traffic

Building a SaaS is one thing. Getting people to notice, visit, and actually engage with it is another.

Drop your SaaS below with:

  1. What it does
  2. Who it’s for
  3. What’s currently holding back your growth

I’ll check out as many as possible and share honest feedback.

I’m building Shipflash, a production-ready SaaS foundation that helps founders skip repetitive setup and focus more on building, launching, and growing the actual product.

https://shipflash.dev

Drop yours 👇

u/ryan_almasu — 7 days ago
▲ 117 r/vibecoding

The first 80% of vibe coding feels fast. The last 20% has been exhausting.

I really enjoy vibe coding. It helped me turn ideas into working software much faster than I could before.

But my biggest pain started after the app already looked finished.

Authentication was working, but then I had to think about authorization and whether every user could access only their own data. Checkout was working, but billing also needed webhooks, retries, duplicate-event protection, subscription states, refunds, and access control.

Then came database migrations, error handling, rate limits, security policies, tests, monitoring, deployment differences, and making sure one AI-generated change didn’t quietly break something elsewhere.

The hardest part has been maintainability. As the codebase grows, the AI sometimes solves the immediate problem without understanding the wider architecture. A small feature can introduce duplicate logic, inconsistent patterns, or files that become difficult to reason about later.

At some point, it stops feeling like “describe the feature and ship it.” You start managing context, boundaries, conventions, and all the boring systems that users never see but depend on.

I still think vibe coding is incredibly useful. I just underestimated how large the gap is between an app that works in a demo and one I would feel comfortable giving to real users.

For people who have taken a vibe-coded app beyond the prototype stage, how do you keep the codebase understandable and prevent each new feature from making it more fragile?

reddit.com
u/ryan_almasu — 27 days ago