Simran Kumar

A big part of my week is spent talking to early-stage founders about how they handle login, access, and identity, and there is a pattern I keep noticing that I want to understand better.

Almost everyone puts auth off at the start, which honestly makes sense when you are still trying to prove the product matters at all.

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?

When we first built Murror, we stored every journal entry forever. More data meant better emotional pattern detection, smarter insights, richer reflections.

Our AI kept getting better. Our users kept getting quieter.