- Make battery usage more efficient
- Add logic to batch requests until a wifi connection is present (or a certain amount of time has passed) on Android
- Trigger flush on the scenario : use goes offline , triggers events [ by using the app], stays offline after exiting the app and does not launch it after coming back online.
Description
Description
Event Timeline
Comment Actions
Make battery usage more efficient
+1
Add logic to batch requests until a wifi connection is present (or a certain amount of time has passed) on Android
When @Dbrant introduced us to event logging in the app, he mentioned events get put into a queue if the device is offline and then sent off once the app is launched and the device is online. (Or at least that's the case for MobileWikiAppSessions summary events.) Is that not the case for all the events?
Trigger flush on the scenario : use goes offline , triggers events [ by using the app], stays offline after exiting the app and does not launch it after coming back online.
Was the idea behind this that events should have an expiration date and that an event that's several days or even a week old is not super useful? (And yeah, it's useless in the sense that any metrics that would have been calculated from that time period have already been calculated and wouldn't be impacted by having this old data suddenly come in.)