
TrackMyBatch — Learning Management System
Replaces an institute’s paper attendance and spreadsheets with one system split across three role-specific apps.
A complete LMS with three role-specific Flutter apps (Admin, Teacher, Student) over a Node.js + MySQL backend — attendance, course/batch management, performance analytics and reporting.

- Industry
- Education / EdTech
- Role
- Full-Stack Engineer
- Type
- Mobile App
- Year
- 2025
01
Overview
TrackMyBatch is a complete Learning Management System for educational institutes, delivered as three specialized Flutter applications — Admin, Teacher and Student — over a shared Node.js/Express + MySQL backend.
The Admin app controls the whole institute: students, teachers, courses, batches and detailed reports. Teachers mark attendance, track performance, manage assignments and communicate with students. Students access courses, attendance, performance metrics and announcements.
The system features real-time sync, PDF report generation, Excel import/export and rich charts, all built on role-based access control across the three apps and a published Android release.
02
Business challenge
Institutes ran attendance, performance and communication on paper and spreadsheets, with no single system connecting administration, teachers and students.
Before this system
03
Solution
Built an LMS with three role-specific Flutter apps over one Node.js/Express + MySQL backend, giving each role exactly the tools they need with real-time sync and rich reporting.
What it does
04
My contribution
- Role
- Full-Stack Engineer
- Scope of my work
- Backend API and the three Flutter applications
05
Product screenshots
Screens from the application itself. Select any image to view it full size.
06
Architecture
Swipe sideways, or expand to zoom.
Three role-specific apps over one API
Each audience gets an app built around its own work rather than one app with hidden menus. All three call the same REST API, where role-based access decides what a request may read or change, and MySQL remains the single system of record.
- Interface
- Service
- Data store
How it fits together
- 01Node.js / Express REST API with MySQL as the system of record
- 02Three Flutter apps (Admin, Teacher, Student) consuming the shared API with role-based access
- 03PDF generation and Excel import/export for reports; charting for analytics; real-time data sync
07
Engineering challenges
01
Three audiences with very different jobs
- The difficulty
- Administrators, teachers and students each need a different set of tools and must see only what their role allows.
- Why it mattered
- One application carrying every feature for every role is confusing to use and easy to get wrong on permissions.
- What was built
- Three role-specific applications backed by one API that enforces role-based access.
- Why this approach
- Each application stays focused on one role’s work while the rules live in one place on the server.
- Result
- Every role gets a purpose-built experience, and the backend is written once.
08
Technology stack
- Frontend
- FlutterGetX
- Backend
- Node.jsExpress.js
- Data
- MySQL
- Infrastructure
- PDF GenerationExcel IntegrationREST APIs
Why these choices
- Flutter + GetX
- Three applications sharing one toolkit and state approach.
- Node.js + Express
- One REST API behind all three applications.
- MySQL
- The system of record for institutes, batches, attendance and results.
- PDF and Excel
- Reports in the formats institutes already exchange.
09
Security & scale
Security
Scalability
10
Business impact
Every figure is labelled with where it comes from: a measurement, an estimate, a design target, or a fact of the system as built.
3
Role-specific applications
Administrator, teacher and student.
Published
Google Play listing
Available on the Play Store.
What changed
- Attendance and performance
- BeforePaper registers and spreadsheets.
- AfterRecorded in the application and reported automatically.
- Communication
- BeforeNo shared channel between office, teachers and students.
- AfterAssignments and announcements inside the same system.
Digitized end-to-end academic operations — automated attendance, performance tracking and institute-wide communication — in a published, multi-role product.
11
Project status
What I took from it
- Role-specific apps over a shared API keep each experience focused while reusing one backend.
A learning-management system that gives each role its own application and keeps the rules about who can see what in a single API.
Next step
Need a similar solution for your business?
Tell me what you are trying to build or fix. I will come back with how I would approach it, what it realistically takes and where the risks are.