This meta tracks the work to enable the following: if a user installs Firefox from an AMO detail page, on first run we want to determine what that extension was and be able to refer to it (either by linking to the page or linking to the extension). While this is initially specific to one use case, this could/should be variable, to allow for recognizing other specific use cases/referrers that precede install and first run.

Some questions about the spec: - How are the add-on name and install URL determined via attribution? Do they need to be parsed from the source URL? - Where does “Find More Extensions” button link to? - Is there an attribution link / example we can test with somewhere? - Is there a way for users to cancel/close the dialog without clicking get the extension, or is that just the "Start browsing" button? - Is the icon generic for all add-ons? Also, we will need comps and final copy / image asset once the design is finalized. Thanks!

> - How are the add-on name and install URL determined via attribution? Do > they need to be parsed from the source URL? In https://bugzilla.mozilla.org/show_bug.cgi?id=1344771#c25, the snippet mixedpuppy posted shows how to get the data from attribution. the `content` param is what's storing the ID of the extension, and that's what you'd use to query the AMO API for the current version's installation URL. > - Where does “Find More Extensions” button link to? addons.mozilla.org (this is actually noted if you scroll down in the invisionapp mock -- which is not obvious unless you know to do it) > - Is there an attribution link / example we can test with somewhere? I'm not sure I understand the question. Attribution just results in a local file (see 1344771) which the AttributionCode.getAttrDataAsync() gets. Do you mean that level, or earlier? Because attribution happens currently from OSX installs and Windows via the stub installer when installed from addons.mozilla.org (among others). > - Is there a way for users to cancel/close the dialog without clicking get > the extension, or is that just the "Start browsing" button? It's basically the "Start browsing" button -- that should send us to AS/about:home. > - Is the icon generic for all add-ons? No, the icon should vary per extension and also be retrieved from the AMO API call. > Also, we will need comps and final copy / image asset once the design is > finalized. Thanks! NI emanuela because I *think* that's all finalized?

I can confirm this is the final UI with the final copy. Kate, how do you usually collect assets?

If you could add it as attachment (or a link to it:eL) in this bug that would work!

*typo, should be (or a link to it)

UX comps: https://mozilla.invisionapp.com/share/Y5I1DJYT8KU