Spike: Investigate refactoring and enabling a single source of management for existing CFRs
Categories
(Firefox for Android :: Onboarding, task, P1)
Tracking
()
People
(Reporter: towhite, Assigned: towhite)
References
(Blocks 2 open bugs, )
Details
(Whiteboard: [fxdroid][group2])
The current management of CFRs (and other 'views') is handled in multiple places in the code which makes it difficult to keep track of the various views being displayed to the user and is susceptible to conflicting views - especially when we factor in Nimbus experiments. We should look at refactoring the current CFR implementation to use a single central source of management which could include queuing and prioritization. This should also be scalable to include more 'view' types in the future such as Dialogs, Snackbars, Toasts etc. Suggestions so far have included the use of a Store.
This Spike should include:
- inventory of all the current CFRs used in the app, including any triggered in experimental settings or with experiments.
- identify potential solutions
Use the Spike investigation report doc to capture the findings of the investigation.
Important
- Do NOT change any of the current CFR ordering/triggers
- Take inventory of the current CFRs
Updated•1 year ago
|
| Comment hidden (obsolete) |
Comment 2•1 year ago
•
|
||
Attaching a Google Doc where Nick has documented all of the CFRs and their triggers. It also has a link to a Figma where this is all captured by UX.
Thanks Noah - also linked in the Spike doc
Description
•