CloudServices/Notifications

Info

What is "Notifications"?

Notifications is designed to allow brief messages to be sent to a user however they are connected. Somewhere between email and IM lies Notifications.

Notifications are built around a pseudonymous, 256bit+ entropy, public identifier. Sites post messages using that identifier to one of several methods. (URL, Email, etc.) Notifications may be human readable, or opaque, machine readable content. The user has full control over whether or not to receive notifications from a party, allowing for "chatty" or compromised IDs to be disabled or removed.

Goals

• Q1
  • BIPOSTAL in staging supporting Apps/ID?
    • Production Dependant on Q1 blockers:
      • HW availability
      • Coordination with external mail partner
      • Coordination with BrowserID Team
      • Coordination with WebApps re: requirements
      • UX for client dashboard?
    • PUSH: product defined and on track for Q2 launch

• Q2
  • Integration of BIPostal and PUSH to unified Notifications structure
  • Finalization of Notification SLAs
  • Finalization of metrics and logging info
  • BIPostal to production
  • Shift notification token (ntoken) mapping from mysql to MySQL -> Queuey
  • Notifications to Nightly, Fennec, iOS, Android
  • Dependent on:
    • Mobile Team adoption of code
    • Coordination with WebApps on availability

• Q3
  • Full Production ready release of Notifications
  • Documentation and demonstration code
  • Customer support in place
  • Additional demand/work from Q2 integration work (e.g. new demands)

• Q4
  • Unknown at this time.

v.1

Older Notifications work

v.2

Push

Bipostal