Design a Mobile Kill Switch That Survives Backgrounding and Lost Networks

Short summary

Proposes a three-state mobile kill-switch model (pending, acknowledged, confirmed) that honestly handles backgrounding, lost connectivity, and app termination. The UI must never show success when only local intent is recorded, and server-side lease expiry and admission denial are necessary companions since a disconnected handset cannot confirm remote revocation. Includes a proposed test envelope covering device lifecycle, network conditions, and accessibility requirements.

• •Three-part truth model: local intent recorded, server receipt received, revocation confirmed
• •UI must show uncertain state when offline; never promise background delivery will succeed
• •Server-side lease expiry and admission denial required since offline handsets cannot confirm remote shutdown

Generated with AI, which can make mistakes.