3 ms·

It seems to me that for the sake of user experience they should really, really try to automatically coalesce multiple system messages and notifications that app

It seems to me that for the sake of user experience they should really, really try to automatically coalesce multiple system messages and notifications that appear while others have not yet been dismissed. For example, automatically grow the first alert into a list with checkboxes or something if another alert shows up, so that the user can reply to all of them in a sane way.

dwaite 7y ago
The dialogs are meant to be presented in context so that the user understands _why_ they are being asked for a privacy-impacting decision. Applications rely on this so that they may ask for permission within context. E.g., a retail company app that asks to track location permissions on start will often get denied. That same app asking for location permissions when the user says 'find nearest stores' will have decent success. Promoting it up to a system-level coalesced set of notifications both eliminates the benefits of asking for permissions in contexts and the motivation to stop asking for permissions out of context. It also creates a problem in some apps where the prompt is modal, because the API is blocked until the question is answered.
- makecheck 7y ago
  Apple does require apps to provide context in a lot of cases, and the app’s provided reason appears alongside the message. There is nothing about a combined window that requires context to be lost. For example, add a column that includes trigger conditions and reasons for each one, e.g. “while launching startup item”, “when opening AppName”, “to authorize task performed by AppName”, “downloaded from xyz.com”, etc. If that information really isn’t enough, the user still has the option to deselect one and try it again in isolation. An API can be held in a modal state without requiring each app to have its own dialog; the system can decide what action allows the API to return to resume the app. Similarly, an app can fire off an async notification without caring if that notification window is separate from others. This is entirely a presentation issue.

dwaite 7y ago

The dialogs are meant to be presented in context so that the user understands _why_ they are being asked for a privacy-impacting decision. Applications rely on this so that they may ask for permission within context. E.g., a retail company app that asks to track location permissions on start will often get denied. That same app asking for location permissions when the user says 'find nearest stores' will have decent success. Promoting it up to a system-level coalesced set of notifications both eliminates the benefits of asking for permissions in contexts and the motivation to stop asking for permissions out of context. It also creates a problem in some apps where the prompt is modal, because the API is blocked until the question is answered.

makecheck 7y ago
Apple does require apps to provide context in a lot of cases, and the app’s provided reason appears alongside the message. There is nothing about a combined window that requires context to be lost. For example, add a column that includes trigger conditions and reasons for each one, e.g. “while launching startup item”, “when opening AppName”, “to authorize task performed by AppName”, “downloaded from xyz.com”, etc. If that information really isn’t enough, the user still has the option to deselect one and try it again in isolation. An API can be held in a modal state without requiring each app to have its own dialog; the system can decide what action allows the API to return to resume the app. Similarly, an app can fire off an async notification without caring if that notification window is separate from others. This is entirely a presentation issue.