chadpav
commented
9 years ago Example documentation from another platform: Customizing your Notifications
If you want to send more than just a message, you will need to use an NSDictionary to package all of the data. There are some reserved fields that have a special meaning.
- alert: the notification's message.
- badge: (iOS only) the value indicated in the top right corner of the app icon. This can be set to a value or to Increment in order to increment the current value by 1.
- sound: (iOS only) the name of a sound file in the application bundle.
- content-available: (iOS only) If you are a writing a Newsstand app, or an app using the Remote Notification Background Mode introduced in iOS7 (a.k.a. "Background Push"), set this value to 1 to trigger a background download.
- category: (iOS only) the identifier of the UIUserNotificationCategory for this push notification.
- uri: (Android only) an optional field that contains a URI. When the notification is opened, an Activity associated with opening the URI is launched.
- title: (Android, Windows 8, and Windows Phone 8 only) the value displayed in the Android system tray or Windows toast notification.
We currently send push notifications through the CBPush class. There are apple specific implementation details in this class and a consumer of the class has to have internal knowledge of it's implementation to get it to work (e.g. the "aps" attributes).
I'd like the CBPush class to support strongly typed properties for standard notification features like "message" and "sound". In some cases maybe a feature is only supported by Apple or Android but this could be clearly documented in the header documentation for that property.