Why We Split One App Into Two — The Architecture Behind Studoo & Padhloo

When we started building Studoo, the goal was simple: help students book seats in nearby study libraries.

We began with one app, one codebase, and an "we'll fix it later" mindset. But reality hit fast.

A deeply nested MongoDB model looked perfect on paper, but collapsed during real seat bookings. One product trying to serve both students and library owners created endless UI and focus confusion.

We made the hard decision to split into two clear experiences:

Padhloo → for students

Studoo → for library owners

Turborepo helped us build two apps with one shared core, keeping schemas and logic in sync.

This journey reminded us of something fundamental: Architecture isn't about complexity — it's about reducing future pain.