Skip to content

Product engineering

Talk to us Discuss a Project

Case study · Regional-language EdTech

Bright Edutech

A video learning platform for students outside the metros, where the deciding constraint was not features but the cost of delivering video at all.

Production system

Engagement
MVP design and engineering
Platforms
Android app and web
Role
Product, engineering and infrastructure
Market
India Verify before publishing
The Bright Edutech Android app: a regional-language lesson catalogue, a video lesson playing with its accompanying notes, and the admin dashboard where lessons are uploaded and transcoded.
Industry
EdTech
Users
Students in tier-2, tier-3 and rural India
Content
Video lessons and notes
Platforms
Android + web
Role
MVP build
Status
Production

01The business situation

The competition was not other apps. It was the price of bandwidth.

An education startup from Assam set out to reach students in tier-2, tier-3 and rural India with lessons in their own regional language. The market was crowded with feature-rich platforms, and none of them was the real obstacle. Video delivery on a managed CDN would have cost more each month than an early-stage company could carry, and the product only works if the video plays.

Core challenge

Deliver smooth video learning at a price an early-stage company can sustain, without handing the economics to a managed CDN.

Before

Regional-language learners underserved by metro-first platforms

  • English-first Content
  • Metro Pricing
  • Managed CDN Costs
  • Feature Bloat

After

Regional lessons delivered on infrastructure the business can afford

  • Student
  • Lesson Library
  • Video Pipeline
  • Admin

Bright Edutech Platform

02The system at a glance

One platform. Four connected parts.

  • Web Presence Discovery and subscription
  • Android App Lessons, video and notes
  • Admin Dashboard Content, students and accounts
  • Account Controls Session-based device limits
Core PlatformCustom video delivery on commodity infrastructure
  • Lesson Catalogue
  • Video Transcoding
  • Adaptive Delivery
  • Notes & Materials
  • Subscriptions
  • Device Limits

03Workflow 01

Lessons in the language the student thinks in.

The whole proposition rests on one decision: pre-recorded lessons in the regional language, with notes alongside, at a price below the national competition. The product was kept deliberately simple so that proposition could be tested honestly.

Image placeholder The Android app: subject and lesson catalogue in the regional language, a video lesson playing, and the accompanying written notes for the same lesson. assets/portfolio/bright-edutech/workflow-lessons.png · 16 / 11
  • Regional language throughoutBoth the video lessons and the written notes are produced in the learner’s own language.
  • Two ways to learn the same thingEvery lesson pairs a pre-recorded video with notes, so a student on a weak connection still has the material.
  • Deliberately simpleFeature scope was held down on purpose, so the language proposition was what got tested.

04Workflow 02

Upload once. Serve smoothly, cheaply.

An uploaded lesson is transcoded into chunks and served adaptively, on ordinary cloud storage rather than a managed content network. This is the piece of engineering the business case rests on.

  1. 1Admin uploads

    Image placeholder Admin dashboard: uploading a video lesson with its subject, language and accompanying notes. assets/portfolio/bright-edutech/step-upload.png · 1 / 2.04
  2. 2Transcode & chunk

    Image placeholder Processing view: the uploaded video being transcoded into multiple chunks and quality levels, with progress against the queue. assets/portfolio/bright-edutech/step-transcode.png · 1 / 2.04
  3. 3Plays anywhere

    Image placeholder The lesson playing in the app with smooth seeking, quality selection and no buffering pause. assets/portfolio/bright-edutech/step-playback.png · 1 / 2.04

05Workflow 03

A subscription has to be worth protecting.

If one login can be shared indefinitely, a subscription business does not exist. Account use is bounded: first by device, later by session, which proved the more reliable model.

  • Bounded account useA subscription is limited in how widely it can be used at once, which is what makes the pricing sustainable.
  • Devices, then sessionsThe first implementation identified devices; moving to sessions proved more reliable in practice.
  • Content managed in one placeLessons are uploaded, edited and withdrawn from a single dashboard rather than through engineering.
Image placeholder Admin dashboard: the lesson library with upload and edit controls, the student list with subscription state, and account session management. assets/portfolio/bright-edutech/admin-console.png · 16 / 10
Image placeholder Subscription screen in the app: the plan, its price and the active-device or session limit for the account. assets/portfolio/bright-edutech/subscription.png · 1 / 2.04

06Engineering behind the product

The system behind affordable video.

Most of the engineering effort went somewhere users never see: making video delivery cheap enough that the rest of the product could exist.

  • Custom transcoding pipeline

    Uploaded lessons are transcoded into multiple chunks so playback can start quickly and seek smoothly from any point.

  • CDN alternative on block storage

    Delivery was built on DigitalOcean Volumes rather than a managed network like Amazon CloudFront, which is where the cost reduction comes from.

  • Queue-driven processing

    Transcoding runs through a Redis queue and publishes the lesson when it completes, so an upload never blocks the dashboard.

  • Session-based account limits

    Concurrent use is capped by session, an approach adopted after device identification proved less dependable.

  • Native Android application

    The learner experience is a native Kotlin app, which matters on the mid-range devices this audience actually uses.

  • Content management

    Lessons, notes and student accounts are administered from one dashboard without engineering involvement.

  • Subscription handling

    Plans and entitlements gate access to the lesson library.

    Verify before publishing

07Technical architecture

Under the hood

A native Android client over Laravel, with video delivery built on block storage rather than a managed CDN.

Mobile

  • Kotlin (Android)

Backend

  • Laravel
  • PHP

Frontend

  • Tailwind CSS

Media pipeline

  • Custom transcoding
  • Chunked delivery
  • Redis queue

Cloud

  • DigitalOcean
  • DigitalOcean Volumes (CDN alternative)

08Delivery journey

How the platform was delivered.

  1. Ideation

    Shape the proposition with founder Debjayoti Paul

  2. MVP definition

    Cut scope to what tests the USP

  3. Design

    Mock up and approve app and web

  4. Infrastructure

    Build the transcoding and delivery pipeline

  5. Engineering

    Build the app, site and dashboard in parallel

  6. MVP release

    Ship and gather market feedback

  7. Scaling phase

    Continue development toward growth

The company reports early-months registrations and subscriptions, a monthly infrastructure saving against a managed CDN, and selection for Assam Startup Incubation ’22. Those are the client’s published figures and are pending confirmation. Verify before publishing

09What the system enabled

What the delivered platform enabled

  • Video lessons and notes delivered in a regional language
  • Smooth playback on ordinary cloud infrastructure
  • A transcoding pipeline the business could afford to run
  • Account sharing bounded by session limits
  • Content managed without engineering involvement
  • A validated proposition taken from MVP into growth