Skip to content
~/ projects / / headless-lms-api

Headless LMS API

A flexible, API-first Learning Management System backend designed for Guinea's education sector.

· Idea ·
Guinea EdTech API Education LMS
project.json
// project overview
"status": "idea",
"tags": ["guinea", "edtech", "api", "education", "lms"],

What I See

I sell laptops to students through Kalinko Store. Every semester, more students in Conakry walk out with a machine under their arm. The hardware problem is shrinking. The software problem is not.

Most schools still run on paper ledgers and WhatsApp groups. The few that digitized bought rigid platforms built for contexts nothing like Guinea. Attendance tracked in notebooks. Grades announced by pinning a sheet to a wall. Parents find out their kid is failing when the year is already over.

The Gap

Every Guinean developer who tries to fix a piece of this — a grade tracker, an attendance app, a parent portal — starts from zero. There is no shared backend. No common API for enrollment, grading, or course management that local teams can build on top of. So effort gets duplicated, projects stall, and nothing reaches scale.

What a Headless LMS API Solves

A headless LMS is the backend layer only. It handles the data and logic — enrollment, grades, attendance, content delivery, notifications — and exposes it all through clean APIs. Any developer can plug in whatever frontend makes sense: a web app, a mobile app, an SMS-based interface, a USSD menu for feature phones.

Schools get a system that fits their workflow instead of forcing a new one. Developers get a foundation instead of a blank page. Parents get visibility. Students get records they can actually access.

What It Would Cover

  • Auth and roles — students, teachers, parents, admins, each seeing what they need
  • Courses and content — modules, lessons, quizzes, assignments
  • Enrollment and attendance — who is registered, who showed up, alerts when they don’t
  • Grading and transcripts — automatic calculations, downloadable records, certificates
  • Notifications — SMS via Orange/MTN gateways, email, in-app
  • Payments — tuition and fees through mobile money

Guinea-Specific Challenges

Connectivity. Outside Conakry, internet is unreliable. The API needs to support offline-first clients that sync when a connection appears. Responses must be small. Every byte counts on a phone hotspot.

Mobile-first. Most users will access this through a phone, not a laptop. The API must serve lightweight clients well. SMS and USSD as delivery channels are not nice-to-haves — they are core.

Local languages. French is the official language, but Susu, Pular, and Malinke are what people speak at home. The content and notification layers need multilingual support from day one.

Trust. Schools and parents need to trust the system with student data. Role-based access, audit logs, and data residency matter here.

Current Status

This is at the concept stage. I am mapping the requirements based on what I hear from students, school administrators, and developers in Conakry. If you work in edtech or education in West Africa, I want to hear what you are building: laminekalinko2@gmail.com