DEV Community

Show Prove
Show Prove

Posted on

Why I Now Check App Permissions Before Installing Anything on Android

A few months ago I started doing something simple: before installing an app, I scroll down to its permissions list. It changed how I pick apps.

Promises vs. constraints

Most apps ask you to trust a privacy policy. But a policy is just a promise. An app that never requests the INTERNET permission can't send your files anywhere, no matter what the developer wants. That's privacy enforced by the system, not by goodwill.

What I look for

No network access for tools that don't need it (PDF editors, notes, scanners, calculators)
Scoped storage instead of full file access
No background location unless the app is literally a map
Open source code when possible, so others can verify claims

Testing it on a real device

I've been testing this on my Google Pixel 6 Pro. Pixels get Android updates early, so the newer permission controls (one-time permissions, the privacy dashboard, auto-reset for unused apps) show up there first. The privacy dashboard alone was eye-opening: a flashlight app I'd forgotten about had checked my location dozens of times.

Quick checklist for developers

Request only what the feature actually needs.
Ask at the moment of use, not at launch.
If the app works offline, drop INTERNET entirely and say so. It's a selling point.

Takeaway

Permissions are the most honest description of an app. Read them before you read the marketing.

Top comments (0)