Building an LMS for Bharat: engineering for 4G, mid-range Androids and real learners

Most LMS platforms are built on campus fibre and tested on laptops. Indian learners are on mid-range Androids, intermittent 4G and monthly data caps — and they abandon platforms that don't respect those constraints, no matter how good the content is.

Three engineering decisions carry most of the outcome. Adaptive bitrate video with 360p-first defaults, because smooth beats sharp on a patchy connection. Downloadable lessons with resumable transfers, because a commute shouldn't cost a full re-download. And a UI that stays responsive on 2GB RAM devices — which in practice means lean bundles, cached lists and discipline over animation.

The product decisions matter as much: WhatsApp-friendly notifications instead of email dependency, offline-first attendance and homework for teachers in low-connectivity schools, and assessments that tolerate a dropped connection mid-test without losing answers.

The proof is in completion rates: platforms engineered this way routinely see 2–3× course completion versus generic LMS deployments with identical content. The lesson generalises beyond education: in India, the low-end device is the median user, and designing for it is not charity — it's just correct engineering for the actual audience.