Learning Quests — Building Education Into the Quest Board

As the foundation of Path of Progress came together, I started realizing I could accomplish more than I originally set out to.

The whole premise of the app is building habits and responsibility through the structure of a game. And when I looked at what a family’s actual daily routine looks like — especially homeschool families or families doing supplemental learning at home — homework and academic practice are just as much a part of that routine as cleaning your room or taking out the trash.

So the question became: how do you bring learning into the quest system without making it a mess?

The Problem with Treating Homework Like a Chore

The obvious approach is simple: add “math homework” as a quest, kid completes it, parent approves it, done.

But the moment I thought through that flow, I saw the problems. Who checks whether they actually did it? Did they do it correctly, or did they just rush through? Does the parent need to sit down with them to get them started, walk them through the material, set it all up? That’s a lot of friction — and it defeats the point.

The whole value of the quest system is that kids can move through it with a degree of independence. They see their quests, they do the work, the app tracks the outcome. Adding homework breaks that loop the moment it requires the parent to validate the work manually or set it up from scratch every time.

I wanted learning quests to run the same way. Open the app, see the quest, do the work — no parent required to make it happen.

Learning Modules: Built In and Ready to Go

The solution I landed on was learning modules — interactive content built directly into the quest, waiting for the kid when they open it.

When a parent assigns a learning quest, they’re not just adding a task label. They’re attaching a structured module that launches right inside the app. The kid taps the quest, and the learning session begins. No setup. No prep. No “let me get the worksheet.”

The first module I built was pixel art math. The inspiration came from my mom, who’s an educator and had introduced me to some Google Sheets plugins that generate pixel art math worksheets — the kind where solving the problems reveals a hidden picture. My son has special needs, and that format clicked for him in a way regular worksheets didn’t. The problem was the setup. Every time he was ready to do math, I had to go find the sheet, configure it, get it open and ready for him. It took long enough that it became a genuine barrier. If the moment passed, the session didn’t happen. Consistency suffered.

That’s what I wanted to fix. A parent creates a math quest — selects which operations to cover and how many questions to run — and that’s the last time they have to think about it. When the kid opens the quest, the session is already waiting. Visual aids are available if they need them: number lines, block representations, arrays. The app walks them through the problems, tracks what they got right and what they struggled with, and marks the quest complete when they’re done.

Now my son just launches the quest. No setup, no delay. It happens because the friction is gone.

The completion is automatic. The parent doesn’t need to check the work; the app knows whether the problems were answered. That’s the piece that changes everything.

Taking it Further — Memory Verses

Math was the proof of concept, but the module architecture was always meant to go further.

The second module I built was memory verse practice — a drag-and-drop word scramble system where kids reconstruct a Bible verse by placing words in the right order. Parents set the verse, the app handles everything else. The kid works through it level by level, either in a single sitting or one level per day in a slower daily mode. Progress is tracked automatically, hints are available if they get stuck, and the quest completes when they’ve genuinely mastered it.

Both modules follow the same pattern: the parent configures the learning objective once, the app delivers it as a self-contained experience, and the result is tracked without anyone needing to sit down and supervise the session.

The Learning Tab

Because learning quests generate real data — questions attempted, accuracy over time, which problems gave a kid the most trouble — I built an analytics dashboard alongside the modules. Parents and admins can see how each child is progressing, where the gaps are, and how their performance is trending.

That data matters. If a kid is breezing through addition but consistently struggling with multiplication, that’s useful information. The goal was never to just automate the homework — it was to make it visible and meaningful.

What Comes Next

Learning modules are designed to be additive. The architecture supports new modules without rebuilding anything — the quest system just plugs them in.

I have more in mind. But the foundation is there, and it works the way I always wanted it to: the kid opens their quest, the learning is waiting for them, and they can do it on their own.

That’s the version worth building.