UX Improvement part 2

Provide user notification support in SimplyE for iOS and Android regardless of vendor content provider limitations.

• As a user I want to get a notification when my reserved books are available for download. SIMPLY-192
• As a user I want to know when my borrowed ebooks are about to expire SIMPLY_193
• As a user I want to know when my reservation checkout grace period is to expire.  SIMPLY-194
• As a user I want to opt into notifications SIMPLY-195
• As a user I want to select / subscribe to certain notifications SIMPLY-196
• As a user I want to configure how my app notifies me. SIMPLY-197

• Vendor Notification Systems: Email push notifications from vendors can hijack the user or confuse them. Vendors push notifications from their systems through email. However, they do not provide subscription services for machine based API access to queued change events or notification queues which SimplyE can reliably integrate from vendor to vendor. These independent systems allow the vendor to manage the user experience by drawing users into their app through email notifications and potentially confusing the user.
• Security and Privacy: Vendors such as Overdrive require a users security credentials in order to access the their holds and loans. This creates a challenge for SimplyE in that storing such information is against is principle privacy and security design and is not consistent across vendors. Therefore, SimplyE client initiated queries against a patron distributor bookshelf. This requires SimplyE to use a client initiated notification strategy vs a server based push notification strategy.
• Polling Based Notifications
  Because the Circulation Manager is polling providers bookshelf only when prompted by the user, the mobile app can provide polling based notifications by asking the cric manager for an update of the users bookshelf on a regular basis. This server side strategy is due to the fact that the users ide and pin are required for access the service providers API in exchange for a temp token. Because SimplyE servers do not store a user’s service provider credentials, updates are user initiated from their client application. In other words, the users privacy and security is in their possession, not the libraries. While this may not allow Push based notifications it does enable near real time notifications based on the client's ability to initiate updates in the background while the user is “in” the app.