Solutions · Education
Edtech app: what to decide, build and test.
Planning one? Here's what to settle before you brief anyone, what goes in the first version, how the build runs week by week, how the beta is tested with real people, and the numbers that show it's working.
Decisions to make before you brief an edtech app
An edtech brief that says "live classes, tests and doubts" hides four decisions that change the product and the budget.
- Live, recorded or both. Live classes build a batch habit and justify higher fees, but need a streaming service, a moderator and a timetable. Recorded courses are cheaper to run and easier to scale, but completion drops without a schedule. Many teams start recorded plus a weekly live doubt hour.
- Own the streaming or rent it. Renting a video service gets you running quickly and is billed by minutes watched. Self-hosting trades bills for engineering and on-call work. At small scale, rent.
- Test series as the core or an add-on. For exam-prep, tests with rank and topic analysis are what students return for. A strong test engine (question types, negative marking, analytics) is a product in itself.
- Online only, or centres too. Centres add attendance, batch capacity, fee instalments and gate entry, and they bring regulatory rules about timetables and admissions. Hybrid doubles the surfaces.
- One-off course sale or subscription. Paying for a batch and paying monthly for access lead to different refund, renewal and reminder flows. See the subscription app guide.
Before you brief anyone, write down:
- The exams and classes in the first release, and the language of each
- How much content already exists and in what form
- Who writes, reviews and uploads questions
- Your refund and fee instalment policy
- The youngest student you will enrol
What goes in the first batch release, and what waits
| Module | First version | Add later | Why |
|---|---|---|---|
| Course catalogue | Batches, schedule, price, enrol | Recommendation quiz, bundles | Students need to find and pay first |
| Live class | Rented video with chat and hand-raise | Polls, whiteboard, audio-only mode | Basic reliability matters more than features |
| Recorded lectures | Stream plus notes download | Offline downloads with expiry | Download rights need content-protection work |
| Doubts | Typed or photo doubt, teacher answers in a queue | Auto-matching to solved questions | Matching needs a large solved bank first |
| Test engine | MCQ and numeric answers, timer, score, answer key | All-batch rank, topic analytics, adaptive sets | Rank is meaningless below a few hundred attempts |
| Faculty tools | Schedule class, upload notes, answer doubts | Live analytics, assignment grading | Teachers abandon heavy tools |
| Fees | UPI and card, instalments, receipts | EMI partners, scholarship codes | EMI needs a lending partner |
| Centre ops | Only if hybrid: attendance, batch capacity | Gate scanning, timetable compliance checker | Skip entirely for online-only |
| Parents | Progress summary by message | Parent app | Parents mostly want results and fee reminders |
Our concept build RankUp is a worked example of a hybrid product: student app, faculty console and a centre desk with a timetable checker.
How the 10 to 12 weeks run, and what you supply
| Weeks | What we build | What you supply |
|---|---|---|
| 1–2 | Scope, student journeys, content model, test engine rules | Sample lectures, question paper formats, marking scheme |
| 3–5 | Sign-up by OTP, catalogue, payments, recorded lectures | Payment aggregator account, GST details, a first batch of content |
| 5–8 | Live class integration, doubts, faculty portal | Faculty for testing; the live video service account |
| 6–9 | Test engine, results and analysis | At least a few hundred questions, tagged by topic and difficulty |
| 9–10 | Website, admissions, scholarship test page | Faculty photos and profiles, fee and refund text, terms |
| 10–12 | Beta with one batch, load test, store submission | Test phones, including low-end Android; students for a pilot batch |
Content is the usual bottleneck. If the question bank is not ready by week 6, the test engine ships empty. See launching on Play Store in India for store review lead times.
How we work with you each week
The same rhythm runs from week 1 to launch, so you always know what's happening and what we need from you.
- Friday: a demo link and a 30-minute call. You open the latest build on your own phone and try it yourself, rather than watching our screen.
- Within 48 hours: your feedback, in writing. In one shared doc, next to the screen it's about. Written feedback is clear, dated and doesn't get lost between calls.
- Monday: triage. Every comment goes into fix now, next week or later. Anything that changes the agreed scope gets a written quote before we touch it.
- Each milestone: two revision rounds, then your sign-off. Sign-off is against the scope we agreed, so it's clear what done means.
- One decision-maker on your side. Most delays aren't build time. They're feedback waiting on several people who disagree.
The full version, including how the beta and user testing work across every kind of project, is on our process page.
The beta: one batch, one exam
The beta is the single-batch run in weeks 10–12. It starts once a student can enrol, pay, watch a recorded lecture, join a live class, post a doubt and take a timed test, with faculty handling their side without our help.
- What's in it. OTP sign-up, the batch page with real fee and refund terms, UPI and card payment, recorded lectures with notes, the live class with chat and hand-raise, the doubt queue, the test engine with score and answer key, and the faculty portal.
- What stays out. Batch-wide rank, topic analytics, offline downloads, EMI, the parent app and centre operations. Rank especially, because one batch is too small for it to mean anything.
- Who uses it. One real batch for one exam: 30 to 50 enrolled students, two or three faculty who teach it, a doubt moderator, and the admin who handles fees. The institute recruits them from current or incoming students. Include students on low-end Android phones and patchy home data, not only the toppers.
- How they get it. Students install through TestFlight or Google Play testing. Faculty use the web portal on their own laptops. For students under 18, a parent gives consent before the account is opened.
- How long. Three weeks, enough for at least six live classes, two full tests and one fee instalment date.
A new personal Google Play developer account has to run a closed test with at least 12 testers for 14 days before it can publish. Count the beta batch towards that, or use an organisation account.
What we test with real people, and the tasks we set
We give each person a task to finish and watch quietly while they do it, on their own phone and in the language they study in. No hints. Roughly five sessions per role brings out the biggest problems; we fix those and repeat the task. For students under 18 we have a parent's consent before the session, and a parent or teacher can sit in.
| Who | The task | What we watch for |
|---|---|---|
| Student | "Join tonight's 8 pm physics live class from your phone and ask a question with hand-raise." | Does it join on mobile data? Do they find hand-raise? What happens when the network drops mid-class? |
| Student | "Take the 30-minute chemistry test, then find which questions you got wrong and why." | Do they understand negative marking before starting? Does the timer survive a phone call? Is the answer key clear? |
| Student | "You can't solve question 12 from the homework sheet. Send a photo and get it answered." | Is the photo readable? Do they know when to expect an answer? |
| Faculty | "Answer five doubts from your queue and upload tomorrow's notes." | How many taps per doubt? Can they write an equation or attach a photo of a worked solution? |
| Admin | "A parent paid the second instalment twice. Find it and start a refund." | Can they find the student by phone number? Does the refund follow the published policy? |
| Parent | "Find out how your son did in this week's test and when the next fee is due." | Does the progress message make sense without logging in? Is it in the language they read? |
The numbers that say it's working
You choose two or three of these in week 1, with your current figure where one exists, for example attendance in your existing online batches. We add the tracking before the beta batch begins, and report at launch and 30 days after. The numbers are yours to judge; we don't promise them, we make them easy to read.
| Goal | What we measure | Where it comes from |
|---|---|---|
| Students turn up live | Share of enrolled students attending each live class, and for how long | Live video service reports |
| Classes play on real phones | Joins that fail or drop, by phone type and network | App analytics |
| Tests get finished | Tests started versus submitted | Test engine |
| Doubts don't pile up | Time from doubt posted to first answer | Doubt queue |
| Recorded lectures get watched | Share of each lecture watched before the next class | Video player events |
| Enrolment doesn't leak | Drop-off from batch page to paid | Payment and app analytics |
What an edtech app costs, and why it varies
A student app, a faculty portal and an admin or centre desk fit the "two user types plus admin" tier in the app development cost guide, a ballpark of ₹10–25 lakh for a small studio. A recorded-course app for one teacher sits nearer the one-user-type tier of ₹3–10 lakh. These are ballparks, not a quote.
- Live classes. Using a rented service is cheaper to build than custom streaming, but adds a recurring bill.
- Test engine depth. Plain MCQs are quick. Several question types, equations, sectional timers, rank and topic analytics each add weeks.
- Content protection. Stopping screen recording and link sharing is partial at best, and costs engineering time.
- Languages. Each language needs reviewed content, not just a translated interface.
- Hybrid centres. Attendance, timetables and gate entry add a third surface.
Running costs for video storage, streaming and notifications grow with students, so budget for them separately. See edtech app guide.
India rules and habits for an edtech app
- Children. Most coaching students are under 18. The DPDP Act 2023 requires verifiable parental consent before processing a child's data, and bars tracking, behavioural monitoring and targeted advertising aimed at children. The Rules have an exemption for educational institutions limited to their own educational activities or the safety of enrolled children. Whether your platform qualifies is a question for your lawyer, so do not assume it. Obligations are reportedly phased in about 18 months after the November 2025 notification. See the DPDP checklist.
- Notice in the student's language. The Act requires the privacy notice to be available in English or any language listed in the Eighth Schedule to the Constitution. Offer Hindi or the regional language of your batch. See regional language apps.
- Coaching regulation. The Ministry of Education issued guidelines for coaching centres in January 2024 as guidance for States to adopt, so your state's rule is what applies. As reported they set a minimum enrolment age of 16, ask for a prospectus with fees and exit terms, a complaints process, and no misleading claims about results. Check with your state and design batch pages to show real fee and refund terms.
- GST. Supplementary coaching has been treated differently from a school's own education in advance rulings. Confirm with your CA how to invoice and whether to register.
- Habits. Data is the constraint, not the screen. Students download on Wi-Fi at night, share phones with siblings, and prefer UPI. Parents want fee reminders in their language.
This is general information, not legal advice. Regulations on coaching and children's data are changing, so confirm with a lawyer.
Common edtech app mistakes and what to do instead
- Building live streaming from scratch. It consumes months. Rent it first and replace it only when volume justifies.
- Launching tests without a question bank. Students churn on an empty test tab. Load content first, build features second.
- Promising an "all-India rank" with a small cohort. A rank among 200 is not national. Label it as a batch rank until the numbers support more.
- Fake countdown offers and inflated result claims. They risk regulatory attention and parents' trust. Show real prices, refund terms and how results were counted.
- Ignoring weak networks. Test on a low-end phone on 3G-like speeds, and offer audio-only and downloads.
- Leaving faculty out of design. If marking a doubt takes six taps, teachers stop. Sit with two teachers and watch them use the prototype.
- Collecting everything about students. Gather only what teaching needs, and do not use it for ads aimed at minors.
- No moderation for chat and doubts. A minor-heavy chat needs reporting, muting and a named moderator before launch.
Cost and timeline
10–12 weeks for a first version.
Fixed quote within 48 hours of your brief: scope, timeline and price in writing before we start. These are what move the number.
- Live classes, recorded courses or both
- Test engine depth: question types, analytics, ranks
- Offline centres alongside the app
- Content protection and downloads
- Number of languages
Questions
About your edtech app.
How much does an edtech app cost in India?
It depends mainly on live classes, the depth of the test engine and whether you run offline centres too. We give a fixed quote within 48 hours of your brief. The app cost guide covers the drivers. Content migration also matters.
Will live classes work on slow mobile data?
That is the main thing we design for. In our concept build RankUp, live classes adapt to weak connections, quizzes run inside the stream, and lectures can be downloaded on Wi-Fi to watch later. Audio continues even when video has to drop.
How long does it take?
A student app, faculty portal and website usually take 10 to 12 weeks. A recorded-course app with tests can be quicker. A two-week concept sprint gives you a prototype to test with a batch first. We time launch around a batch start.
Can the app be in Hindi or bilingual?
Yes. We build the interface in Hindi or a regional language with English, and support bilingual questions and notes. See our regional language guide. Students can switch language at any time, and faculty can publish the same test in two languages.
Who owns the app and content?
You do. Code, designs and all your course content stay yours, and are handed over in full. Videos and question banks sit in storage accounts in your name, and any team can extend the platform after hand-over. Nothing stays behind with us.
Read next
- EducationApps for coaching institutes: live classes, tests and fees →What a coaching institute app needs in India: live and recorded classes, doubts, test series, batches, attendance and fee instalments, online and offline.
- LanguagesBuilding apps in Hindi, Tamil, Kannada and other languages →How to build an app or website in Indian languages: scripts and fonts, longer text, voice input, transliteration, lakh and crore formats, and translation that sounds right.
- StartupsHow to build an MVP in India: scope, cost and a 12-week plan →A practical MVP guide for Indian founders: what to build first, what to cut, a week-by-week 12-week plan, ballpark costs and the mistakes that waste a first budget.
- TechnologyNative, cross-platform or PWA: choosing for Indian users →Should your app be native, Flutter or React Native, or a progressive web app? A practical comparison for India's budget Android phones, patchy data and app-size limits.
Start a project
Tell us how your business runs. We'll build what it runs on.
Four taps, about a minute. Fixed quote within 48 hours.


