Platform/60fps: Difference between revisions
< Platform
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
against native." - jonas | against native." - jonas | ||
== Implementation Strategy == | |||
=== Outstanding Issues === | |||
* How do we work with [[Firefox/Content_Performance_Program | Firefox Content Performance program]] | * How do we work with [[Firefox/Content_Performance_Program | Firefox Content Performance program]] | ||
* What forms of jank are we prioritizing? | * What forms of jank are we prioritizing? | ||
| Line 20: | Line 20: | ||
* How do we measure? How do we automate that measure and see our progress over time? | * How do we measure? How do we automate that measure and see our progress over time? | ||
=== How do we measure === | |||
* Video (compositing on-time). | * Video (compositing on-time). | ||
* Animations (compositing on-time, JavaScript/main thread latency+throughput) | * Animations (compositing on-time, JavaScript/main thread latency+throughput) | ||
| Line 26: | Line 26: | ||
* Scrolling (compositing on-time, input latency, and layout/painting). | * Scrolling (compositing on-time, input latency, and layout/painting). | ||
=== Sites we care about === | |||
Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE. Perhaps measu | Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE. Perhaps measu | ||
* [http://www.facebook.com www.facebook.com] | * [http://www.facebook.com www.facebook.com] | ||
| Line 37: | Line 37: | ||
* [http://www.macrumors.com www.macrumors.com] | * [http://www.macrumors.com www.macrumors.com] | ||
=== Internal Projects we care about === | |||
* Gaia Team | * Gaia Team | ||
* Partner Engieneering | * Partner Engieneering | ||
| Line 43: | Line 43: | ||
* Shumway | * Shumway | ||
=== External Projects === | |||
And a list of 5 web frameworks that are likely focal points for concerns along these lines. | And a list of 5 web frameworks that are likely focal points for concerns along these lines. | ||
===Identify existing programs that have the same or similar goals === | |||
When will they land? If they land did they solve the problem? | When will they land? If they land did they solve the problem? | ||
Revision as of 21:15, 26 June 2015
Overall Goal
Enable a smooth and responsive user experience for Firefox desktop and mobile users.
Justification
We believe or have data that hangs, jank, and other forms of poor performance result in users moving to other browsers. [evidence needed]
"Both aspects here are important. Making existing content less janky makes it easier to compete against other browsers. Making it easier to create jank-free content makes it easier for the web to compete against native." - jonas
Implementation Strategy
Outstanding Issues
- How do we work with Firefox Content Performance program
- What forms of jank are we prioritizing?
- What are our use cases, projects, sites that we prioritize
- How do we measure? How do we automate that measure and see our progress over time?
How do we measure
- Video (compositing on-time).
- Animations (compositing on-time, JavaScript/main thread latency+throughput)
- WebGL/WebVR (compositing on-time, input latency, main thread latency, and JavaScript throughput).
- Scrolling (compositing on-time, input latency, and layout/painting).
Sites we care about
Important sites, especially those perform worse in Firefox versus Chrome/Safari/IE. Perhaps measu
- www.facebook.com
- www.twitter.com
- www.nytimes.com
- www.latimes.com
- ww.foxnews.com
- www.engadget.com
- www.tumblr.com
- www.macrumors.com
Internal Projects we care about
- Gaia Team
- Partner Engieneering
- Games/VR
- Shumway
External Projects
And a list of 5 web frameworks that are likely focal points for concerns along these lines.
Identify existing programs that have the same or similar goals
When will they land? If they land did they solve the problem?
- Firefox Content Performance program
- Async pan zoom
- Off main thread compositing
- Project Silk
- E10S
People
- Product sponsor/driver: naveed
- Engineering program manager:
- Platform Teams and Team champions:
JavaScript/naveed,
- Technical lead(s):