Public capability record

Compatibility & capability status

DistractionKiller does not currently offer a production-ready system-level blocker. This page separates the available web surface from experimental native work and records the permissions, bypass risks, test evidence, and limits needed before release.

Release gate: the first native platform is still awaiting an explicit choice and repeatable physical-device proof. Paid checkout and public store claims remain closed.

Platform matrix

Web

Available

Current capability: Public capability status, safety education, and beta registration.
Required permission / policy: No device-level app permission is requested.
Known or untested bypasses: A browser page cannot enforce system-level blocking.
Last physical test: Public web build verification; no enforcement claim.
Limits: No app or website blocking. No paid checkout.

Android

Prototype — not certified

Current capability: Candidate first platform; native enforcement loop is still under physical-device proof.
Required permission / policy: Candidate design uses an explicit, revocable Accessibility grant plus a humane interruption surface. It reads package-change events without screen content and does not request Usage Access or overlay permission. Final Play declaration and device certification are pending.
Known or untested bypasses: Permission revocation, force-stop, reboot, battery optimization, OEM task killers, clock changes, and safe emergency unlock remain unverified.
Last physical test: No repeatable physical-device enforcement test recorded as of 1 August 2026.
Limits: Not published to Google Play. Do not rely on it to block critical or safety-related apps.

iOS

Not available

Current capability: No public iOS blocker exists.
Required permission / policy: Family Controls / Managed Settings entitlement has not been confirmed.
Known or untested bypasses: Screen Time changes, entitlement denial, device reboot, and emergency unlock have not been tested.
Last physical test: No physical-device enforcement test recorded.
Limits: No App Store listing and no enforcement promise.

macOS / Windows / extensions

Not in the first proof cycle

Current capability: No desktop agent or browser extension is offered.
Required permission / policy: Not applicable until a platform and policy mechanism are selected.
Known or untested bypasses: Not assessed.
Last physical test: No implementation or device test recorded.
Limits: Roadmap only; not a current feature.

Safety before strictness

Emergency unlock must remain accessible and shame-free.
Phone, system, authenticator, health, transport, and emergency apps must be protected by a non-blockable allowlist.
A revoked permission must produce a visible unhealthy state, never a false protected message.
Catastrophic lockout tolerance is zero.

Privacy boundary

Selected app and URL history is intended to remain local to the device.
No clinical, ADHD-treatment, or guaranteed screen-time reduction claim is made.
Any beta telemetry must be limited to permission health and anonymous enforcement outcomes.
The event contract must be reviewed before a closed beta begins.

Interested in the physical-device beta?

Join the waitlist for platform-selection and closed-beta updates. Registration is not a promise of compatibility or store availability.

View beta registration

Platform matrix

Web

Available

Current capability: Public capability status, safety education, and beta registration.
Required permission / policy: No device-level app permission is requested.
Known or untested bypasses: A browser page cannot enforce system-level blocking.
Last physical test: Public web build verification; no enforcement claim.
Limits: No app or website blocking. No paid checkout.

Android

Prototype — not certified

Current capability: Candidate first platform; native enforcement loop is still under physical-device proof.
Required permission / policy: Candidate design uses an explicit, revocable Accessibility grant plus a humane interruption surface. It reads package-change events without screen content and does not request Usage Access or overlay permission. Final Play declaration and device certification are pending.
Known or untested bypasses: Permission revocation, force-stop, reboot, battery optimization, OEM task killers, clock changes, and safe emergency unlock remain unverified.
Last physical test: No repeatable physical-device enforcement test recorded as of 1 August 2026.
Limits: Not published to Google Play. Do not rely on it to block critical or safety-related apps.

iOS

Not available

Current capability: No public iOS blocker exists.
Required permission / policy: Family Controls / Managed Settings entitlement has not been confirmed.
Known or untested bypasses: Screen Time changes, entitlement denial, device reboot, and emergency unlock have not been tested.
Last physical test: No physical-device enforcement test recorded.
Limits: No App Store listing and no enforcement promise.

macOS / Windows / extensions

Not in the first proof cycle

Current capability: No desktop agent or browser extension is offered.
Required permission / policy: Not applicable until a platform and policy mechanism are selected.
Known or untested bypasses: Not assessed.
Last physical test: No implementation or device test recorded.
Limits: Roadmap only; not a current feature.

Safety before strictness

Emergency unlock must remain accessible and shame-free.

Phone, system, authenticator, health, transport, and emergency apps must be protected by a non-blockable allowlist.

A revoked permission must produce a visible unhealthy state, never a false protected message.

Catastrophic lockout tolerance is zero.

Privacy boundary

Selected app and URL history is intended to remain local to the device.

No clinical, ADHD-treatment, or guaranteed screen-time reduction claim is made.

Any beta telemetry must be limited to permission health and anonymous enforcement outcomes.

The event contract must be reviewed before a closed beta begins.