Parents tracking their children and teachers running classrooms share almost nothing. One Flutter codebase serves both, changing its entire shape depending on who signs in.
Start your projectThe build
TMS is a school operations app for a private schoolhouse, built by Aipxperts as one Flutter codebase for iOS and Android.
It serves two audiences that share almost nothing: parents tracking their children, and teachers running classrooms and their own timekeeping. The app changes its entire navigation, dashboard and feature set based on who signs in.
The problem
A small private school generates a surprising amount of process. Daily drop-off and pick-up has to be verified. Lesson plans have to be shared. Parents need to reach teachers and teachers need to reach all parents. Payments have to be collected. Staff need to log hours, claim reimbursements and request time off. Before the app, all of that lived in paper forms, email chains and phone calls, which creates three problems:
A paper drop-off sheet cannot tell you who collected a child at 3:40pm on a Tuesday in March.
A note in a bag is not a conversation.
Staff administration competes with teaching for the same hours.
Underneath that sat a real engineering constraint. Parents and teachers need genuinely different applications, and building two would have doubled the maintenance for a single small school.
What we built
We built role as a first-class concept rather than a permission check bolted onto a shared interface.
Parent and teacher modes with multi-child switching for families with more than one child enrolled.
Break tracking and history logs, used both for staff timekeeping and for verified parent drop-off and pick-up.
Student attendance and classroom lists, entered where they happen.
Upload, subjects and topic detail, plus classes, supply lists and teacher bios.
One-to-one and group messaging with voice messages, attachments and media over Socket.IO.
Slot booking for parent and teacher meetings.
Events with add-to-calendar, announcements, bulletin board, blogs, newsletters, lunch menus and parent surveys.
A shop with cart and Stripe checkout, plus subscription plans through App Store and Google Play billing.
Reimbursement claims, time-off and sick-pay requests, and order management.
Multi-factor authentication, one-time passcode sign-up and verification, and password reset.
The outcome
The structural result is that the school's daily record is now a record. Every collection, message, payment and claim has a timestamp and a person attached to it.
Flutter
Dart
GraphQL
Stripe
Firebase
ZoomIf two very different groups of people need the same system, that is usually one product with two faces rather than two products.
Start the conversationInstall size was working against growth in the markets this children's platform was expanding into. The build came down from 162MB to…
Read the buildInstructional coaching only works if the loop closes while the lesson is still fresh. Seven years of building later, school leaders across…
Read the buildTell us what you're building. We'll reply within one business day.
