Closed Bug 1475354 Opened Last year Closed Last year
Create first-run template and content for Return To AMO experience
We discussed previously that the ReturnToAMO project would need to result in presenting information to the user at first run. This fits with the plan for a dynamic about:welcome that's fed by AS Router. This bug is to track the actual template and content development that ReturnToAMO would integrate with AS Router & about:welcome. While the OSX attribution is still in flight, we could proceed with this now on Windows, provided we can identify the development team that should own it.
Sounds good to me! The first step here would be to consult with Aaron Benson and/or Bryan Bell on the proposed design and we can take it from there.
(setting to p3 until we have a clearer idea of the scope/timeline)
Emanuela is going to talk to Aaron. He was engaged early on in this UX. The PRD links to the invision doc. https://docs.google.com/document/d/1BukJcOsfXoP651IN8P2BTZ8jpc83KAa3caMKlpjTxDQ/edit#bookmark=id.bqs5864xhtjf The scope of what needs to happen is here in the PRD: https://docs.google.com/document/d/1BukJcOsfXoP651IN8P2BTZ8jpc83KAa3caMKlpjTxDQ/edit#heading=h.do1xmty2dup7 Timing wise we'd hope to implement this in 64 if possible (Amy Tsay is the PM, working with Cmore in OnBoarding). The impact is high - since this is customizing after a user initiated install, to get them back to where they intended to go. Return-to-AMO (~35,000 installs per week) is the first candidate, but Test Pilot and monitor.firefox.com would want to fast follow (for users who install firefox from either of those 2 sites). _______ Ddurst in Eng is verifying (with Stephanie Ouillon) if the primary CTA button on about:welcome can go directly to install the add-on or if it needs to link to the AMO detail page they started from - where they can install the add-on. The only impact to implementation is: If it can go directly to install - the wording on the CTA button changes to "Add the Extension" instead of "Get the Extension" The link where the button goes (either kicks off install or goes to AMO page the user started from).
Just a note for implementors. In bug 1344771 comment 25 I have a code example of how to get the addon data from the attribution data. It's a simple couple lines to get the data you need to build the content. The attachment is a full example that can be run from the scratchpad in browser mode.
(In reply to Kate Hudson :k88hudson from comment #1) > Sounds good to me! The first step here would be to consult with Aaron Benson > and/or Bryan Bell on the proposed design and we can take it from there. Aaron is good for this one. The UX team consulted with him during the design phase and we met yesterday to be sure we are all align. We are. Green light from the UX team
untriaged from P3, for reconsideration for higher priority. Timeframe we are hoping is 64 - scoping would be a talk with Ddurst to see how the work breaks out.
Priority: P3 → --
No longer blocks: 1432588
Summary: [AS Router] Create first-run template and content for Return To AMO experience → Create first-run template and content for Return To AMO experience
Commit pushed to master at https://github.com/mozilla/activity-stream https://github.com/mozilla/activity-stream/commit/f40d201cfe4d67fec4ba7adc10d46c4c97924af6 Fix Bug 1475354 - Create first-run template and content for Return To AMO experience (#4578)
Verified this bug using MacOS 10.13.6, as discussed with Andrei, Windows validation will be treated on a different bug.
You need to log in before you can comment on or make changes to this bug.