Ios Non Dismissable Modal
Presenting a sheet or full-screen modal with no cancel button and swipe-to-dismiss disabled, trapping the user until they complete a forced step.
$ aoe install @community/anti-pattern-ios-non-dismissable-modalProjection
Always in _index.xml · the agent never has to ask for this.
IosNonDismissableModal [anti-pattern] v1.0.0
Presenting a sheet or full-screen modal with no cancel button and swipe-to-dismiss disabled, trapping the user until they complete a forced step.
Loaded when retrieval picks the atom as adjacent / supporting.
IosNonDismissableModal [anti-pattern] v1.0.0
Presenting a sheet or full-screen modal with no cancel button and swipe-to-dismiss disabled, trapping the user until they complete a forced step.
Label
iOS Non-Dismissable Modal (Trapped User)
Meta
- License: MIT AND Apache-2.0
- License Provenance: legacy-backfill
Why Bad
Users feel trapped and cannot exit to other app features or use the back button. There is always an interruption scenario (phone call, wrong tap) where the user needs to abandon the flow. iOS sheet dismissal is expected behavior and disabling it without a Cancel button violates the HIG — Apple HIG Rule 8.4 and Anti-Pattern #11.
Instead Do
Always provide at least one dismiss path: a Cancel/Close button in the toolbar, or preserve the default swipe-to-dismiss behavior on sheets (.presentationDetents). If the task requires confirmation before exit, present a .confirmationDialog asking 'Discard changes?' rather than blocking dismiss entirely.
Loaded when retrieval picks the atom as a focal / direct hit.
IosNonDismissableModal [anti-pattern] v1.0.0
Presenting a sheet or full-screen modal with no cancel button and swipe-to-dismiss disabled, trapping the user until they complete a forced step.
Label
iOS Non-Dismissable Modal (Trapped User)
Meta
- License: MIT AND Apache-2.0
- License Provenance: legacy-backfill
Why Bad
Users feel trapped and cannot exit to other app features or use the back button. There is always an interruption scenario (phone call, wrong tap) where the user needs to abandon the flow. iOS sheet dismissal is expected behavior and disabling it without a Cancel button violates the HIG — Apple HIG Rule 8.4 and Anti-Pattern #11.
Instead Do
Always provide at least one dismiss path: a Cancel/Close button in the toolbar, or preserve the default swipe-to-dismiss behavior on sheets (.presentationDetents). If the task requires confirmation before exit, present a .confirmationDialog asking 'Discard changes?' rather than blocking dismiss entirely.
Relations
related: [@community/anti-pattern-ios-stacked-modals, @community/pattern-ios-sheet-presentation, @community/rule-ios-alerts-critical-only]
Label
iOS Non-Dismissable Modal (Trapped User)
Meta
- License: MIT AND Apache-2.0
- License Provenance: legacy-backfill
Why Bad
Users feel trapped and cannot exit to other app features or use the back button. There is always an interruption scenario (phone call, wrong tap) where the user needs to abandon the flow. iOS sheet dismissal is expected behavior and disabling it without a Cancel button violates the HIG — Apple HIG Rule 8.4 and Anti-Pattern #11.
Instead Do
Always provide at least one dismiss path: a Cancel/Close button in the toolbar, or preserve the default swipe-to-dismiss behavior on sheets (.presentationDetents). If the task requires confirmation before exit, present a .confirmationDialog asking 'Discard changes?' rather than blocking dismiss entirely.
Source
aoe-engine/examples/frontend-design/primes/compiled/@community/anti-pattern-ios-non-dismissable-modal/atom.yaml