Seven Questions to Ask Before You Download Any Math App

I write software for a living, and part of what I've built is a math app for my own kids. That means I've sat on the other side of the screen. I know how the sausage gets made, and I know exactly which corners get cut when a company cares more about session time than about whether your kid learns anything. So the questions to ask before downloading a kids app aren't abstract for me. They're the checklist I actually run before an app touches my kids' tablet.

Most of these you can answer in about five minutes from the store listing and the first launch, before you ever hand the device over. Here they are, in the order I use them.

1. What does it want to sell, and to whom?

Every free app makes money somehow. That's fine. The question is how, because the answer tells you who the real customer is. If the money comes from ads, your kid is the product and their attention is what's being sold. If it comes from a subscription the parent chooses, the incentives point the other way, toward keeping you happy enough to keep paying.

Neither is automatically evil, but ad-supported kids apps make me nervous. The whole business depends on maximizing time in the app, which is the opposite of what you want for a seven-year-old. Check the listing for "contains ads" and "in-app purchases" before anything else.

2. Where do the ads go, and can a kid tap them?

If there are ads, the next question is placement. The dark pattern I hate most is an ad button placed right where the "next problem" button usually sits, or a fake close button that opens the ad instead of shutting it. Kids tap fast and don't read. A single misplaced ad can dump a six-year-old into an app store or a video they shouldn't see.

Launch the app once yourself and just watch where ads appear and how easy they are to escape. If you can't close an ad in under two seconds, imagine your kid trying. This one test catches a lot of junk.

3. Does it actually teach, or just quiz?

A lot of "math apps" are quiz apps wearing a costume. They throw problems at a kid and mark them right or wrong, but they never teach the thing the kid got wrong. That's a flashcard, not a teacher. It's useful for a kid who already understands the material and only needs speed, and close to useless for a kid who's actually stuck.

Look for whether the app explains a miss. When my kid gets 6 times 7 wrong, does the app show why it's 42, or does it just flash a red X and move on? An app that only quizzes will frustrate a struggling kid and teach them that math is a series of things they fail at.

4. Are the rewards tied to real work?

This is the one I care about most, because I've watched how badly it can go. Plenty of apps hand out coins, gems, and prizes for basically nothing. Tap the screen, get a reward. Answer wrong, still get a reward. Sit through an ad, get a jackpot. The kid learns that rewards come from clicking, not from thinking.

What you want is the opposite. Rewards should come from real progress, from getting problems right and getting faster, not from time spent or busywork completed. When I built our app, that was the whole design fight: make the prize mean something by tying it to actual correct work. If a math app rewards a kid the same whether they try or not, it's training the wrong habit, and you'll feel it later when the reward runs dry and there's no real skill underneath.

5. What does it collect, and where does it send it?

Kids apps in the US are supposed to follow COPPA, which limits what they can gather from children under 13. But "supposed to" and "does" are different things. Skim the privacy policy, or at least the store's data-collection summary, and watch for anything about advertising identifiers, location, or sharing data with third parties.

A well-behaved kids app needs almost nothing. It doesn't need your location. It doesn't need contacts. If a times-tables app is asking for permissions that have nothing to do with times tables, that's a flag. Deny what you can and see if the app still works. Usually it does, which tells you the request was never necessary.

6. Can you actually control it?

Look for real parent controls behind some kind of gate. A few things I check:

• Can I set a difficulty or grade level so my kid isn't hammered with problems they can't do yet?
• Can I turn off or limit the flashy stuff if it's too distracting?
• Is there a spending gate so my kid can't rack up in-app purchases with a happy tapping finger?
• Can I see what they actually practiced, not just a "great job" screen?

If the controls are there but wide open, a determined kid will find every purchase button. A simple PIN or math-gate on the parent section is a small thing that tells me the developer thought about this.

7. Who made it, and does anyone answer?

Finally, tap the developer name in the store and see what else they've shipped. A studio with fifty near-identical clone apps and no responses to reviews is probably churning out ad vehicles. A smaller developer who answers questions and pushes real updates is more likely to care whether the thing works.

Read a handful of the one and two star reviews specifically. Five star reviews tell you nothing. The angry ones tell you where the app actually breaks: surprise charges, ads in the wrong place, crashes that lose a kid's progress. That's the real product tour.

The five-minute version

You don't have to do a full audit on every app. Most fail fast. Open the store listing, check how it makes money and what it collects. Then launch it once yourself and watch two things: where the ads go, and whether it teaches or just quizzes. Those two moves catch the majority of the bad ones before your kid ever touches the screen.

The good apps hold up under these questions without much trouble, because someone built them for kids to learn from rather than for a kid's thumb to feed. You can usually tell which kind you're holding within the first minute. Trust that read.