4 ms·

One reason this was kind of urgent for us is: 1. The prevalance of low-end Android devices 2. The dominance of Android worldwide, e.g. http://www.idc.com/prod

One reason this was kind of urgent for us is: 1. The prevalance of low-end Android devices 2. The dominance of Android worldwide, e.g. http://www.idc.com/prodserv/smartphone-os-market-share.jsp http://www.idc.com/prodserv/smartphone-os-market-share.jsp shows 2015Q2, android 82.8%, iOS 13.9%, everything else ~3% We've also been working with Google to see what they can do to make Android/Chrome performance better with complex JavaScript like Ember and Angular. Chrome 45 improved things about 25% which is great, but when you start 500 to 800% slower, there's a long way to go.. Complex JavaScript performance on iOS is, and remains, amazing and stellar. Problem is not much of the world is on iOS.

codinghorror 11y ago
Adding insult to injury, 2015 was also an abysmal year for Android performance, largely due to Qualcomm, uh, how do I say this... sucking. "I don't think there's any way to sugarcoat this, but 2015 has not been a particularly great year for Qualcomm in the high-end SoC business" -- http://www.anandtech.com/show/9837/snapdragon-820-preview http://www.anandtech.com/show/9837/snapdragon-820-preview If you compare geekbench single threaded performance numbers, you can sure see why Google is anxious to build their own silicon.
- on_and_off 11y ago
  >you can sure see why Google is anxious to build their own silicon This can't come too soon. Even for native development, the Nexus 6P is a bit disappointing. It does have a lot of pixels to carry around but still its real life performances are not up to what I would expect.