3 ms·

I don't think cpu were ready back then. Sure you had that blackberry thing using the equivalent of the modern embedded webview but you couldn't do much heavy li

I don't think cpu were ready back then. Sure you had that blackberry thing using the equivalent of the modern embedded webview but you couldn't do much heavy lifting with it. Also many standard didn't exist. Maybe today, with webgl and asm.js and web workers It's viable, but in the days native access was the only way to provide a smooth experience. See: http://techcrunch.com/2012/09/11/mark-zuckerberg-our-biggest-mistake-with-mobile-was-betting-too-much-on-html5/ http://techcrunch.com/2012/09/11/mark-zuckerberg-our-biggest...

amelius 11y ago
Good points, but I think that Facebook's problems might have been more about integration than about performance.
- LoSboccacc 11y ago
  Found the technical writeup http://lists.w3.org/Archives/Public/public-coremob/2012Sep/0021.html http://lists.w3.org/Archives/Public/public-coremob/2012Sep/0... Two main issues back then were scrolling perrformance and memory constraints. We're working at image heavy microsites at lookcast and I can confirm memory issues and composition performances are still constraining what we can do on devices.