An education app landing page for learners, parents and schools
An education app has more than one reader to convince: the learner who will use it, often a parent who pays, sometimes a teacher or a school that recommends it. Each of them wants to see what a lesson looks like and how progress is shown before they install anything.
This kit builds the site from the app’s screens: today’s lesson as the main one, new topics filling the list, the week’s progress, one exercise up close, and plans that can speak to each reader — free, premium, family, schools. If there’s a dashboard for teachers or parents, its desktop screenshot goes on a laptop.
It’s the app’s website, and nothing else: no accounts, no classes, no data about any learner. The main button opens the store or your sign-up page; a school plan’s button can open a page for talking to you.
What your site shows
Today’s lesson
The page opens with your main screen — today’s lesson, the streak, the next step — on a phone, next to your headline, the line that says what the app teaches and to whom, and the button to install it. A teachers’ or parents’ dashboard, if you add its screenshot, shows on a laptop.
How it teaches, in four screens
Four screens chosen from the app, shown together with your heading and text: a lesson, the list of topics, the progress, an exercise — the method, visible at once.
New topics arriving
The list starts empty and fills, one by one, with the lessons or words you write — “Past tense”, “Fractions”, “The water cycle”. It shows the curriculum as concrete things to learn, not as a promise.
Progress over the week
The overview screen, with a text of yours: the week’s practice, the streak, what’s been mastered — what a parent or a teacher wants to see first.
One exercise
A detail screen on its own, for the exercise that best shows how your app teaches: the question, the hint, the correction. Your title and text go with it.
A plan for each reader
The plans take up to four cards, which suits an education app well: free, premium, family and schools, each with its price, its lines and a button — the schools one can lead to a page for booking a call.
Have this ready
- Five screenshots from an invented learner’s account, 390 × 844: today’s lesson, a topic list full and empty, the progress, one exercise
- A 1440 × 900 screenshot of the teacher or parent dashboard, if there is one
- Up to ten lessons or topics, a couple of words apiece, for the list
- The app’s name, a slogan, what it teaches and for which ages
- The main button’s link: the store, or the page where people sign up
- Your plans — free, premium, family, schools — with prices and links
- The address of the app’s privacy policy, above all if children use it, for the footer
- Who is behind the app, in a few lines, and your details for the legal notice
Worth knowing
An invented learner in every screenshot
No real child’s name, photo, school or marks in the screenshots. Set up a demo learner with made-up progress; with minors, even a first name is too much.
Say which ages, and what that means for data
Say plainly which ages the app is for. If it’s children, their data comes with stricter rules — in the EU, each country sets the age, between 13 and 16, below which a parent must consent — so link the app’s privacy policy from the footer, where parents can find it.
Show what is learned, not a promise
Let the list items be real lessons — the verbs, the fractions, the water cycle — and leave out promises of fluency or grades by a date: what someone learns depends on how much they practise.
Plans that match who pays
A parent compares the family plan, a school the price per class or per pupil. Name each plan after who it’s for, and write what it’s per in their terms: “per month, 4 children”, “per class, per year”.
Questions
- Children use our app. Does the site collect anything about them?
- No. The site has no forms, no accounts and no cookies; its buttons send people to the store or your sign-up page, and whatever data the app handles stays in the app.
- Can the site show the teachers’ side too?
- Yes: the phones carry the learner’s screens, and a desktop screenshot of the teacher or parent dashboard goes on the laptop. Say in the words which is which, and give schools their own plan.
- Our lessons are videos. Does the kit play them?
- No: every screen on the site is a screenshot, a still picture. A trailer or a sample lesson hosted on YouTube, or on a page of yours, can be linked from the footer.
- We teach a language. Which language should the site be in?
- The learners’, not the one being taught: an app teaching English to Spanish speakers gets its site in Spanish. The kit makes sites in English or Spanish, one per site.
- Can schools pay by invoice?
- The site doesn’t take payments at all. The schools plan’s button can open a contact page or a calendar for a call, and invoices stay with whoever handles your billing.