The idea was to bring property search, user accounts, bookings, and relocation services into one place. And we wanted to do it without building everything from scratch.
Full Story below 👇
Shipping your MVP fast is the right call. But there's a difference between cutting scope and cutting corners.
What I'd happily cut from a first version:
✂️ Roles and permissions beyond admin and user
✂️ Native mobile apps (a responsive web app gets you to real users first)
✂️ Analytics dashboards
✂️ Integrations no user has asked for yet
✂️ Settings for everything
All of that is easy to add later, once real users tell you what they actually need.
What I never skip, even in the smallest build:
✅ A clean database schema. It's the hardest thing to change once real data is in it.
✅ Background jobs. Emails, API calls and reports run outside the request, so a slow service never freezes your app.
✅ Error logging and alerts, so you hear about a bug before your users do.
✅ Login and payments done properly. Users trust you with these before anything else.
Cut features, and you ship faster. Cut foundations, and you pay twice: once to build it, and again to rebuild it when real users show up.
Planning an MVP? I offer a free build audit: calendly.com/roshaanali-business
Developed and maintained Maestro, a school management application for Active Brains Academy, designed to support the school's day-to-day digital operations.
I worked across the application, building and maintaining its functionality, backend integrations, and database systems. The project spans web, desktop, and Android platforms, using a shared backend to support the different clients.
I also worked on restructuring parts of the codebase with TypeScript to improve maintainability and make further development easier.
This project has given me hands-on experience working with a real-world application, handling an evolving codebase, supporting multiple platforms, and building software around the needs of an operating institution.