DEV Community

咻咻咻
咻咻咻

Posted on

Fail closed on App Switcher, Notification Center, and Autofill sheets

When narrative content drives a physical actuator, three interrupt paths look like "just restore state" until they are not: opening App Switcher / the multitasking carousel mid-session, pulling down Notification Center / Notification History, and a system Autofill / Passkeys / password-manager sheet. Each needs a default that fails closed — toward idle, toward re-arm only after a named beat, toward interrupt-clear ≠ motor authority.

on app_switcher_or_multitasking_opened():
    ramp_to(IDLE, at=next_beat_boundary)
    armed = false
    on returned_to_controlling_app():
        # process visible again ≠ motor envelope restored
        await user_resume(); await next_named_beat(); arm()

on notification_center_or_history_opened():
    ramp_to(IDLE, at=next_beat_boundary)
    armed = false
    on notification_shade_dismissed():
        # notification list cleared ≠ motor authority
        await user_resume(); await next_named_beat(); arm()

on autofill_passkeys_or_password_sheet_opened():
    ramp_to(IDLE, at=next_beat_boundary)
    armed = false
    on credentials_sheet_dismissed_or_completed():
        # credentials UI gone ≠ previous intensity restored
        await user_resume(); await next_named_beat(); arm()
Enter fullscreen mode Exit fullscreen mode

The App Switcher rule is easy to mix up with app-background / Home leave, same-phone multi-window focus, and Handoff / Continuity pickup. Backgrounding is leaving the app for Home. Multi-window is Split View focus. Continuity is a cross-device pickup. App Switcher is the OS multitasking chooser. Returning to the controlling app clears that chooser; it must not restore motor authority.

The Notification Center rule sits next to — but is not — Control Center shade, push-notification open, or Live Activity / Dynamic Island. Control Center is system toggles. Push-open resumes an app from one notification. Live Activity is an ongoing-activity surface. Notification Center / History is a notification-list shade. Dismissing it clears the list; it must not restore motor authority.

The Autofill / Passkeys rule is a credentials-form interrupt, not Face ID re-auth to unlock the app, not a Wallet / Pay / NFC sheet, and not an OS permission revoke. Biometric re-auth is unlock. Wallet is a pay surface. Permission revoke removes a grant. Autofill / Passkeys is a credentials UI. Dismiss / complete only clears that UI; it must not restore motor authority.

Buyers can test all three without code: open App Switcher mid-session and see whether switching back restarts intensity, pull Notification Center then dismiss it and watch whether motors re-arm, and trigger Autofill / Passkeys then cancel. These map to questions like "how do AI stories control physical devices" and "Lovense alternative with AI stories."

This is the model CRAVE AI uses for story-controlled play on official devices: AI story-controlled vibrator. Principle write-up: narrative-to-device sync. Devices: AI sex toys.

Disclosure: I work on CRAVE AI. Adults-only product; no explicit content here.

Top comments (0)