Personal tools

Improved missing plugin experience

From MozillaWiki

Jump to: navigation, search
Please use "Edit with form" above to edit this page.

Status

Improved missing plugin experience
Stage Planning
Status In progress
Release target `
Health OK
Status note `

Team

Product manager Chris Lee
Directly Responsible Individual Justin Dolske
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Paul Silaghi
UX lead Alex Limi
Product marketing lead `
Operations lead `
Additional members `

Open issues/risks

`

Stage 1: Definition

1. Feature overview

Our current experience when a plugin is missing is pretty abysmal, and rarely works for anything else than a very small set of plugins. We want to fix the experience for the small set of plugins that have a lot of users, and stop pretending to supply an auto-detect service for the others.


This feature falls primarily in the Experience category (from the "Discover, Experience, and Connect" vision statement.)

2. Users & use cases

`

3. Dependencies

`

4. Requirements

  • Ability to detect and point to relevant locations for the major plugins
    • PFS does this
  • Mozilla needs to host permanent redirect URLs for this, so we can change quickly, should downstream providers suddenly change their URLs or similar
    • PFS basically does this.
  • bug 268936 - It should be possible to say "Don't ask me to install this plugin again"
  • We should never imply that installing a plugin is absolutely necessary for the browser to function (like we kind of do today), but rather that plugins are required for certain types of content
  • bug 678707 - We should label which plugins you'll end up downloading/installing in the location where we show the "Missing Plugin" message. Right now, you don't know until you go ahead and start the process
  • bug 264254 (essentially WONTFIX) - We want to stop using Plugin Finder Service, and instead hardcode the small list of plugins we care about to simplify the code and maintenance burden
    • We are maintaining plugin data for plugincheck anyways

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

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

`


Feature details

Priority P2
Rank 2
Theme / Goal Experience
Roadmap User Experience
Secondary roadmap `
Feature list Desktop
Project `
Engineering team Desktop front-end

Team status notes

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