Experiments library, do we need to update experiments if the app is not running or in the background?
Categories
(Data Platform and Tools :: Glean: SDK, task, P3)
Tracking
(Not tracked)
People
(Reporter: travis_, Unassigned)
References
Details
(Whiteboard: [mobile-experiments])
Currently we are working on a way to periodically update the experiments (in bug 1541973 ) in the background using WorkManager
with a PeriodicWorkRequest
on a schedule of every 6 hours. Do we really want to update experiments in the background like this and what is the best method of notifying when experiments have changes?
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
Georg, what do we want to do about this since Benson's team is taking it over?
Reporter | ||
Comment 2•5 years ago
|
||
Mythmon, do you or your team have input on this issue?
Comment 3•5 years ago
|
||
It would be nice for experiments data to be updated when the app isn't open. That decreases the potential delay between starting the app and getting experiments, which might be crucial for things like start screen or first-run experiments. I think it also means we have a way to manipulate the experiments store when the app isn't running, which seems like a very good bit of architecture to have.
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 4•5 years ago
|
||
Keeping this as is since it seems that updating experiments async when the app is not open is desirable.
Description
•