3 ms·
In the example of Apple Calendar, creation is arguably the "dangerous" event even if it's not destructive, so one might argue that what Apple is currently doing
by threatofrain 3y ago
In the example of Apple Calendar, creation is arguably the "dangerous" event even if it's not destructive, so one might argue that what Apple is currently doing on Apple Calendar (cancel destroys the event) is compliant with the spirit of their HIG. I'd use the same argument of creation-is-dangerous for the alarm app, which also has a non-scary cancel button that destroys the input.
Then we go to something like Apple Notes where even the slightest bit of data is auto-saved without asking.
- isodev 3y agoI don't follow. Apple Calendar shows a sheet to create a new event. The sheet has a primary action (Add) and a discard action (Cancel). If you hit Cancel after adding some data, you get an action sheet "Are you sure you want to discard this new event?" with the options to "Discard Changes" and "Keep editing" The primary and secondary actions on a sheet are not the same (different modality and context) as the options on a modal action sheet (where we usually have to confirm or discard).
- deleted 3y ago[deleted]
- threatofrain 3y agoOops, you're right, I just didn't change any data. However, on Apple Calendar for MacOS, using ⌘-n and dismissing the prompt will destroy your data. The same is true for alarms on iOS.