Contributed API and data design through the client-submission-ready stage; 2–4 schools were live during the contribution period, and the product is now used by approximately 10–12 schools.
Education ERP & e-learningProject media coming soon
// The system
A live school and college ERP with e-learning workflows, a Django REST Framework backend, and Flutter applications structured around section-aware data boundaries.
Joining an in-progress product required understanding existing decisions while improving APIs and section-aware data boundaries without disrupting active school users.
01
Ownership
What I was responsible for
Designed and extended Django REST Framework APIs
Contributed section-aware database design
Developed Flutter application features
Integrated improvements into an established product codebase
Supported the product through its client-submission-ready phase
02
Architecture
A layered view of the delivered system
01
ExperienceFlutter · Dart
02
APIDjango REST Framework · JWT
03
Data modelSection-aware school data
04
ServicesSMTP · Firebase
05
CloudAWS
03
Product scope
What the system includes
Admissions, academics, accounts, exams, library, transport, and payroll workflows
Online classes, assignments, submissions, and result publication
Section-aware data separation
JWT-authenticated APIs
Cross-platform Flutter application
Email and Firebase integrations
04
Evidence
Verified outcomes
2–4 schools live during the contribution period
Approximately 10–12 schools using the product today
Product advanced to a client-submission-ready phase
