Add telemetry probe for knowing more details about audio competition
Categories
(Core :: Audio/Video: Playback, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox86 | --- | fixed |
People
(Reporter: alwu, Assigned: alwu)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
|
48 bytes,
text/x-phabricator-request
|
tdsmith
:
data-review+
|
Details | Review |
When multiple audible tabs play at the same time, we call that situation as Audio competition. Audio focus managment is used to address the audio competition by only allowing one tab to play at the same time.
We already have a pref media.audioFocus.management to do that, which is OFF by default on desktop and ON by default on mobile.
I would like to explore the possibility of enabling the audio focus management on desktop, which might improve the UX for media control. Therefore, I would like to add a Telemetry probe to see (1) how often would users encounter the audio compeition and (2) would they address audio competition by themselves? Or simply ignore that and allow multiple audible tabs playing at the same time.
|
Assignee | |
Comment 1•5 years ago
|
||
|
||
Updated•5 years ago
|
|
|
Assignee | |
Comment 2•5 years ago
|
||
Comment on attachment 9194325 [details]
Bug 1683788 - add telemetry probe for the audio competition.
Request for data collection review form
- What questions will you answer with this data?
(1) how often would users encounter the audio compeition and (2) would they address audio competition by themselves? Or simply ignore that and allow multiple audible tabs playing at the same time.
- Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements? Some example responses:
We're exploring the possibility of enabling a feature, audio focus management, on desktop. Therefore, we want to know how real world users deal with the audio competition and how often it happens.
- What alternative methods did you consider to answer these questions? Why were they not sufficient?
No other way can do that.
- Can current instrumentation answer these questions?
As above, currently we don't have any result for them.
- List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories found on the Mozilla wiki.
Probe name : TABS_AUDIO_COMPETITION
Categories : 1 & 2 (Technical & Interaction data)
Description : The number of times users (1) play audible media without encounting audio competition (2) encounter audio competition but ignore it (keep all media continually playing) (3) encounter audio competition and manually handle it (4) encounter audio competition and let Gecko handle it
- Please provide a link to the documentation for this data collection which describes the ultimate data set in a public, complete, and accurate way.
This collection is documented in its definitions files Histograms.json.
- How long will this data be collected? Choose one of the following:
Until Fx91.
- What populations will you measure?
On non-release channels.
- If this data collection is default on, what is the opt-out mechanism for users?
That control by telemetry system, so I think user can disable Telemetry collection if they want.
- Please provide a general description of how you will analyze this data.
For example, the value ManagedFocusByUser from the probe can help us estimate the amount of users who would be benefit from enabling the feature
- Where do you intend to share the results of your analysis?
That is a Telemetry probe, so everyone is free to check the result.
- Is there a third-party tool (i.e. not Telemetry) that you are proposing to use for this data collection? If so:
No
|
||
Comment 3•5 years ago
|
||
Comment on attachment 9194325 [details]
Bug 1683788 - add telemetry probe for the audio competition.
Once the documentation is addressed this is r+ but if you'd like to understand user behavior I'd encourage you to collect this in release, as well -- prerelease users are not representative of the Firefox userbase and this is not an invasive collection.
- Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?
There will be, in the probe definition files and the Probe Dictionary.
- Is there a control mechanism that allows the user to turn the data collection on and off?
Yes, the Firefox telemetry opt-out.
- If the request is for permanent data collection, is there someone who will monitor the data over time?
This is a temporary collection.
- Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Cat 2, interaction data.
- Is the data collection request for default-on or default-off?
Default-on.
- Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)?
No.
- Is the data collection covered by the existing Firefox privacy notice?
Yes.
- Does there need to be a check-in in the future to determine whether to renew the data?
alwu is responsible for renewing as needed.
- Does the data collection use a third-party collection tool?
No.
|
||
Comment 5•5 years ago
|
||
| bugherder | ||
Description
•