Confirmed users
385
edits
Features/Services/Notifications: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature open issues and risks=* | |Feature open issues and risks=* Product Decisions Needed | ||
* | * who is first real consumer? | ||
** AITC has expressed interest, B2G has expressed interest | |||
* | |||
* | |||
* B2g question: are they adopting it? is an addon feasible? | * B2g question: are they adopting it? is an addon feasible? | ||
* Desktop client - is an addon really a good idea? | |||
* Desktop - is an addon really a good idea? | * Android client - is an addon a good idea? | ||
* Android - is an addon a good idea? | * [strawman] Definition of Success (one was not set) | ||
* Definition of Success (one was not set) | |||
** Someone out side of mozilla consumes it by EOY | ** Someone out side of mozilla consumes it by EOY | ||
*** bonus points for a major social web property (fb, twitter, etc) a year after release | *** bonus points for a major social web property (fb, twitter, etc) a year after release | ||
** 1000 msg/day by EOY | ** 1000 msg/day by EOY | ||
|Feature overview=Notifications are a way for websites to send small messages to users when the user is not on the site. iOS and Android devices already support their own push notification services, but we want to make a better notifications system available to the whole web. | * Implementation Needs | ||
** needs privacy review | |||
** needs security review | |||
*** is pending for crypto | |||
** needs ops review | |||
*** petef is involved | |||
*** estimate: initial load ~100 msgs/day | |||
** hardware for production has not been ordered? | |||
** deployment timeline is in question | |||
* Process Needs | |||
** needs a Product Marketing Manager and/or Business Development Owner | |||
|Feature overview=Notifications are a way for websites to send small messages to users when the user is not on the site. iOS and Android devices already support their own push notification services, but we want to make a better notifications system available to the whole web. | |||
|Feature users and use cases=*''Email Notice'' - | |Feature users and use cases=*''Email Notice'' - | ||
A webapp provider wishes to communicate with their audience. The provider has a set of user tokens for their customers. They then send messages to token@mozillamessaging.com (domain tbd). Notifications parses the message, wraps the message in a useful wrapper, and then relays the message to the registered user address, thus providing the user the ability to quiet noisy providers, drop compromised addresses and otherwise manage their message delivery. | A webapp provider wishes to communicate with their audience. The provider has a set of user tokens for their customers. They then send messages to token@mozillamessaging.com (domain tbd). Notifications parses the message, wraps the message in a useful wrapper, and then relays the message to the registered user address, thus providing the user the ability to quiet noisy providers, drop compromised addresses and otherwise manage their message delivery. | ||
| Line 54: | Line 58: | ||
A user no longer wishes to receive alerts for a given notification. The user | A user no longer wishes to receive alerts for a given notification. The user | ||
loads their admin and control panel and disables the queue. The user can either temporarily silence a given notification queue (in which case, notifications are still collected, but not immediately alerted to the user) or delete the queue (in which case, incoming notifications are rejected, existing notifications are removed, and the queue is no longer associated with the user.) | loads their admin and control panel and disables the queue. The user can either temporarily silence a given notification queue (in which case, notifications are still collected, but not immediately alerted to the user) or delete the queue (in which case, incoming notifications are rejected, existing notifications are removed, and the queue is no longer associated with the user.) | ||
|Feature dependencies=* Clients | |Feature dependencies=* Clients | ||
** This product page only covers the backend system. | ** This product page only covers the backend system. | ||
| Line 62: | Line 64: | ||
* Android - addon? | * Android - addon? | ||
* Services Ops - deployment | * Services Ops - deployment | ||
|Feature requirements=* Transparency: Process MUST be transparent to user. For example, other than clicking "Yes" or "No" to a dialog of the web app requesting to send notifications, the user should not be aware of the underlying mechanics of the process. | |Feature requirements=* Transparency: Process MUST be transparent to user. For example, other than clicking "Yes" or "No" to a dialog of the web app requesting to send notifications, the user should not be aware of the underlying mechanics of the process. | ||
| Line 72: | Line 73: | ||
* Control: The user should be able to disable or delete any created notification channel. Upon deletion, the user should not see any additional messages sent to that channel. The sender should be notified that messages to that channel are no longer being accepted. | * Control: The user should be able to disable or delete any created notification channel. Upon deletion, the user should not see any additional messages sent to that channel. The sender should be notified that messages to that channel are no longer being accepted. | ||
|Feature non-goals=* Not an identity solution | |Feature non-goals=* Not an identity solution | ||
* Not an instant message replacement system | * Not an instant message replacement system | ||
| Line 79: | Line 79: | ||
|Feature ux design=* Without firm commitment from clients, there are no official UX specs. | |Feature ux design=* Without firm commitment from clients, there are no official UX specs. | ||
** Jeff's addon has ux from a community member | ** Jeff's addon has ux from a community member | ||
|Feature implementation plan=see github | |Feature implementation plan=see github | ||
|Feature security review=security review: ? | |Feature security review=security review: ? | ||