Features/Firefox/Easy UI Feature Testing

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

Status

Easy UI Feature Testing and "Success Evaluation" (integrate TestPilot like features)
Stage	Draft
Status	In progress
Release target	Firefox 13
Health	OK
Status note	`

{{#set:Feature name=Easy UI Feature Testing and "Success Evaluation" (integrate TestPilot like features)

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

Team

Product manager	`
Directly Responsible Individual	Gregg Lind
Lead engineer	`
Security lead	`
Privacy lead	`
Localization lead	`
Accessibility lead	`
QA lead	`
UX lead	`
Product marketing lead	`
Operations lead	`
Additional members	`

{{#set:Feature product manager=`

|Feature feature manager=Gregg Lind |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

Ability to modify UI has potential performance, privacy implications Collecting data has Privacy implications Publishing collected data has Privacy Implications What makes a "successful" feature?

Stage 1: Definition

1. Feature overview

Right now, features can go into FX without knowing if they will be 'successful' or not. What 'success' even means is a bit nebulous!

By incorporating Test-Pilot-like features into Firefox, it makes it easier for Feature Developers to design, implement, and instrument new features.

With usual statistics (among targeted test populations), product managers can make better decisions around which features should go forward, be revised, or be removed. This removes one of the barriers to having every feature in Firefox go through usability testing.

2. Users & use cases

• A/B testing of user features
• UI experiments
• all new user features

3. Dependencies

bringing TP like code (with mechanisms for watching events, deploying modified UI elements) into main build.

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

Include TP like functionality into FX directly, making the addon superfluous, on all FX platforms.

Specific functionalities:

• record/report any event on any id-able element, with timestamp, for a user.
• choose to run a study / instrumentation on a particular subset of users
• deploy variations in UI (via restartless addon, or another mechanism)

6. User experience design

Users should be able to see submitted data, similar to current TP implementation. Users get notification of initial opt-in Users can destroy / opt-out / not submit their data.

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=Ability to modify UI has potential performance, privacy implications Collecting data has Privacy implications Publishing collected data has Privacy Implications What makes a "successful" feature? |Feature overview=Right now, features can go into FX without knowing if they will be 'successful' or not. What 'success' even means is a bit nebulous!

By incorporating Test-Pilot-like features into Firefox, it makes it easier for Feature Developers to design, implement, and instrument new features.

With usual statistics (among targeted test populations), product managers can make better decisions around which features should go forward, be revised, or be removed. This removes one of the barriers to having every feature in Firefox go through usability testing. |Feature users and use cases=* A/B testing of user features

• UI experiments
• all new user features

|Feature dependencies=bringing TP like code (with mechanisms for watching events, deploying modified UI elements) into main build. |Feature requirements=` |Feature non-goals=` |Feature functional spec=Include TP like functionality into FX directly, making the addon superfluous, on all FX platforms.

Specific functionalities:

• record/report any event on any id-able element, with timestamp, for a user.
• choose to run a study / instrumentation on a particular subset of users
• deploy variations in UI (via restartless addon, or another mechanism)

|Feature ux design=Users should be able to see submitted data, similar to current TP implementation. Users get notification of initial opt-in Users can destroy / opt-out / not submit their data. |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	Unprioritized
Rank	999
Theme / Goal	`
Roadmap	`
Secondary roadmap	`
Feature list	`
Project	`
Engineering team	`

{{#set:Feature priority=Unprioritized

|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	sec-review-needed	Please schedule with curtisk
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=sec-review-needed |Feature security health=` |Feature security notes=Please schedule with curtisk |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=` }}