Add event tracking for key Fennec events to help inform decision on when Fenix is at parity to make Fennec to Fenix Transition
Categories
(Data Platform and Tools :: General, defect)
Tracking
(Not tracked)
People
(Reporter: gkaberere, Unassigned)
Details
With Fenix launched, we are now in the process of continuing to improve Fenix in preparation for it replacing Fennec. To inform the decision as to when Fenix is ready to replace Fennec, we need to understand how Fennec is currently used and prioritize key features to be built in Fenix that are essential to our current Fennec user base to make sure that the large majority of users will not be dissatisfied once we make the transition.
Upon discussions with different teams during the non desktop work week, we realized that we need to add some event / feature tracking into Fennec to help inform this decision. The prioritized list of items we would like to track can be found in this doc: https://docs.google.com/document/d/1Urke8GLeaN9P2_QIVWnf7FU3jWoS-Z1TkWVFuzu4zxU/edit
|
||
Comment 1•6 years ago
|
||
I set this to P1 as it is the highest functional development work priority for Mobile right now. Should the Product category be Firefox for Android for proper triage? I'm not sure as I suspect engineering work is needed on both the product side and the data ingest side.
|
|
||
Comment 2•6 years ago
•
|
||
@Stefan (who we should get up to speed about this work).
I'd suggest we keep this as the meta bug, and then create two bugs this one is dependent on: one for DE and one for Android engineering (and eventually one for DS or A depending on how we want to use that data once it lands, but we can do that later)
|
|
||
Comment 3•6 years ago
|
||
The engineering work is happening in this bug and the bugs it depends on https://bugzilla.mozilla.org/show_bug.cgi?id=1584188
|
|
||
Comment 4•4 years ago
|
||
Fennec - closing
|
Assignee | |
Updated•3 years ago
|
Description
•