Check App Details: The Filter Before You Install

Additional resource for the lesson “Checking App Details Before You Install” — Online Security course

Almost every problem in this part of the course is prevented at the same moment: the few seconds before you press install. Learning to check app details turns that moment from a reflex into a decision.

A. Why this matters

The resources that follow this one describe different things that go wrong with apps: imitations, hidden subscriptions, fake warnings, manipulated reviews. They have different mechanisms and one thing in common — they are all prevented at the same moment.

That moment is the store page, and it contains more information than people use. Not because the checks are difficult, but because the install button is more prominent than any of them.

B. Key concepts

Four checks, then two things that make them easier.

The developer name

Who published the app, shown under the title on the store page.

Why it matters to you: This is the single most useful field. A well-known app published by a developer you have never heard of is not that app.

The official website

Reaching the store page through a link on the developer’s own site, rather than by searching the store.

Why it matters to you: It removes the ambiguity entirely. If you know the company, going to their site and following their link cannot lead you to an imitation.

The listing itself

Description, screenshots, last update date, download count.

Why it matters to you: Awkward English in a listing from a large company, screenshots that do not match the described features, and a last update three years ago are all signals worth noticing.

Reviews, read rather than counted

The rating number tells you very little. The recent reviews tell you more.

Why it matters to you: The companion resource on manipulated ratings covers why the number is unreliable. Reading five recent one-star reviews is usually faster and more informative.

Permissions requested

What the app asks for, visible on the store page before installing on most platforms.

Why it matters to you: A calculator requesting contacts is a decision you can make before the app is on your phone rather than afterwards.

Where you started

Did you go looking for this app, or did something suggest it?

Why it matters to you: The same question as in the download resource, and it does the same work here.

C. A practical example: two listings

You search the store for a well-known banking or utility app. Two results look similar.

The real one

• Developer name matches the company.
• Millions of downloads, updated within the last few weeks.
• Screenshots match what the app actually does.
• Reviews span years.

The imitation

• Developer name is a variation, or an individual’s name.
• A few thousand downloads and reviews all from the last month.
• Screenshots taken from the real app.
• Requests permissions the real one does not.

The second is not hard to spot once you look. The difficulty is that nothing prompts you to look, and both are one tap from installed.

D. Try it yourself: the thirty-second check

Practise it once on an app you already have, so it is familiar when it matters.

Step 1 — Open the store page of an app you use

• Read the developer name. Does it match the company you expect?
• Check the last update date.

Step 2 — Find the same app from the company’s website

• Go to their site and look for the app link.
• Confirm it leads to the listing you were looking at.

Step 3 — Read five recent reviews

• Not the rating. The reviews, sorted by most recent.
• Complaints about charges, about the app changing, or about support are the useful ones.

Step 4 — Look at the permissions before installing

• Ask whether each one matches what the app is for.
• The companion resource on permissions covers what to do afterwards.

Step 2 is the one worth making a habit. It takes longer than searching the store and removes an entire category of mistake.

E. Videos, articles and further resources

Independent and institutional sources in English.

Google — Use Play Protect to keep your apps safe and your data private
How the store checks apps and what you can see about a listing before installing. Platform documentation.
https://support.google.com/android/answer/2812853?hl=en

FTC — Malware: how to protect against, detect and remove it
What tends to arrive with an app that is not what it claims.
https://consumer.ftc.gov/articles/malware-how-protect-against-detect-and-remove-it

NCSC (UK) — Smart devices: using them safely in your home
What to change when a connected device arrives in the house, and what to check before buying one. Written for households rather than for network administrators.
https://www.ncsc.gov.uk/guidance/smart-devices-in-the-home

FTC — How to protect your phone from hackers
Practical steps for the device that holds most of your digital life.
https://consumer.ftc.gov/articles/how-protect-your-phone-hackers

NCSC (UK) — Cyber security advice for you and your family
The UK national authority’s advice hub for individuals: short, practical guidance written for people who are not IT professionals.
https://www.ncsc.gov.uk/section/advice-guidance/you-your-family

CISA — Secure Our World
The US cyber security agency’s public programme: four basic actions, explained for people who are not IT professionals.
https://www.cisa.gov/secure-our-world

Links checked in August 2026.

F. The Cyber Welfare Framework: Skills, Awareness, Secure Behavior

This lesson sits on the Skills pillar at level FL2 and is the foundation for the rest of this cluster.

Skills

• Reading a store listing critically: developer, dates, screenshots, reviews.
• Reaching an app through the developer’s own website.
• Judging requested permissions before installing.

For professionals and organizations

• Providing an approved list, so the judgement is made once rather than by each person.

Awareness

• Understanding that the store page contains more information than people use.
• Recognising that the download count and rating are the least reliable fields.
• Knowing that imitations are common enough to check for routinely.

For future instructors and ambassadors

• Demonstrating with a real search. The imitations are usually visible on the first screen.

Secure Behavior

• Checking the developer name every time.
• Installing from the company’s own link where one exists.
• Reading recent reviews rather than the average.

For organizations

• Restricting installation sources on managed devices.

G. Questions to sit with

1. When you last installed an app, did you read who published it?
2. Do you reach apps by searching the store, or from the company’s website?
3. Have you ever read the recent reviews of an app rather than the rating?
4. Would you recognise an imitation of an app you use daily?

H. What to do now

The recommendations (R) and security measures (MS) that apply before installing.

Before installing

• R17 — Install only from sources you sought out, never from a prompt or a link you received.
• R9 — Reach the developer’s site over HTTPS and follow their link.
• MS7 — Review the permissions requested before granting them.

Afterwards

• R6 — Keep apps updated, which official stores handle automatically.
• MS2 — If an app asks for credentials and your password manager does not recognise it, stop.

In short

• The developer name is the most useful field on the page.
• Following the company’s own link removes the ambiguity entirely.
• Read recent reviews; ignore the average.
• Check permissions before installing rather than after.

Related resources in this course

What this check prevents:

• Recognize and Avoid Fake and Imitation Security Apps
• Navigating Fake Ratings and Deceptive Apps on Stores
• Download Security: Deciding Before You Install

Discover more companion resources from the online courses of the Protect Your Digital Privacy programme.