Is it possible to have a custom dialog message when asking for notification permissions?

Question

I would like to customize the following part of the notification permission prompt:

Notifications may include alerts, sounds, and icon ba

Answer 1

No, I'm fairly certain that that part of the message is out of your control.

Answer 2

No, this is system message, you can't change to custom.

Answer 3

I do not believe you can change the iOS prompt, but should maybe make your own. See the guidelines that Apple has provided:

https://developer.apple.com/ios/human-interface-guidelines/interaction/requesting-permission/

Not the best resource because it does state that you can change the subtext (this is specifically for location, photos, etc.) but this, and others, have some good practices:

https://blog.clevertap.com/asking-for-ios-push-notification-permissions/

Basically, you should make your own prompt. Be sure to handle the cases where they have either said no, or turned it off in settings and redirect the user to settings, if so.

Answer 4

You are not able to customize this message. Read Here for more information.

The recommended way that most apps handle this is by first presenting their own dialog, then show the Apple system dialog.

So when it comes time to ask the user for notification permissions, first you trigger your own custom alert that says something like "Please allow your-app-name to send you notifications..." and maybe a brief description of why the user should allow this. With this alert, only add one action to the UIAlertController, I usually just have the action title set to "Ok" and use .default as the style. In the completion handler of this "Ok" UIAlertAction that is when you will trigger the Apple system dialogue which presents the generic UIAlertController with the option for the user to either accept or deny permissions for your app to send notifications.

So the flow is something like -> users reaches point in app where they have to decide if they want to accept or deny notifications permissions -> app presents UIAlertController that is essentially just an explanation of why the app wants/needs to send notifications -> once user taps "Ok" then trigger the generic system alert that actually makes the user choose to accept or deny notification permission.

There seems to be some psychological advantage to doing it this way. By sort of forcing the user to tap "ok" to notifications in the first dialogue, it primes them to tap "allow notifications" in the generic Apple dialogue displayed immediately after.