Project Overview

LMS Hub Mobile is not two separate apps. On login the app asks the server who the user is, then builds the matching navigation. The role is never chosen on the device — the server decides, and every request is still verified in the backend.

The Challenge

Learning on a phone meets real conditions: signal drops, incoming calls, the app closing mid-quiz. A session expiring during an exam is a product failure, not a minor annoyance.

Scope of Work

• Dynamic, server-driven role-based navigation
• A course player that stores watch position in seconds on the server
• A quiz engine with autosave and a visible countdown
• Instructor modules: KPIs, a cross-course grading queue, and earnings reports
• Secure session handling via Keychain and Keystore with silent background refresh
• 25 screens plus three accompanying PDF manuals

Key Features

• One app, two roles; accounts holding both can switch modes without logging out
• A continue-learning list whose button reads Start, Continue, or Repeat based on progress
• Stop on the phone, resume on the laptop — watch position lives on the server
• Six question types, answers saved as you go, and automatic submission at time-up
• Self-issued certificates with public QR verification, shareable straight from the phone
• Zoom and BigBlueButton live classes open in-app with attendance recorded
• App name, logo, and currency pulled from backend settings, so rebranding needs no rebuild

Technology

Flutter with go_router, provider, and dio; one codebase for Android and iOS, four languages including right-to-left Arabic. The app is a client of the LMS Hub backend.

Outcome

Students can finish a course entirely on a phone while instructors grade and track earnings without a laptop — with data scoping still enforced server-side.