Maximiliano Firtman interviewed at Velocity 2011

on YouTube ↗07m

" summary

Mobile web faces fragmentation across hardware, browser engines and HTML5 support and suffers from sparse official documentation, so testing becomes mandatory. Claim: BlackBerry PlayBook browser has almost all HTML5 APIs and a remote web inspector, while Safari on iOS leads in new features. Emulators are fine for early UI and screen testing but not performance; there are about 25 browsers and 150 emulators to consider. Note: iOS UIWebView lacks Nitro JavaScript engine. Predictions: WebGL 3D and WAC/W3C device APIs arrive within a couple of years.

AI-written summary · about

" chapters (8)

1. 0:00Introduction
2. 0:20Biggest obstacles in developing for mobile browsers
3. 1:09Best mobile browser
4. 2:35Best decision to start developing
5. 3:04Mobile emulators
6. 3:55Real devices
7. 4:17Browsers
8. 5:22Web app functionality

" related talks

• 25mThe Web: Evolution in ActionBrendan Eich · dotJS 2013
• 40mWeb Applications of the FutureIlya Pukhalskiy · FrontTalks 2013
• 37mBuzz It For Real ! ... the tortuous road to Mobile HTML5 AppsAndrea Giammarchi · JSConf EU 2011
• 35mThe Ugly Truths about HTML5 for Mobile AppsRobert Virkus · infoShare 2013
• 43mThe Mobile Web: MIAAlex Russell · JSCamp Romania 2019
• 01h 18mMobile browser panelArnaud Weber, Andrea Trasatti, Andreas Bovens, Eli Fidler · Mobilism 2012
• 39mDoes The Browser Have A FutureTim Bray · GOTO Copenhagen 2014
• 56mDoes the Browser have a Future?Tim Bray · GOTO Chicago 2014