Later

Directions rather than plans. Each of these is something we believe is worth doing and have not yet decided how to do — several will change shape completely before they are built, and some will not be built at all.

Read these as an indication of where the platform is heading, not as a queue.

Learning paths

Courses are currently a flat list per cohort. A path would sequence them, with one course opening on completion of another, and a single progress view across the whole sequence.

The open question is prerequisites: strict gating is simple to build and rigid for anyone who joins part-way through a programme.

An integration surface

Organisations want the platform to be where training happens, not where training data ends up. That means webhooks for the events other systems care about — enrolment, completion, grade — and an API that is documented as a product rather than as an implementation detail.

Offline and low-bandwidth

A meaningful share of learners are on connections where a video-first lesson is not usable. Downloadable lessons and submissions that queue until there is a connection would change who can take part.

This is the item we most want to be pushed on. If it matters to your programme, tell us — it is the kind of work that stays in Later indefinitely without someone making the case for it.

Multi-language content

The interface is English. Courses are authored in whatever language the organisation teaches in, which works, but the surrounding interface does not follow — and for a learner, a Swahili course inside an English shell is a half-translated product.