The situation this article is about
It is a back seat, or a waiting room, or the twenty minutes between one thing and the next. Someone small wants the phone. You have thirty seconds to decide, and the store page is not going to help you, because the store page was written to persuade.
Our desk runs a formal version of this decision on every game we consider describing as suitable for a younger player. It takes us a couple of hours per title. What follows is the compressed version — the same logic, arranged so that a reader can run it on a game we have never covered, in about three minutes, before the phone changes hands.
The vocabulary, first
Half the difficulty here is that the words on a store listing do not mean what they sound like. These are the ones worth pinning down.
- Content rating
- The band a game declares in the store, together with a short list of descriptors underneath it. The band is a summary. The descriptors are the useful part — they say what produced the band.
- In-app purchases
- A note on the listing that money can change hands inside the game. It says nothing about how hard the game pushes. A single quiet shop and a countdown timer over a purchase panel produce the same line on the listing.
- User interaction
- The descriptor that usually indicates players can reach each other. It covers everything from a full free-text channel to a shared leaderboard where names are typed by strangers.
- Offline play
- The game runs with the connection off. This is rarely stated plainly on a listing, which is why it is the one thing on this list you have to test rather than read.
- Commercial pressure
- Our own term for the difference between a game that will sell you something if you go to the shop, and a game that comes to find you mid-level with a countdown.
The three-minute walkthrough
- Read the descriptors, not the badge. Scroll to the content rating on the listing and read the small text under it. If it mentions user interaction or in-app purchases, you now know which of the later steps matter most. If the descriptors are absent or vague, treat that as a reason to look harder, not a clean result.
- Look at the screenshots for a shop icon. Developers tend to photograph their best screens, and a currency counter pinned to the top corner of every screenshot is a design decision, not an accident. Two or three different invented currencies in the same shot is the clearest single warning you can get without opening the game.
- Switch the connection off and open it. This is the highest-value ten seconds in the whole process. A game that plays normally in flight mode cannot show live adverts, cannot open a chat channel, and cannot carry anyone to an external page. A game that shows a spinner and refuses to start has told you what it depends on.
- Play the first five minutes and count the interruptions. Not the tutorial prompts — the panels selling something. Zero is good. One, on arrival, that closes cleanly, is normal. A panel between every level is a shop with a game attached.
- Try, deliberately, to leave. Tap the corners of the title screen. Tap the logo. Tap the small icons around any results panel. You are checking whether a browser can be opened by accident. If it can, the phone is not really being handed over to the game.
- Look for a text field. Anywhere a player can type — a name, a message, a level title, a comment on someone's run — is a place where words you did not write can arrive. Fixed menus of preset phrases do not carry this risk; free text does.
If steps three through six come back clean, the game is behaving. If any of them does not, you have a specific reason rather than a vague unease, which is a better position to be in either way.
What our desk adds that a listing cannot
The walkthrough above is honest about its limits. It samples the first five minutes, and games are not always the same at minute five and minute ninety. Our own pass exists to cover the gap.
| What the reader can see in three minutes | What we cover in a full pass |
|---|---|
| The opening storefront panel | Whether pressure escalates after the first hour |
| Whether a chat channel is visible early | Whether one unlocks at a later stage |
| Offline behaviour on first launch | Whether offline play survives once progress accumulates |
| The current build | Whether an update changed any of the above since we tested |
That last row is the one we take most seriously. A game can pass every check on the day we play it and fail one three months later, because a feature was added by people who were solving a different problem. Our re-tests exist for exactly that, and a title can lose the description on a re-test as easily as gain it.
Two things we deliberately do not do
We do not use age markers in our write-ups, and we do not describe what a game contains in terms of the things it avoids. Our note is a plain statement that specific mechanical checks passed — rating and descriptors read, no commercial pressure during play, no open text between players, no external links reachable by tapping, plays with the connection off. Readers can apply their own judgement to their own household, which they are far better placed to do than we are.
We also keep this entirely separate from the score. A game can pass all five checks and still be a dull, thin, repetitive thing that we place near the bottom of the table. Suitability is a gate, not a merit. Our editorial score out of ten is our own judgement about quality, produced by the process described on our methodology page, and it is deliberately not the Play Store star average.
The current table is on the front page, and the rest of our explainers are indexed on the blog.