I built Math Builders for my daughter because I kept seeing the same problem in the apps and worksheets we tried. A kid could get a decent score, but one or two facts were still slow every single time, and those facts never really got isolated.
The real issue was not whether she had "seen" the fact before. It was whether she could pull it back fast enough for the rest of math to feel easy.
That pushed me into building the practice loop a little differently.
The part I kept seeing other tools miss
Most practice tools are good at giving you more reps.
What they are not always good at is noticing which exact facts are still dragging and then bringing those back before the kid drifts into fake fluency. A mixed score can hide a lot. Seven facts may be automatic, two may still take five seconds, and one may just be a lucky guess.
So I stopped thinking about practice as "did you finish the set" and started thinking about it as "which fact is still too slow to count as stable."
That changed everything.
Why I landed on spaced repetition for math facts
Spaced repetition is usually discussed around flashcards, vocabulary, or memorization systems, but it maps pretty cleanly to math facts too. If a fact comes back quickly and cleanly, show it less. If it comes back slow or wrong, bring it back sooner.
Simple idea, but it makes practice feel less random.
The part that mattered most for us was not some big algorithm story. It was just having the session spend more time where the friction actually was. That meant a kid was not forced to grind through a giant mixed set becuase the app decided "practice happened" already.
Short sessions mattered more than I expected
I also built around a short-session ceiling. Two to five minutes has been a lot more useful than the longer sessions I grew up associating with drill practice.
That is partly attention span, partly morale.
If a session is short, it is easier to come back tomorrow. If it runs too long, even a good practice mechanic starts feeling like punishment. That was one of the things I had to relearn building this. More minutes is not automatically better minutes.
What I ended up shipping
Math Builders is still the same one-parent project it has been the whole time, no big growth story here, but the core loop now does the thing I wanted in the first place:
- per-fact recall tracking instead of only mixed-score feedback
- short daily sessions
- weaker facts resurfacing sooner
- stronger facts spacing out instead of clogging every session
If you want to see the route that came out of that work, it is here: Math Builders math facts practice.
I still think the biggest lesson was this: practice feels better when it behaves like a memory problem instead of a worksheet problem.
Top comments (0)