Details
-
Type:
New Feature
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.1 Final
-
Fix Version/s: BridgeIt 1.0
-
Component/s: Containers, Faces, Spring
-
Labels:None
-
Environment:ICEmobile
Description
User notifications including status bar, sounds and vibrations should be supported in the containers, and made available through JSP and JSF tags.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Moving to 1.4.
The HTML5 JS API's need to be defined for this, and then native capabilities must be developed to support it.
Android notifications are described at http://developer.android.com/design/patterns/notifications.html. The Notification.Builder (http://developer.android.com/reference/android/app/Notification.Builder.html) supports the following options that can be applied to a notification.
Basics
- title
- text
- subtext
- small icon (used in status bar)
- large icon (used in expanded drawer view)
- ticker (displayed when notification first arrives)
- priority
- when
Advanced
- lights (flashing LED)
- sound
- vibration
- chronometer (time elapsed since notification)
- number (count something: like number of new emails)
Behaviour
- OnlyAlertOnce (sound, vibrate, ticker only when notification is not showing)
- Ongoing (user cannot dismiss)
- AutoCancel (automatically dismisses when user touches)
Apple iOS capabilities are fairly different from Android:
The main common features are already supported: subject and detail. APNS does allow a sound to be specified, however that sound must be included in the application (unlike GCM which allows a sound URL). Additionally, the "number" can be specified as an APNS "badge", however, ICEmobile-SX/BridgeIt can be used by multiple different web applications, so the badge would be ambiguous.
APNS supports notification metadata, so even though, say a vibration mode cannot be specified in the API, it may be possible to define a custom metadata attribute for vibration and implement this directly in the iOS client. However, the metadata would likely not be available until the user viewed the notification, resulting in the vibration occurring too late.
The tag has not been implemented, but Cloud Push features support notification on the home screen. (A new JIRA can be created for the tag if the feature is determined necessary.)
The basic question here is, where are the notification options configured? Should it be driven from the server-side application, or a user preference at the container?