Direct Answer
Education platforms are scheduling and progress-tracking systems with video attached. We build course, class, enrolment, attendance and progress models first, then layer delivery — recorded, live or blended — on top.
Suitable For
- Training institutions needing enrolment, scheduling, attendance and renewal tracking
- Course creators needing a branded platform instead of renting a marketplace
- Corporate training teams needing internal courses, assessments and completion records
Not Suitable For
- Content libraries with no scheduling, assessment or progress requirement — a hosting service is cheaper
- Products depending on unlicensed third-party course material
Core modules and the data each one owns
| Module | Scope, data and rules it owns |
|---|---|
| Course & curriculum | Course, chapter, lesson and resource tree; prerequisite rules and publish state. |
| Class & scheduling | Class groups, teacher assignment, room or channel allocation, recurring sessions and make-up lesson rules. |
| Enrolment & entitlement | Who bought what, when access starts and expires, remaining lessons, transfers and refunds. Entitlement is checked server-side on every playback request. |
| Attendance & progress | Check-in records, watch progress per lesson, resume position, and the completion rule per course. |
| Assessment | Question bank, paper assembly, auto and manual grading, retake policy and score history. |
| Teacher & parent views | Teacher workload and class roster; parent-facing progress, attendance and homework feedback where required. |
Step-by-step Process
- Send the current workflow, the roles involved and where the process breaks down today
- We map the data model, the modules needed at launch and what can wait for a later phase
- Confirm scope, integrations, acceptance criteria, source-code ownership and deployment responsibility
- Iterative build with demos at each milestone, then functional, compatibility and performance testing
- Deployment, source-code and documentation handover, then an agreed maintenance path
Buyer Checklist
- One primary user workflow and one admin workflow defined for the first release
- Role and permission matrix agreed before development, enforced in the backend
- Integration accounts and API credentials confirmed as available
- Data migration source, format and volume reviewed
- Acceptance criteria written per module, not per screen
- Source-code ownership, deployment responsibility and maintenance scope stated in the contract
Information Needed for Quotation
- The workflow you want to replace or build, and who performs each step
- User roles and what each role may see and edit
- Platforms required at launch (web, mini program, iOS, Android, desktop)
- Systems to integrate: payment, ERP, WMS, hardware, accounting, third-party APIs
- Existing data to migrate, its current format and rough volume
- Whether source-code handover and self-hosting are required
Frequently Asked Questions
How do you stop paid course content being shared or downloaded?
Playback runs on short-lived signed URLs tied to an entitlement check, with optional dynamic watermarking of the account ID over the player. No client-side scheme is unbreakable; the goal is to make casual sharing impractical and traceable.
Can it handle both live and recorded classes?
Yes. Live sessions integrate a third-party RTC SDK while attendance, entitlement and progress stay in our data model, so recorded and live courses report through the same progress and renewal logic.
Which platforms do you build for this industry?
Web app for desktop study and admin, WeChat mini program for enrolment and check-in, iOS and Android apps when offline download or push reminders matter, plus an admin panel for the academic office.
What can you integrate with?
Video hosting and CDN with signed playback URLs; live-class SDKs; payment and instalment plans; SMS and template message reminders; export to existing student information systems.
Will we own the source code?
Source-code handover, repository access, deployment notes and database documentation can be included in the agreed scope. State it in the brief so it is priced in rather than added later.
Can you take over an existing system instead of rebuilding?
Yes. We start with a code and environment review, then propose a scoped plan for bug fixes, refactoring, UI rework or new features. Rebuilding is only recommended when the review shows the existing codebase cannot carry the roadmap.
Related Pages
Request a Quotation
Include the fields listed above so the response can focus on model, material, fitment or service scope instead of generic claims.
Request a Project Estimate
Tell us about the product goal, current workflow, target platform, constraints and decision timeline. We will review the scope and recommend a practical next step.