Mobile Performance

Goals and Status

Engineering

• Land on what architecture we want to use: do we stay with dual architecture or do we move to a single, multi-threaded process?

Status: dougt is working on a build using the Java front-end for testing and evaluation by 10/7.

• Improve startup time

Status: Java architecture helps us with this but we need to continue to plow through mobile startup shrink bugs.

• Understand Memory Usage

Status: Pending, more info due by 10/7

• Improve Perceived Performance

Status: We are defining what this means and how we measure/analyze it. Pending, more info due by 10/7

• Improve Page Load, Panning, Zooming

Status: We have collected some measurements but need to standardize testing methodology. Aaron Train is doing a QA test day on Friday, 10/7. Stay tuned.

Refresh on the Big Picture

All these details. Brain. Refresh. Need Big Picture. Now.

• Provide customers with a mobile browser that exceeds customer expectations in terms of responsiveness by March 2012
  

• Be faster than native Android Browsers
  

• Be faster and better than iOS Browsers