LearnQuest AI — a project by Ahsan Mahmood
750+ games and learning activities for kids ages 1-15
An audience that runs from age 1 to age 15 is not one audience. It is several, and they share very little.
That range is the whole design problem.
A child who cannot yet read needs an interface with no words in it. A child at the top of that range will abandon anything that looks as though it was made for the one at the bottom.
An interface for the youngest end is mostly pictures, sound and very large targets. One for the oldest end is closer to what an adult expects, and covering both honestly is the part that is easy to promise and hard to build.
LearnQuest AI carries 750+ games and learning activities across the whole span.
The number is the easy part.
750+ is written with a plus, which is a hedge rather than a rounding. A library that grows has no stable count, and a page quoting an exact one would be stale by the next addition.
Age-appropriate content answers the range. Progress tracking is what makes a second visit continue rather than start again, and personalised learning paths sit over the top of both.
Those are the four the record names.
How the matching is decided, which subjects are covered and what a path is composed of are not written down anywhere I can point at, so they are not written down here either.
A children's product is a bad place to guess.
Progress tracking is worth one more sentence than it usually gets.
Anything that lets a child pick up where they stopped is keeping a record about a child, and a record about a child is a responsibility somebody owns whether or not the feature list mentions it. The person who owns it here is the same person who wrote everything else.
The stack is ordinary and the record is short about it.
React and TypeScript with Tailwind on the interface, Firebase underneath, and AI and ML listed beside them. Listed is the accurate word: the record names the category and does not name a model, a provider or a mechanism, so a page filling that in would be describing something it had never seen.
A name is not evidence.
Firebase carries the whole backend.
There is no server here that has to be kept alive, which is the arrangement that lets one person keep a product like this running for years instead of for a launch week.
What it cost is the claim nobody gets to make.
There is nothing on this page about what a child learns, how quickly they learn it, or how any of it compares with a classroom or another application. Those are outcome claims, and an outcome claim about a child's education is the kind that ought to arrive with evidence attached.
There is none here.
So the page describes an activity library with age filtering and a progress record, which is what the thing actually is.
The second cost is breadth.
750+ activities is 750+ things that have to work, read correctly on a small screen and stay appropriate as a child moves up through fifteen years of the range. Nothing about that count makes any one of them easier.
The record marks it completed.
It is at learnqai.aoneahsan.com.
Age-appropriate is a claim about content and a promise about judgement, and one person made every part of it.
What it does, and what that costs to build
- 750+ learning games
- Age-appropriate content
- Progress tracking
- Personalized learning
Built with
- React
- TypeScript
- Firebase
- AI/ML
- TailwindCSS
Worth knowing
- education
- kids
- games
- learning
- ai
Who built LearnQuest AI?
Ahsan Mahmood built it working alone, and it is at learnqai.aoneahsan.com. The same person chose the age bands, built the activity library, wrote the progress tracking and set the rules holding one child's record apart from another's. It is React and TypeScript with Tailwind on the interface and Firebase underneath, with AI and ML listed in the stack. The record marks it completed, which is a description of where it stands today rather than a statement about what happens to it next.
What ages is LearnQuest AI for?
Children from age 1 to age 15, which is a range rather than an audience. A child who cannot yet read and a child preparing for secondary school need different interfaces, different pacing and different content, and they will not tolerate each other's. That span is the reason age-appropriate content is listed as a feature rather than as a setting: on a product covering fifteen years of development, matching content to the child is most of the work rather than a filter applied at the end.
What is actually in LearnQuest AI?
750+ games and learning activities, with age-appropriate content, progress tracking and personalised learning paths over the top. Those four are what the record names, and the page you are reading names the same four. Which subjects are covered, how an activity is graded and what a learning path is composed of are not recorded anywhere I can point at, so no version of them appears here. A children's product is a poor place to fill a gap with something plausible.
How does it decide what a child sees?
The record says age-appropriate content and personalised learning paths, and it does not say how either one is decided. So this page reports the capability and stops, rather than describing a matching rule that nobody wrote down. That distinction matters more here than on most products: a claim about how a child's material is selected is a claim a parent might reasonably act on, and it should come from the product rather than from a portfolio page trying to sound complete.
Does LearnQuest AI work on iPhone?
No, there is no iOS build. LearnQuest AI is a web application, so an iPhone or an iPad opens it in a browser exactly as any other device does, which for an activity library is most of what an installed application would have offered anyway. There is no Apple Developer account behind this work, so nothing built here has been submitted to the App Store. That is true of all of this work, and it is stated rather than left to be discovered.
https://aoneahsan.com/projects/com.aoneahsan.learnqai