Cohort learning platform
A full-stack LMS for cohort-based courses, from checkout to the last lesson.
- Role
- Full-stack development
- Context
- Client work, anonymized
- Category
- Learning platform
This is client or employer work, so it's anonymized: no names, links, internal details or screenshots. The visual below is concept art, not the real product.
The problem
Running a cohort-based course usually means stitching together a payment tool, a video host, a spreadsheet of who's enrolled and a separate place to track progress. Learners bounce between products, and the team spends its time reconciling who paid for what and who should be able to see which lesson.
The product
One platform for the whole learner journey. A learner pays, is enrolled into a cohort, watches video lessons, tracks progress and earns rewards for keeping up. The team runs cohorts, learners and content from an admin area inside the same product, instead of from a stack of disconnected tools.
My contribution
Full-stack development across the learner experience, the admin functionality and the integrations behind enrollment, video playback and payments.
Technical approach
- Enrollment is the source of truth for access. Course pages and lesson videos check the learner's enrollment for that cohort on the server, rather than trusting what the client happens to show.
- Payments confirm enrollment server-side. A successful checkout redirect on its own doesn't grant access; enrollment follows the payment provider's confirmation.
- Video playback is gated by the same rules. Lessons stream through a video platform, and playback is only issued to enrolled learners.
- Progress is recorded per learner per lesson, and gamification is derived from those progress events, so rewards and streaks always agree with what the learner actually completed.
Engineering decisions
- Treating cohort enrollment, not the course, as the unit of access. The same course can run several times with different learners and dates.
- Keeping the admin area inside the product rather than relying on a database console, so the team can run cohorts without engineering help.
- Deriving gamification from progress data instead of storing it separately, which avoids two sources of truth drifting apart.
Challenges and trade-offs
Payments and access are where an LMS gets hard. Payment confirmations can arrive late, twice or out of order, and a learner who paid must never be locked out, while a learner who didn't must never get in. Designing enrollment to be safe under repeated confirmations matters more than any UI detail.
Gamification is a trade-off too. Rewards encourage consistency, but rewards that are easy to game reward the wrong behaviour, so they are tied to completed lessons rather than clicks.
Outcomes
The platform covers the complete cohort journey in one product: enrollment, payments, video lessons, progress, gamification and administration.
Technologies used
- Next.js
- React
- TypeScript
- Node.js
- Payments
- Video streaming