Native enforcement proof
A first platform must pass repeatable physical-device tests, including permission loss, reboot, bypass, and emergency-unlock cases.
Loading…
DistractionKiller is validating whether a future native enforcement loop can meet its safety gates. The public web surface documents focus planning, permissions, bypass risks, and beta progress.
Public capability record
Release status
Web
Status & beta registration
Android
Prototype — physical proof pending
iOS
Not available
No system-level blocking, store availability, or outcome guarantee is claimed until a repeatable physical-device test passes.
Release discipline
These are the product's current boundaries and proof gates, not a list of promised production features.
The web product documents current capability, permissions, bypasses, evidence, and release limits. It does not block apps.
The candidate native path still needs repeatable physical-device tests across permission revocation, force-stop, reboot, battery, and OEM cases.
Family Controls entitlement and enforcement behavior are unconfirmed. There is no App Store listing or iOS release promise.
A release must preserve an accessible emergency unlock and a non-blockable allowlist for critical system, health, transport, and authenticator apps.
Selected-app and URL history is intended to remain on-device. Any beta telemetry must be minimal, explicit, and limited to reliability evidence.
No paid plan is for sale while native enforcement, lifecycle handling, and provider configuration remain uncertified.
Path to beta
Choose the first platform only after confirming entitlement, policy, and distribution feasibility. Multi-platform availability is not assumed.
Run repeatable physical-device tests for permission revocation, force-stop, reboot, time changes, OEM behavior, emergency unlock, and critical-app exclusions.
Release only after evidence is recorded. Measure reliability and false-lockout risk without promising productivity or clinical outcomes.
Beta access
DistractionKiller is not selling blocking, coaching, timers, or outcome improvements while the core native capability remains unverified. Joining the waitlist is free and does not create a subscription.
A first platform must pass repeatable physical-device tests, including permission loss, reboot, bypass, and emergency-unlock cases.
Critical-app allowlisting, permission health, telemetry boundaries, entitlement, and store-policy fit must be documented.
Checkout, entitlement binding, cancellation, refund, restore, duplicate-event, and out-of-order lifecycle tests must pass before a price can be sold.
Register for platform-selection and physical-test updates. No card details are requested.
We are not collecting email addresses while consent and unsubscribe controls are being certified.
Check the capability status for source-backed release updates.
Transparent answers
Review the public capability record, then join the closed-beta waitlist if the current platform and safety limits fit your expectations.
No payment, platform guarantee, or outcome promise.