Features/Fennec/Android Snippets

Please use "Edit with form" above to edit this page.

Status

Cloud to Device Messaging
Stage	Draft
Status	In progress
Release target	`
Health	OK
Status note	`

{{#set:Feature name=Cloud to Device Messaging

|Feature stage=Draft |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=` }}

Team

Product manager	Jen Arguello
Directly Responsible Individual	`
Lead engineer	`
Security lead	`
Privacy lead	`
Localization lead	`
Accessibility lead	`
QA lead	`
UX lead	Madhava Enros / Ian Barlow
Product marketing lead	Jaclyn Fu
Operations lead	`
Additional members	Erin Lancaster, Ian Barlow, Irina Sandu

{{#set:Feature product manager=Jen Arguello

|Feature feature manager=` |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=Madhava Enros / Ian Barlow |Feature product marketing lead=Jaclyn Fu |Feature operations lead=` |Feature additional members=Erin Lancaster, Ian Barlow, Irina Sandu }}

Open issues/risks

`

Stage 1: Definition

1. Feature overview

Cloud to Device Messaging (aka Push Notifications) is a feature which will enable greater engagement with Firefox mobile users through an Android messaging service called Google Cloud Messaging.

The 2012 Firefox Mobile goal is to achieve 4.2 M ADIs

2. Users & use cases

• Reactivation - Reactivate 2 - 4% of installed-but-non-users into an incremental 530,000 – 1M ADIs
• User Research (surveys, etc)
• App or System update messages (not necessarily confirmed as a use case)

3. Dependencies

`

4. Requirements

• P1 - Enable messaging to users who have not used Firefox Mobile in X (what?) period of time
• P1 - Enable messaging with a call to action in the message
• P1 - Must be opt in
• P1 - Can be opted out
• P1 - Must work for Firefox Mobile Beta
• P2 - Must work for Firefox Mobile GA

Non-goals

This service is not for the Aurora and Nightly channels of Firefox Mobile.

Stage 2: Design

5. Functional specification

`

6. User experience design

Components:

• Notification system notifications themselves
  • do we have control over the icon shown?
  • how much control over the content of the notification row
• Where does it lead?
  • Directly to the market? -- only useful for reactivation/udpate
  • Interstitial messaging page
    • Is this a webpage? Does the C2DM system provide something?

Resources:

• C2DM developer page: https://developers.google.com/android/c2dm/
• GCM developer page: http://developer.android.com/guide/google/gcm/gs.html

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |Feature overview=Cloud to Device Messaging (aka Push Notifications) is a feature which will enable greater engagement with Firefox mobile users through an Android messaging service called Google Cloud Messaging.

The 2012 Firefox Mobile goal is to achieve 4.2 M ADIs |Feature users and use cases=* Reactivation - Reactivate 2 - 4% of installed-but-non-users into an incremental 530,000 – 1M ADIs

• User Research (surveys, etc)
• App or System update messages (not necessarily confirmed as a use case)

|Feature dependencies=` |Feature requirements=* P1 - Enable messaging to users who have not used Firefox Mobile in X (what?) period of time

• P1 - Enable messaging with a call to action in the message
• P1 - Must be opt in
• P1 - Can be opted out
• P1 - Must work for Firefox Mobile Beta
• P2 - Must work for Firefox Mobile GA

|Feature non-goals=This service is not for the Aurora and Nightly channels of Firefox Mobile. |Feature functional spec=` |Feature ux design=Components:

• Notification system notifications themselves
  • do we have control over the icon shown?
  • how much control over the content of the notification row
• Where does it lead?
  • Directly to the market? -- only useful for reactivation/udpate
  • Interstitial messaging page
    • Is this a webpage? Does the C2DM system provide something?

Resources:

• C2DM developer page: https://developers.google.com/android/c2dm/
• GCM developer page: http://developer.android.com/guide/google/gcm/gs.html

|Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

Priority	P1
Rank	999
Theme / Goal	`
Roadmap	`
Secondary roadmap	`
Feature list	`
Project	`
Engineering team	`

{{#set:Feature priority=P1

|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=` |Feature project=` |Feature engineering team=` }}

Team status notes

	status	notes
Products	`	`
Engineering	`	`
Security	`	`
Privacy	`	`
Localization	`	`
Accessibility	`	`
Quality assurance	`	`
User experience	`	`
Product marketing	`	`
Operations	`	`

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}