personal / July 2026 to present
Masar School
A multi-tenant school platform with separate Admin, Instructor, Student, and Parent workflows, plus PWA behavior.
Overview
A school platform has to keep each school isolated while still supporting different workflows for staff, learners, and families.
I shaped the product around school-level data isolation and role-specific experiences for Admin, Instructor, Student, and Parent users.
Architecture and stack
React and Vite sit on a Firebase foundation with Auth, Firestore, Storage, a multi-tenant model, and installable PWA support.
Security and authorization
Firestore rules use schoolId as an authorization boundary. Controlled school provisioning and role-aware access are part of the design.
Testing and verification
Used Firebase emulator rules tests and ongoing security and code-quality review to validate the data boundary.
What I directed
I defined the workflows, directed the implementation, integrated AI-assisted output, and reviewed the security-sensitive paths.
What I learned
Why tenant isolation has to live in the data rules, not only in the interface, and how PWA constraints shape product decisions.
Current limits
Active and still under security and code-quality review. The demo link is evidence of the current direction, not a claim of finished scale.
AI-assisted development
AI helped with implementation, debugging, review, tests, and documentation. I directed the requirements and decisions, then verified the result through builds, tests, repository review, and manual checks.
Selected evidence
Masar School
Real project material, selected for clarity. No generated product screens.
