1

I'm writing guidelines for drafting notifications. Is there a hard numeric limit on how many characters can be in a notification?

I'm especially interested in compatibility with older iOS versions: Which limit should writers respect to ensure compatibility with iOS 9?

Another point of interest: Notifications can have a title. Is the title backwards compatible to older iOS versions as well?

Finally, is there data on what length of notifications people engage best with?

1 Answer 1

3

According to the documentation, the character limit is around 4000 (4kB minus some other things in the payload, such as the device token).[1] However, not all 4000 characters will be shown to the user; it will depend on whether the notification is shown as an alert or banner, and if it's shown in the notification center, on the lock screen or when the iPhone is actively used. There are two things that help:

  • Keep your message as short as possible, and invite users to open the app if they need to read more.
  • Test your messages and see how they are truncated in various situations. Sometimes, the intention of the message is almost completely lost; sometimes, it will only be a very minor annoyance.

The title key in the APNS payload was introduced in iOS 8.2, according to table 9.2 in the documentation. So you should be safe if you're aiming for iOS 9.0 and up.

You should note that iOS 10 introduced Rich Notifications, which enables all kinds of formatting, images and videos to be shown when the user interacts with your notification (even when not actually opening the application).

[1]: if you're using a legacy library to send push notifications, the limit is half of that, so around 2000 characters.

1
  • I don't have any reference for the last part of your question. It probably depends on the purpose of the message. E.g. I only read most of CNN's breaking news notifications, I won't open the app. If I receive an image via WhatsApp, I probably will open the app.
    – Glorfindel
    Sep 1, 2017 at 9:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.