Bug 1555328 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Alessio Placitelli [:Dexter] - Out until 01/July from comment #2)
> Instead of persisting the status, which would still leave the case of starting the application with glean for the first time uncovered, what about requiring the product to tell us the initial state through `initialize`?

Ok, how about we run through how an integration could look like in an app, based on how we know behavior is in firefox:
1) on first app launch/init, we shouldn't send data yet (as we couldn't give the user an opportunity to opt out yet).
2) after some time, the app can enable upload
3) after this, there might be some times where disabling/enabling of upload happens through the user changing application settings

From here i assume we need:
- default to upload disabled - covers 1)
- we need a Glean SDK function to enable/disable upload - covers 2) & 3)

How does that sound?

We should also probably double-check with mobile app engineers from 1-2 products how that sounds to them.
(In reply to Alessio Placitelli [:Dexter] - Out until 01/July from comment #2)
> Instead of persisting the status, which would still leave the case of starting the application with glean for the first time uncovered, what about requiring the product to tell us the initial state through `initialize`?

Ok, how about we run through how an integration could look like in an app, based on how we know behavior is in firefox:
1) on first app launch/init, we shouldn't send data yet (as we couldn't give the user an opportunity to opt out yet).
2) after some time, the app can enable upload
3) after this, there might be some times where disabling/enabling of upload happens through the user changing application settings

From here i assume we need:
- default to upload disabled - covers 1)
- we need a Glean SDK function to enable/disable upload - covers 2) & 3)

How does that sound?

We should also probably double-check with mobile app engineers from 1-2 products how that sounds to them. The needs and actual integrations may be different from what we're used to.

Back to Bug 1555328 Comment 3