Details
-
Type: New Feature
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: 4.0.BETA
-
Fix Version/s: None
-
Component/s: Push Library
-
Labels:None
-
Environment:ICEpush, Cloud Push, mobile
Description
Both Android and iOS (8) support Actionable notifications. Actions potentially include buttons or a text field for direct interaction with the notification.
Activity
Ted Goddard
created issue -
Ted Goddard
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Ted Goddard [ ted.goddard ] |
Android and iOS Actionable Notifications are customized in different ways. In the case of iOS, the ability to include a text field is not yet documented and the the button actions must be defined on the notification category during startup (so it is safe to assume that the presence
of a text field must also be defined during startup).
Since BridgeIt is general-purpose, this means that we must a set of actionable notification categories that are useful for a variety of applications. The category is set as an attribute on the PushConfiguration. For instance:
default : message, no buttons
AcceptDecline : message, Accept, Decline buttons
TextFieldOK : message and text field with an OK button
The BridgeIt JavaScript callback will be invoked with the category name in "category", the button text in the "button" value, and any input text in "input".
Some other options for actionable buttons are "maybe", "snooze", "dismiss", "later" since it is common to use notifications for reminders. Another potential feature is for a push notification to result in a recurrent notification on the device (as a reminder).