Skip to content
All case studies

05 · EdTech · NTT

Fee Management System + LMS micro-frontends

Led the Fee Management System frontend and three micro-frontend services for the LMS.

Context

NTT's EdTech products needed a fee management system for schools, and an LMS frontend split into services that teams can ship separately.

My role

Led the frontend for the Fee Management System with a team of three junior engineers: UI architecture, code reviews, delivery, and working with product. Led three micro-frontend services for the LMS.

Architecture

Architecture, left to right. Users: Schools and institutions → Frontends: Fee Management System, LMS: 3 micro-frontend services → Integrations: REST APIs, Razorpay payments, Mixpanel analytics.

Two products, shared integrations.

Key decisions

  1. 01

    Three micro-frontend services for the LMS

    [WHY: ask Saif — why split the LMS into three services, and where the boundaries sit]

  2. 02

    Redux for state in the Fee Management System

    State lives in one place, so data flow is predictable and fewer runtime errors reach users.

  3. 03

    Jest coverage on critical flows

    Tests cover the critical flows. Code reviews and mentoring keep the standard across the team.

Results

  • Delivered the Fee Management System frontend with a team of three junior engineers.
  • Integrated Razorpay payments and Mixpanel analytics across LMS and ERP.
  • Mentored 3–4 juniors and interns.

Stack

  • React
  • TypeScript
  • Redux
  • Material UI
  • Razorpay
  • Mixpanel
  • Jest