Move Your Online Education Platform Into a Mobile App

You have enrolled students, but the video lessons only open in a browser, the live class link circulates in a WhatsApp group, and payments are tracked through bank transfer receipts. When a student wants to watch on their phone, they have to log in again every time and can never find where they left off. That disorder is the leading cause of unfinished courses and refund requests: even when the content is good, the student disappears in week two.

How many separate apps does this need?

  • 01

    Student App (iOS + Android)

    Video lesson playback, resume where you left off, offline downloads, joining live classes, taking mock exams, submitting homework, plus subscription and single-course purchase screens.

  • 02

    Instructor App

    Start live classes, take attendance, grade homework and exams, answer student questions, and see per-lesson viewing and completion data from the phone.

  • 03

    Web Admin Panel

    Course and curriculum structure, video upload and transcoding status, question bank, pricing and campaign management, sales, refund and invoice reports, and parent access settings.

What the app includes

  • In-video checkpoint questions pinned to a timestamp
  • Automatic review list built from wrongly answered questions
  • Gap map by topic and learning outcome
  • Post-mock-exam net score calculation and cohort ranking
  • Photographing handwritten homework and uploading it as a submission
  • Timestamped notes on a lesson, exportable as a study sheet
  • 0.75x-2x playback speed and remembered subtitle preference
  • Drip content: units unlock on a weekly schedule
  • Bulk student enrolment via an institution code, with class assignment
  • Live-class attendance with minute-level participation report
  • Certificate PDF generation with a public verification code
  • Instructor question queue with response-time tracking

State of the sector

In online education you are no longer competing with the other course provider down the road, but with platforms broadcasting from anywhere in the country and with free video channels. Students make the comparison on their phones: the institution with an app has its lessons in the student's pocket, while the one without leaves them in a browser tab. What you lose without an app is not just sales — you cannot see who watched which lesson for how long, where they stopped, or which topic they struggled with. Without that data, content cannot be improved, and when renewal season arrives there is no concrete progress report to show the parent. For regional course providers, a mobile app is the most direct way to play on the same field as a well-known brand.

Metrics that matter here

  • Course completion rate — Resume-where-you-left-off, downloadable lessons and reminder notifications carry the student to the end instead of losing them halfway through.
  • First lesson watched within 7 days — How easy the first launch is after purchase is the single strongest predictor of refund requests and dormant registrations.
  • Subscription renewal and cancellation rate — In-app progress reports, parent visibility and a reminder before renewal directly influence the cancellation decision.
  • Drop-off minute per video — The panel shows which lesson students leave and at what minute, so content and player performance can be fixed accordingly.

Common mistakes in this sector

  • Serving video over a plain MP4 link Share one address and the whole course goes into free circulation, with no way to find who leaked it. The right approach is HLS segmentation, signed links that expire, DRM encryption and a watermark stamped with the student's details.
  • Leaving the in-app purchase model until later Digital lesson sales cannot run through a credit card form on iOS; the app is rejected in store review and the launch date slips by weeks. Whether sales happen on the web or inside the app must be decided in the first week.
  • Focusing on live classes and neglecting recordings A student who cannot attend feels they are not getting what they paid for and asks for a refund. When a live class ends, the recording should automatically become on-demand content and file itself under the relevant unit.
  • Leaving the parent outside the flow For under-18s the parent pays and the parent decides on renewal. In an app without parent visibility, progress cannot be demonstrated — and the consent required to process the child's data is missing as well.

Regulation and compliance

Private education institutions delivering distance learning are subject to the permits and regulations of MEB (Turkish Ministry of National Education); the range of courses the app sells on the institution's behalf must stay within the scope of that permit. If the student is under 18, parental consent must be obtained for processing personal data, and the explicit consent text must be placed inside the purchase flow. Digital content sales require a distance selling agreement and pre-contractual disclosure; where content becomes accessible immediately, the consumer must explicitly acknowledge that the right of withdrawal is waived. An e-Arşiv invoice is issued through GİB (Turkish Revenue Administration) for every sale. Lesson recordings and live class footage are managed with defined retention periods under KVKK (Turkey's data protection law, aligned with GDPR).

The real challenges in this sector

  • Lesson videos being copied and links shared

    One leaked MP4 link puts the entire course into free circulation. Videos are segmented as HLS and served through signed URLs that expire; they are encrypted with FairPlay on iOS and Widevine on Android. The student's name and the last four digits of their phone number are stamped on screen as a moving watermark, and the number of concurrent sessions per account is capped server-side.

  • Selling digital lessons on the App Store and platform commission

    Because courses, subscriptions and lesson bundles count as digital content, in-app purchase is mandatory and platform commission applies. The model is chosen up front: either sales happen on the website and the app only grants access, or in-app purchase is used. In both cases the subscription state is held on your server, and Apple and Google receipts are verified server-side.

  • Keeping live classes alive on a mobile network

    Students join from a bus or over weak home Wi-Fi. The WebRTC stream is distributed through an SFU, and when bandwidth drops it automatically steps down to a lower resolution and, if necessary, audio only. The session is silently re-established when switching between LTE and Wi-Fi, audio continues when the app goes to the background, and the class is recorded server-side and turned into on-demand content automatically.

  • Offline downloads and syncing playback position

    For students who want to watch without internet, video is downloaded encrypted and unlocked with a time-limited offline licence; once the licence expires the file is useless. Playback position is sent at intervals and when the app closes, and waits in a local queue when there is no connection. When the same lesson is watched on different devices, the furthest position wins, so a lesson left on the phone opens at the right point on the tablet.

  • Making the mock exam engine trustworthy

    In a timed exam the countdown cannot be left to the device clock; start and end are stamped with server time. Questions and images are downloaded before the exam begins, every answer is saved instantly, and if the connection drops answers queue locally and are sent once it returns. Maths and science formulas are rendered as formulas rather than images, and the result report breaks performance down by topic and learning objective.

Required integrations

  • Instalment payments and recurring subscription billing via iyzico or PayTR (Turkish payment providers)
  • GİB (Turkish Revenue Administration) e-Arşiv invoicing integration — an automatic invoice for every digital lesson sale
  • Apple App Store and Google Play in-app purchase receipt verification service
  • Video CDN infrastructure with HLS transcoding and signed URL support
  • WebRTC-based live classroom server (SFU) or the Zoom SDK
  • SMS provider and email for lesson reminders, OTP codes and subscription renewal notifications

Who this page is for

  • A face-to-face tutoring or study centre moving into digital delivery

    Enrolment and classes already exist; what is needed is bulk sign-up by institution code, cohort scheduling, live classes and mock-exam analysis. Access comes from enrolment rather than in-app purchase, which simplifies the store-commission question.

  • A boutique online course brand run by a single instructor

    Needs content protection and recurring revenue rather than cohorts or an exam engine. A Phase 1 scope is enough: catalogue, protected video, drip release, subscription and a simple progress report; the web panel replaces a separate instructor app.

  • A newly founded training company selling vocational courses to employers

    The buyer is the employer, not the learner. Seat licences, progress reports by department, certificates with verification codes and SCORM package support matter most, with one invoice per contract and access granted by contract instead of in-app purchase.

A phased plan that splits the budget

  1. 1

    Phase 1 — Course catalogue, video lessons and access 5-7 hafta

    Ships the student app, a protected video player, the course catalogue, access by purchase or institution code, and course setup in the web panel. It stands alone as a sellable product: students watch on their phones and the school sees who reached where. Video delivery and access rules sit at the bottom of the stack, so they are built first.

  2. 2

    Phase 2 — Live classes, instructor app and homework flow 4-6 hafta

    Adds live-class integration, attendance, automatic filing of each recording into its unit, the instructor app, and homework submission and grading. It follows once Phase 1 has proven that content is actually being watched; the live schedule and instructor workload are planned against real viewing data.

  3. 3

    Phase 3 — Question bank, mock exams and progress reporting 4-6 hafta

    Brings in the question bank, the timed mock-exam engine, analysis by net score and learning outcome, the wrong-answer review list, the parent view and certificates. It comes last because it demands the most content work and the heaviest testing, and an exam engine only produces meaningful data once a student base exists.

Typical scope and timeline

Typical scope: a student app (native iOS and Android), an instructor app and a web admin panel; video player and DRM setup, offline downloads, live class integration, a mock exam engine, payment and subscription flows, and an e-Arşiv invoicing connection (part of e-Fatura, Turkey's mandatory e-invoicing system). UI/UX design, store assets, ASO, QA and the App Store and Google Play release process are included.

Estimated timeline: 10-16 weeks

Off-the-shelf or custom build?

Topic Off-the-shelf Custom build
Time to launch and video infrastructure A ready LMS ships transcoding, player and CDN out of the box; a catalogue can go live in days and you maintain none of it. Custom work has to build that layer, which takes time; in return player behaviour, DRM and watermarking are tuned to how valuable your content actually is.
Exam and learning-outcome workflow Ready platforms offer multiple-choice quizzes and completion percentages, which is often enough for certificate courses and language training. Net scoring, outcome-level breakdowns, targeted review lists and server-stamped exam sessions only match your own model in custom development.
Per-user monthly fees versus growth With few students a monthly subscription is the cheapest route and lets you test the idea without an upfront build. Per-seat pricing grows with scale and eats into margin as sales rise; custom development is a one-off cost, after which only hosting and maintenance remain.
Data ownership and connecting to existing records Ready platforms start fast, but your student list, viewing history and exam records live in their format and export is usually limited. With custom development the data sits in your own database, connects directly to your student-record software and to e-Arsiv (Turkey's electronic archive invoice system), and stays portable.

Sector glossary

Learning outcome (kazanim)
The smallest measurable unit of a curriculum, standard in Turkish schooling. Lessons and questions are tagged to it, so a report shows not just the weak topic but the exact sub-step where the student stalls.
Net score (net)
The scoring rule of Turkey's central exams, where four wrong answers cancel one correct answer. A mock-exam engine must compute results this way so the number means the same thing as in the real exam.
Drip content
Unlocking units on a schedule instead of opening the whole course on day one. It keeps students on pace and makes it harder for anyone to pull the entire catalogue down in one sitting.
SCORM / xAPI
The standard formats for packaged e-learning content and its progress data. If you licence ready-made training packages, the app must be able to open them and write completion data back.
Cohort
A group of students who start together and move through the same calendar. Live sessions, homework deadlines and rankings are built per cohort, which needs different plumbing than an always-open self-paced course.

Frequently asked questions

Let us talk about your project

A free 30-minute call to scope it out, then an itemised quote within 48 hours.

Get a Free Quote

This page explains the problems an app must solve in this sector. We share references and comparable projects during the call.

Other sectors

All sectors →