What lernapps is made of
For everyone who uses apps. For everyone who builds apps. And what makes the platform behind them unique.
For teachers, parents and learners
What the apps can do
Every app is built on one of three foundations. That is why they work in a similar way everywhere, and every one is made with the same care.
-
Quiz
Questions with answers to choose from. After every answer it says why it is right or wrong, and where to read on.
-
Explainer
Chapters of pages that explain. Every page has exercises. The pages can be read without JavaScript too.
If you like, add an AI tutor: the app gives your own AI assistant the task, the solution and the typical mistakes. This is optional. The app works entirely without AI and sends nothing itself.
-
Interactive app
Learning by doing: a game, a training, an experiment. What the learners do is the content.
-
Based on the curriculum
The content comes from the state curriculum and the teacher's material. Every app says what you can do afterwards.
-
Exercises with feedback
A wrong answer explains why it is wrong. Then you can try again.
-
One link takes you right there
To the topic, to the section or to exactly the task the whole class should work on. As a QR code too.
-
Made by people
Every app comes from a teacher, a parent or someone who likes to build. We help them build it, but that is no guarantee of quality. You report a mistake in the content with one click on the app's page.
-
Accessible
The apps meet WCAG 2.1 AA and work from 360 pixels wide. Where an app can't, it says so in the catalog.
-
Runs on every device
In the browser, without installing anything: on the projector, on the class tablets or on a phone at home.
For developers
What you get when you build
You bring the idea and the content. lernapps.net gives you foundations, tools and guidance for your AI assistant. And it says openly what you agree to when you contribute an app.
Foundations, or your own stack
With our tooling you create an app from a foundation: quiz, explainer or interactive app. Checks then run on every commit and in CI.
But you can also build freely, with any stack. Then only the platform rules apply: collect nothing, no account, no ads, accessible, usable from 360 pixels, no other servers before a click. Dependencies need an open licence.
Made for your AI assistant
Skills, a plan and rules with fixed IDs guide your assistant through the work: ask, plan, build, check, publish, list. You decide along with it at fixed points.
We test how closely different assistants follow this guidance and publish the results.
How an app gets into the catalog
-
You publish the app in your own repository, at your own address.
-
You submit it: as a pull request to lernapps/apps, or by form or email without GitHub. Anyone can submit an app.
-
An automatic check opens the app the way learners do and compares it with the entry: do all topics open, are the details right?
-
It is checked against the rules for every app. They are exclusion criteria: an app that collects data, needs an account or shows ads does not get into the catalog. An AI agent can also review the app against a checklist.
-
If the app keeps the rules, it is listed, and lernapps.net serves a copy of it. For a finished app, all of this takes a few hours.
Feedback reaches you
Whoever uses your app can say thanks or tell you how it went, up to “mistake in the content”. Today this is an email to lernapps.net, and we pass it on to you.
If your source code is on GitHub, people can also open an issue in your repository straight from the app's page.
Ownership and licence
Your app lives in your repository, at your address and under your licence. The catalog only links to it. We recommend open licences: MIT or Apache 2.0 for the code, CC BY 4.0 for the content. That way others can build on your app, and your name stays with it.
You use content by others, such as texts or pictures, only with a suitable licence and name the source and licence. The platform itself and the tooling are under the MIT licence.
The technical documents are in English.
Build an app →What makes lernapps.net unique
No server. No company. No data collection.
Most learning platforms need servers, accounts and a business model. lernapps.net is built differently. That is why it can stay free.
-
GitHub as a free backbone
This is why it works without money: the apps and the catalog are static pages on GitHub Pages. An entry is a pull request, the check runs in GitHub Actions. There is no server of our own that costs money.
-
Privacy as a feature
Every app runs entirely in the browser. There is no server with data, no database and no account. What is not collected cannot be lost or sold. The privacy notice →
-
Readable for AI assistants
Every part of lernapps.net has an llms.txt. So an assistant can find the right app, explain the platform or build an app itself. Without anyone having to run an API.
-
Planned in the open
We designed lernapps.net with the Platform Design Toolkit: who takes part, what everyone gets out of it, what we try first. Everything is public, including what we don't know yet.
The principles
They apply to everyone alike: to those who build apps and to those who use them.
-
No company behind it
Nobody earns money from lernapps.net. No subscription, no ads, no selling of data. Not later either.
-
Open, not closed
The rules, the plan and the source code are public. Anyone can read how decisions are made here.
-
Your app stays yours
Every app stays with the person who built it. lernapps.net shows it but does not own it.
-
The apps collect nothing
No account, no cookies, no tracking. What someone types stays on their device.
-
Honest about limits
Every app says what it can do and what it can't. We say openly what we don't know yet.
-
Thanks instead of money
Whoever uses an app can say thanks. Today one click opens a ready-made email to lernapps.net, and we pass the thanks on to the person who built the app. Later one click will be enough, without any email.