Mobile/Projects/Telemetry probes for Fennec UI elements: Difference between revisions

(Created page with "== Tracking == * Meta-bug to be filed == Goals == We need more data about how users actually interact with our browser, and we can create a valuable source of data by buildin...")
 
 
(16 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Tracking ==
== Tracking ==
* Meta-bug to be filed
* Meta-bug: {{bug|942279}}


== Goals ==
== Goals ==
Line 6: Line 6:


== What data? ==
== What data? ==
''What questions do we want to answer? What data are we looking to collect?''
=== General usage patterns ===
* Need a session for each "screen" in order to facilitate heatmapping etc.
* How are people opening Firefox?
** [how] Different telemetry session types — allows for partitioning behaviors between these usage types.
** Tapping Firefox icon on Android homescreen
** Link from another app
** Android Homescreen bookmark
* How often are people opening (focusing) Firefox?
* Duration of each browsing session?
** Number of pages visited
** Number of tabs open
*** On restore!
* [P1] What are people doing?
** How are users getting to a page?
*** Searching
**** Breakdown of providers used
**** Are they using suggestions?
*** Typing URLs
*** Retrieving Saved Stuff from Home
**** which parts?
*** Coming in from an outside link
*** Tapping: row, thumbnail/top site
** How are users saving stuff? + bounce time, if applicable
*** Bookmarking
*** Sharing
*** Opening in new tab
*** Adding to reading list
** How are tabs used?
*** Comparison?
**** Actively switching through tabs in a "short" session
***** More tab switching events than tabs
***** Tab switching interspersed (or not) by other events (loading page)
***** Also keep track of re-opened tabs
**** Read later?
**** Do they just collect over time?
***** Tab lifetime between sessions?
*** Amount of effort spent in typing
**** Searches
**** URLs
**** Other web inputs — in content
*** Device orientation (landscape vs portrait)
*** Methods of exiting Firefox (home, closing tab, etc).
** Relative popularity of Private / Guest Browsing
*** For detailed recording within: [privacy-review-needed]
** Extent to which people customize the browser
*** In Settings
*** with Add-ons
* Heatmap of browser UI usage
** Context of what to overlay heatmap on
** Are we prioritizing the right stuff?
* How does this differ on phones vs. tablets?


== Technical details ==
== Technical details ==
TBD
{{bug|932092}} ships in Firefox 28, and allows for UI code to record telemetry events for analysis.
 
Canonical documentation lives here (though bear in mind that m-c is usually behind fx-team by a day):
 
https://ci.mozilla.org/job/mozilla-central-docs/Tree_Documentation/fennec/index.html
 
which is rendered from
 
https://hg.mozilla.org/integration/fx-team/file/default/mobile/android/base/docs/index.rst
 
== Processing ==
 
We use the same MapReduce infrastructure as desktop to get answers out of our measurements. If you are looking to run a job or write a new one, all of our MapReduce jobs and how to use them are in this github repo: https://github.com/gerfuls/fennec-telemetry


== Research/references ==
== Research/references ==
TBD
'''Note:''' Make sure Insights & Metrics teams are aware of what we're hoping to do once we have this a bit more solidly defined.
 
An etherpad that needs a lot of work: https://etherpad.mozilla.org/FxATelemetry


== UX design ==
== UX design ==
Confirmed users
450

edits