The four parts every first release needs
A learning app's first release should prove one thing: that learners come back and finish lessons. Everything that does not help with that can wait. In practice that leaves four parts, and each one has a minimum version and a tempting bigger version.
| Part | First release | Defer to a later release |
|---|---|---|
| Lessons | Text, images, video or audio in a fixed order, grouped into modules | Branching paths, interactive simulations, downloadable worksheets |
| Quizzes | Multiple choice and true/false, instant feedback, retry | Free-text answers marked by an instructor, timed exams, question banks with random draws |
| Progress | Completed lessons, quiz scores, "continue where you left off" | Streaks, badges, leaderboards, skill maps |
| Authoring | Admin panel to add, edit, reorder and unpublish lessons and questions | Version history, multiple editors with approval steps, bulk import |
Community features, live classes and certificates are the most common additions people ask for in version one. They are reasonable products, and they each add roles, moderation or integrations. Launch without them unless the course does not work without them.
A sample screen list
This list is a typical first release for a course companion. Use it to check your own brief; anything you add beyond it is a scope decision worth making on purpose.
- Welcome and sign-in (email link or password, plus account deletion in settings)
- Course home: modules, the next lesson and overall progress
- Module view with lesson list and completion ticks
- Lesson player for text, video or audio
- Quiz screen with feedback after each answer
- Quiz result with a retry option and a link back to the lesson
- Progress screen with completed lessons and scores
- Notifications settings and reminder time
- Profile and account settings
- Admin panel (web): lessons, quizzes, learners and completion
Apple requires apps that let people create an account to also let them delete it from inside the app, so plan that screen from the start.
Define who can see what
Access rules decide a surprising share of the build. "Learners who paid can see the course" sounds like one rule until you list the cases. Write them down before you ask for a quote.
Access questions to answer in the brief
- Can anyone see a free preview lesson without signing in?
- How does a buyer get access: website purchase, in-app purchase, an invite code, or their employer?
- Does access expire, and what happens to their progress if it does?
- Are learners grouped into cohorts that release lessons on a schedule?
- Can a company buy seats and add or remove its own people?
- Who can see a learner's scores: only them, you, an instructor or their manager?
- Will anyone under 18 use the app?
The last question changes more than the others, because children's data rules and Google Play's Families policies then apply. The education app cost guide explains what that adds.
Content ownership and where lessons live
Two kinds of ownership matter here. The first is the app itself: with DFY Games, after full payment you receive the project files and the original assets created for your app, while third-party services, SDKs, fonts and licensed assets keep their own license terms. The second is your course content, which you wrote or recorded and should stay yours however the app is built.
Protect the second kind with a few practical decisions. Host videos on a service whose account is in your name. Store lessons and questions in a database or content system you can export from. Keep the original files outside the app as well. If you ever change developer or platform, you should be able to move the course without retyping it. The code and art ownership guide covers contract wording for the app side; have a lawyer check the final contract.
Turning the checklist into a scope
Take the table, the screen list and your answers to the access questions, and you have most of a brief. The app brief template adds the remaining sections. You can see what a typical course companion app includes, then send your answers through the quote form for a written scope with assumptions and a quote.
Frequently asked questions
What features should an education app MVP have?
Lessons, quizzes with feedback, progress tracking that syncs across devices, and an admin panel for adding content. Community, live classes and certificates usually wait for a later release.
Do I need an admin panel in the first release?
Yes, unless you are happy to ask a developer for every new lesson. A simple panel to add, order and publish lessons and questions is part of a useful first release.
Who owns the course content in a custom learning app?
Content you wrote or recorded stays yours. Keep it in accounts and systems you control so you can export it, and check the contract for the app's own files and assets.
Should learners be able to use the app without an account?
A free preview lesson without sign-in can help conversion, but progress, paid access and syncing between devices need an account.
Does the app need account deletion?
If people can create an account in an iOS app, Apple requires a way to delete it from within the app, so include it in the screen list.
Written and reviewed by the DFY Games team. Published ; facts checked . Prices and store rules change: check the linked sources before you rely on a figure.