Identification and prioritization of responsiveness improvements for Fenix
Categories
(User Research :: Project Request, enhancement)
Tracking
(Not tracked)
People
(Reporter: esmyth, Assigned: kardekani)
Details
Request Description
The November 2018 user research studies comparing Fennec to Chrome and GeckoView to Webview identified many issues or differences related to input, browser, and scroll responsiveness that caused user’s to have a significant preference for Chrome or Webview over Fennec or Geckoview. Significant fixes for responsiveness issues (e.g., scroll anchoring, scroll snapping) have landed since the studies were conducted and additional fixes are planned for the FF67 and FF68 releases.
We would like to conduct a similar study to the November 2018 mobile perceived performance studies to determine if the negative perception of perceived performance, particularly related to responsiveness, persists and is still significant enough to impact browser preference for Fenix relative to Chrome.
User Tasks of Interest:
- Scroll
- Scroll one page
- Scroll to bottom of page
- Scroll to top of page
- Input
- Begin typing in a text element (e.g.,
<input>,<textarea>) - Click/touch hyperlink
- Open page menu
- Touch pan map
- Touch zoom in/out map
- Begin typing in a text element (e.g.,
- UI
- Open new tab
- Initiate tab switch
- Select tab in current session
- Open bookmarked page
- Open three dot menu
- Enter private browsing mode
We propose considering the following:
- Independent variable:, task responsiveness rating
- Dependent variables: Browser preference rating
- Possible segments: bandwidth, Moto G5 vs Pixel 2 devices, primary browser
Perceived performance of app startup, page load, and media playback are not priorities for this study.
Deadline
Requested delivery by April 29, 2019
Priority Level
(1 = High 2 = Medium, 3 = Low): 1
Priority Level Description
The perceived performance of scroll (P1), input (P2), and UI (P2) responsiveness are priorities for the Fenix (Q2 KR) and performance (Q2 KR) teams.
Supporting Information
Comment 1•7 years ago
|
||
@esymth - Does this timeline include enough time to act on the research before Fenix ships?
Alice will also meet with Barbara & Michelle on related questions.
@gemma, no, but that is no longer the intent. Given the Fenix timeline, the perf and Fenix teams agreed that there would not be sufficient time to take meaningful action based on the findings of the study. We revised our Q2 plans to use this study to guide perf-team investigations into fixes that would not land until H2.
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Comment 3•7 years ago
|
||
Putting on hold briefly in order to free up Kamyar for an urgent project.
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
| Assignee | ||
Comment 4•7 years ago
|
||
Here is the report of the study: https://docs.google.com/document/d/1x0_t8kkg6q_pFfz6LfyrjY2h2nKM3RSnGPexdXwYOxo/edit?usp=sharing
Description
•