Clever Geek Handbook

Best practice to disable app notification

I am developing an application that uses Notification a lot, and I expect users to be "annoyed" with too many notifications.

So I decided to add an option in the app settings to stop receiving the notification, either by selecting a user using the server, or the app will only notify it as unregisetr:

[[UIApplication sharedApplication] unregisterForRemoteNotifications];

However, I noticed that the iPhone settings already have options to turn off notification for each app.

Hence, I am wondering if it is good and common practice to duplicate this option in the application settings, or it is assumed that the user is familiar with the option to turn off the notification in the iphone settings.

I noticed, for example, the "WhatsApp" application has the ability to turn off the notification in the application itself.

+3


source to share


2 answers


Here are some tips based on my experience. Of course, this requires server side settings:

  • Allow the user to choose which notification he wants to receive. You may have different notifications, some may interest users and some others less.

  • There is no good guide on how to enable / disable notifications on iOS (for new users buying iDevice). So don't expect him to know exactly how to turn them off. Some users even uninstall your app to get rid of notifications. And don't expect a tutorial to turn them off to have a big impact.

  • You have a "sleep" mode where the user is not notified during the day. However, iOS6, the user can do it himself with the device setup, so I really don't recommend that you implement it :-) But before it was "nice to have".



But be strong with your users. Notifications can be an important part of your application / business. Therefore, do not allow too much "tuning".

+1


source


I think that no good practice or common practice duplicates the standard notification settings in the native app settings. For example, when you go to the notifications section of the Settings app, turn on notifications for your app, it would be wise for the user to assume they will receive notifications. They also don't need to forget that you also visit your app settings.

If you absolutely need a UI to clarify what notifications a user receives, great, suggest that in your app's own settings. But otherwise I would advise to do it. And even then, I would ask if your application really needs that level of control. Rich and fine-grained settings for an app tend to make the app less graceful and less intuitive. Sometimes you really need this control (in this case, do it), but the most elegant apps tend to have minimalistic interfaces.



Many of us are software engineers, but we cannot let the "internal engineer" in us stray too far from UX. We need to put on our digital creative hats and think about how to make this sublime user experience. Often less.

By the way, if you are worried that the user objects to too many notifications, you will almost certainly have too many notifications. See what notifications you have and ask if they are really worthy of interrupting a user doing something else.
+1


source






More articles:


All Articles