FitShield on Android.

How the native app blocks websites

The native app uses Android's VpnService as a local, on-device connection filter. When a connection opens, the device already names its destination in the clear — the TLS SNI of an HTTPS connection, or the Host header of a plain HTTP request. FitShield checks that hostname against the engine-derived rules and resets blocked connections. Everything else is relayed untouched to the destination the device chose.

How the native app blocks food apps

App blocking is a separate, opt-in layer for native apps. An accessibility service you enable yourself reads only the foreground app's package name — never screen or message content. When a blocked delivery or fast-food app opens, FitShield shows a native pause screen: a reflection timer, category-aware recipe suggestions, and localized buttons. It is additive to the connection filter, never a replacement. An optional keep-alive service exists for phones that aggressively freeze idle apps; like every extra, it is opt-in and off by default.

One engine, one dataset

Android has no blocklist of its own. Its rules are generated from the same canonical blocklists through the shared engine, and an audit fails the build if the generated rules ever drift from that data — so the app and the extension can never disagree about what is blocked. The app-to-brand package list is generated and validated the same way. Browse the data behind it: delivery services, the fast-food directory, and categories.

Status: preview, APK on GitHub Releases

The native app is preview-quality. It has been built and verified on-device (Samsung, Android 14), and the latest GitHub Release ships a downloadable preview APK — but it is not on the Play Store yet and still needs backend refinement. IPv6 is currently dropped to force IPv4. Treat it as a preview, not a finished release.

1. Download the preview APK from FitShield's GitHub Releases.
2. Install it on your device, enable protection, and approve the one-time VPN consent dialog.
3. Prefer to build it yourself? Follow the Android guide (docs/ANDROID.md) to build from source with the Android SDK and Gradle.

Prefer the browser? FitShield installs in one click on desktop — see browser support.

Android FAQ

Is the FitShield Android app on Google Play?

Not yet. The native Android app is a preview: you can download the preview APK from FitShield's GitHub Releases page and install it yourself, but a Play Store release needs more backend refinement first.

Is the FitShield Android app a VPN?

It uses Android's VpnService, but only as a local, on-device connection filter. No traffic is tunnelled to any server, nothing is decrypted, and it provides no anonymity. It only checks each connection's destination hostname against your blocklist and resets blocked ones.

Does FitShield on Android filter DNS?

No, never. FitShield reads the destination hostname the device already sends in the clear when a connection opens — the TLS SNI or the HTTP Host header. DNS is never intercepted, altered, or logged, so FitShield works alongside strict Private DNS or NextDNS.

Why is there no block page for websites on Android?

Showing a custom page inside an HTTPS connection would require decrypting your traffic, which FitShield refuses to do. Blocked sites simply fail to connect. Blocked apps do get a native pause screen, because no decryption is needed there.

Does the Android app block other apps?

Optionally. An opt-in accessibility service reads only the name of the app in the foreground — never screen or message content. When a blocked delivery or fast-food app opens, it shows a pause screen with a reflection timer and recipe ideas. It is additive to the website filter, never a replacement.

Does the extension work on Firefox for Android?

Yes. Firefox for Android 142+ can install the same extension from the Firefox Add-ons listing. On-device blocking has not been fully verified yet, so treat it as early.