Learning platform (LMS)

Self-paced courses centre on content: modules, videos, exercises, progress, certificate. Live courses and tutoring centre on organisation: availability, booking, room or video link, attendance, billing per session. Cohort courses sit in between and additionally need groups, deadlines and discussion.

Many projects fail because a system for one format is bent to fit another. So we first establish which format carries the revenue and build the first scope for that alone.

Learners want to pick up where they left off in a few steps — most often on a phone. Teachers need their calendar, their groups and a quick way to share material and feedback. Administration needs the overview of bookings, payments and capacity.

With younger learners a fourth role appears: parents, who book and pay but do not learn. This account model should be right from the start, because it is hard to change later.

Videos sit with a specialised streaming service rather than on your own server — that saves cost and protects against simple downloading. Payments run through a payment provider with subscriptions, bundles and single bookings; invoices are generated automatically.

If you sell courses inside the app, the app stores' rules for digital content apply. It often makes more sense to handle the purchase on the web and use the app for learning. SCORM and similar standards matter mainly for corporate training; for your own content you usually do not need them.

With FlutterFlow and Supabase, a first scope for one format takes a manageable amount of time. Each further format and each piece of assessment logic adds effort.

• Number of learning formats in the first release
• Assessments, automatic grading and certificates
• Scheduling logic: availability, cancellations, substitutes, cancellation deadlines
• Web, app or both — and whether content has to be available offline