Features/Fennec/Android Snippets
Status
| Android Snippets | |
| Stage | Draft |
| Status | In progress |
| Release target | ` |
| Health | OK |
| 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 |
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
2. Opt out: a toggle in Settings, for people who don't want this on.
3. Notification UI
Resources:
- Notifications on Android: http://developer.android.com/design/patterns/notifications.html
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
`
Feature details
| Priority | P1 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | ` |
| Secondary roadmap | ` |
| Feature list | ` |
| Project | ` |
| Engineering team | Sync |
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
