Improved missing plugin experience

Feature	Status	ETA	Owner
Improved missing plugin experience		N/A	Justin Dolske

Summary

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.

Team

• Feature Manager: Justin Dolske
• Lead Developer:
• Product Manager:
• QA:
• UX: Alex Limi
• Accessibility:
• Security:
• Privacy:

Release Requirements

• Ability to detect and point to relevant locations for the major plugins
• Mozilla needs to host permanent redirect URLs for this, so we can change quickly, should downstream providers suddenly change their URLs or similar
• 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
• 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
• 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

Next Steps & Open Issues

• Get estimates from Justin
• Identify the list of plugins we want to handle