Features/Fennec/Android Snippets: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
m (added ops lead)
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{FeatureStatus
{{FeatureStatus
|Feature name=Cloud to Device Messaging
|Feature name=Android Snippets
|Feature stage=Draft
|Feature stage=Draft
|Feature status=In progress
|Feature status=In progress
|Feature health=OK
|Feature health=OK
|Feature status note=Proof of concept underway.
}}
}}
{{FeatureTeam
{{FeatureTeam
|Feature product manager=Jen Arguello
|Feature product manager=Karen Rudnitski
|Feature lead engineer=Richard Newman (client, project); JR Conlin (server)
|Feature ux lead=Madhava Enros / Ian Barlow
|Feature ux lead=Madhava Enros / Ian Barlow
|Feature product marketing lead=Jaclyn Fu
|Feature product marketing lead=Jaclyn Fu
|Feature operations lead=Mark Mayo
|Feature additional members=Erin Lancaster, Ian Barlow, Irina Sandu
|Feature additional members=Erin Lancaster, Ian Barlow, Irina Sandu
}}
}}
{{FeaturePageBody
{{FeaturePageBody
|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 [http://developer.android.com/guide/google/gcm/gs.html Google Cloud Messaging].
|Feature overview=This feature aims to provide a marketing channel to improve user engagement on Android. Some evidence suggests that system notifications can improve stickiness without negatively affecting user feedback; this channel aims to provide a mechanism for delivering those system notifications.


The 2012 Firefox Mobile goal is to achieve 4.2 M ADIs
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
|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)
* User Research (surveys, etc)
* App or System update messages (not necessarily confirmed as a use case)
* App or System update messages (not necessarily confirmed as a use case)
Line 25: Line 28:
* P2 - Must work for Firefox Mobile GA
* P2 - Must work for Firefox Mobile GA
|Feature non-goals=This service is not for the Aurora and Nightly channels of Firefox Mobile.
|Feature non-goals=This service is not for the Aurora and Nightly channels of Firefox Mobile.
|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


some answers here:
Note that Google Cloud Messaging is not a suitable implementation strategy for this, for various reasons.
<a href="http://www.flickr.com/photos/madhava_work/7508528760/" title="skitchV1NLl7 by madhava_work, on Flickr"><img src="http://farm9.staticflickr.com/8153/7508528760_05065cb86a_z.jpg" width="616" height="500" alt="skitchV1NLl7"></a>
|Feature ux design=1. Allowing notifications in the Google Play download terms
 
http://farm9.staticflickr.com/8174/7943622518_e1f78a9792_b.jpg
 
 
2. Opt out: a toggle in Settings, for people who don't want this on.
 
http://farm9.staticflickr.com/8458/7943623308_95ef9ba2fc_b.jpg
 
3. Notification UI
 
http://farm9.staticflickr.com/8310/7943622946_1cdb231efc_h.jpg
 


* 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:
Resources:
* C2DM developer page: https://developers.google.com/android/c2dm/
* Notifications on Android: http://developer.android.com/design/patterns/notifications.html
* GCM developer page: http://developer.android.com/guide/google/gcm/gs.html
|Feature implementation plan=See {{Bug|774497}} and dependencies.
 
Server-side work not yet tracked.
 
Snippets will be periodically fetched via HTTP, with server-side filtering based on client attribute. Client-side filtering, caching, and presentation. Background Android alarm to manage periodic fetches.
|Feature security review=See {{Bug|774497}} and dependencies.
|Feature privacy review=See {{Bug|774497}} and dependencies.
|Feature localization review=l10n is an open question; campaign messages need to be localized.
|Feature accessibility review=Nothing special required for Android.
|Feature implementation notes=Underway.
}}
}}
{{FeatureInfo
{{FeatureInfo
|Feature priority=P1
|Feature priority=P1
|Feature engineering team=Sync
}}
}}
{{FeatureTeamStatus}}
{{FeatureTeamStatus}}

Latest revision as of 22:52, 13 November 2012

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

Status

Android Snippets
Stage Draft
Status In progress
Release target `
Health OK
Status note Proof of concept underway.

{{#set:Feature name=Android Snippets

|Feature stage=Draft |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=Proof of concept underway. }}

Team

Product manager Karen Rudnitski
Directly Responsible Individual `
Lead engineer Richard Newman (client, project); JR Conlin (server)
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead Madhava Enros / Ian Barlow
Product marketing lead Jaclyn Fu
Operations lead Mark Mayo
Additional members Erin Lancaster, Ian Barlow, Irina Sandu

{{#set:Feature product manager=Karen Rudnitski

|Feature feature manager=` |Feature lead engineer=Richard Newman (client, project); JR Conlin (server) |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=Mark Mayo |Feature additional members=Erin Lancaster, Ian Barlow, Irina Sandu }}

Open issues/risks

`

Stage 1: Definition

1. Feature overview

This feature aims to provide a marketing channel to improve user engagement on Android. Some evidence suggests that system notifications can improve stickiness without negatively affecting user feedback; this channel aims to provide a mechanism for delivering those system notifications.

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.

Note that Google Cloud Messaging is not a suitable implementation strategy for this, for various reasons.

Stage 2: Design

5. Functional specification

`

6. User experience design

1. Allowing notifications in the Google Play download terms

7943622518_e1f78a9792_b.jpg


2. Opt out: a toggle in Settings, for people who don't want this on.

7943623308_95ef9ba2fc_b.jpg

3. Notification UI

7943622946_1cdb231efc_h.jpg


Resources:

Stage 3: Planning

7. Implementation plan

See bug 774497 and dependencies.

Server-side work not yet tracked.

Snippets will be periodically fetched via HTTP, with server-side filtering based on client attribute. Client-side filtering, caching, and presentation. Background Android alarm to manage periodic fetches.

8. Reviews

Security review

See bug 774497 and dependencies.

Privacy review

See bug 774497 and dependencies.

Localization review

l10n is an open question; campaign messages need to be localized.

Accessibility

Nothing special required for Android.

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

Underway.

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |Feature overview=This feature aims to provide a marketing channel to improve user engagement on Android. Some evidence suggests that system notifications can improve stickiness without negatively affecting user feedback; this channel aims to provide a mechanism for delivering those system notifications.

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.

Note that Google Cloud Messaging is not a suitable implementation strategy for this, for various reasons. |Feature functional spec=` |Feature ux design=1. Allowing notifications in the Google Play download terms

7943622518_e1f78a9792_b.jpg


2. Opt out: a toggle in Settings, for people who don't want this on.

7943623308_95ef9ba2fc_b.jpg

3. Notification UI

7943622946_1cdb231efc_h.jpg


Resources:

|Feature implementation plan=See bug 774497 and dependencies.

Server-side work not yet tracked.

Snippets will be periodically fetched via HTTP, with server-side filtering based on client attribute. Client-side filtering, caching, and presentation. Background Android alarm to manage periodic fetches. |Feature security review=See bug 774497 and dependencies. |Feature privacy review=See bug 774497 and dependencies. |Feature localization review=l10n is an open question; campaign messages need to be localized. |Feature accessibility review=Nothing special required for Android. |Feature qa review=` |Feature operations review=` |Feature implementation notes=Underway. |Feature landing criteria=` }}

Feature details

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

{{#set:Feature priority=P1

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

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=` }}