App stores make installing effortless and vetting impossible — by design. The listing page is a marketing surface, not a disclosure document. Over a couple of years of writing this blog I’ve condensed the pre-purchase check down to seven checks that fit in five minutes, which is roughly what a bad app costs per incident multiplied by how often it happens.
Here’s the checklist, in order of how often each one saves me.
1. Read the one-star reviews first, sorted by recent
Not the average — the recent one-star reviews, looking for patterns rather than individual rants. Three separate complaints about unexpected charges is data; one furious essay about a crash is noise. The recurring phrases that matter: “charged after cancelling,” “can’t log in,” “deleted my data,” “subscription without warning.”
2. Open the in-app purchases list
On every app listing there’s an expandable in-app purchases section. Expand it. Count the tiers, and note which ones exist — the question isn’t whether the app costs money, but whether the full functionality you’re imagining is reachable, and at what total. An app whose core feature sits behind a second subscription, a coin system, and an annual “pro” unlock is telling you its real price in the one place it legally can’t blur.
3. Annualize anything quoted per week
Weekly pricing is the dominant dark pattern in app pricing because 259.48 does not. Multiply before deciding anything: per-week × 52, per-day × 365. The subscription confirmation screen shows the annualized figure — read it there if mental math isn’t handy at the moment of temptation.
4. Check the privacy label / permissions
The privacy nutrition label on each listing states what data is collected and whether it’s linked to you. The pattern worth flagging: an app whose function needs no identity (flashlight utilities, wallpaper packs, single-player games) that nevertheless collects identifiers linked to your identity, or financial data types. There’s no consumer reason for it; the reason that remains is the data business.
5. Look at the developer’s other apps
Tap the developer name. A studio whose catalog is one coherent product line is a different risk profile than one whose catalog is thirty unrelated utilities with similar names — the latter is a common shape for app-farm operations that ship volume, monetize aggressively, and abandon accounts. Two minutes of scrolling the catalog tells you which kind of operation you’re dealing with.
6. Search the developer name plus “refund” and “scam”
Outside the store, in a regular search engine. Store reviews are curated battlegrounds; outside search results are not. If there’s a pattern of billing complaints, it surfaces here first. This check takes thirty seconds and has the highest save-rate per second of anything on this list.
7. Decide the payment path before buying
For a first-time relationship with a developer you know nothing about, the cautious pattern is paying via account balance (a gift card redeemed to the store account) rather than a fresh card binding — the ceiling on any surprise is the balance. For established, reputable developers, card on file is fine. The point is making this a decision rather than a default.
NOTENone of these checks exist to stop you from spending money on good software — good software deserves to be paid for. They exist to make sure the money goes to the product you imagined, at the price you imagined, run by people who behave the way the listing implies.
What the five minutes has caught
Recent saves from the family’s own downloads: a “free” PDF tool whose export function was a third, undisclosed subscription tier; a habit tracker priced per-week at an annual rate higher than the much better established alternative; a kids’ game whose privacy label linked device identifiers and location to identity (for a coloring app); and one app with a purchase flow my kid triggered three times in two minutes before the store’s own grace-window settings caught it — that last one led to the device-level purchase restrictions I now set up on every family device by default.
The meta-rule
An app that survives all seven checks has earned its download and probably its price. An app that fails any one of them isn’t necessarily malicious — but it has told you something about how it intends to make money, and you get to decide that with eyes open instead of three billing cycles later. Five minutes, seven checks, and the app store turns from a slot machine back into a store.
If this article helped you, please share it with others!
Some information may be outdated