Specifically, I think anything done with NotificationCompat can be done using the default API (level 8). What am I missing here? What does NotificationCompat introduce that cannot be done using 2.2 API?
Source: http://developer.android.com/sdk/compatibility-library.html#Notes
NotificationCompat.Style. An object that can apply a rich notification style to a Notification.
NotificationCompat.Action. Structure to encapsulate a named action that can be shown as part of this notification.
To make this possible, Android N uses the existing NotificationCompat. Builder. setGroup() method. Users can expand each of the notifications, and perform actions such as reply and dismiss on each of the notifications, individually from the notification shade.
Builder class for NotificationCompat objects. Allows easier control over all the flags, as well as help constructing the typical notification layouts. On platform versions that don't offer expanded notifications, methods that depend on expanded notifications have no effect.
You can use things like NotificationCompat.Builder#setLargeIcon(Bitmap) to allow you to take full advantage of Android 3.0+ with things like the large icon, while maintaining compatibility on versions of Android prior to 3.0 that do not support such things.
Though its old question, now NotificationCompat can also be used to create wearable specific notifications. More information on this google's developer guide.
http://developer.android.com/training/wearables/notifications/creating.html
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With