> offline access is a really important part of the mobile user experience Yes, it is. That's why HTML5 has the cache manifest [1]. With that, you don't need a

> offline access is a really important part of the mobile user experience Yes, it is. That's why HTML5 has the cache manifest [1]. With that, you don't need a connection on an HTML5 web app if you wouldn't need one on an installed native app. > access to device specific APIs like camera, accelerometer, notifications etc There are already plans, drafted specifications [3], and working implementations [4] for device APIs. > performance and responsiveness will be worse. Performance is getting better with time, as mobile JavaScript implentations get better (Nitro on iOS, Chrome Mobile on Android). Responsiveness can be improved by using hardware-accelerated CSS transitions instead of JavaScript animation, by disabling built-in wait times on the touch of an HTML element [5], and more. [1]: http://www.html5rocks.com/en/tutorials/appcache/beginner/ http://www.html5rocks.com/en/tutorials/appcache/beginner/ [2]: http://en.wikipedia.org/wiki/WebGL http://en.wikipedia.org/wiki/WebGL [3]: http://www.w3.org/TR/html-media-capture/ http://www.w3.org/TR/html-media-capture/ [4]: http://www.html5rocks.com/en/tutorials/geolocation/trip_meter/ http://www.html5rocks.com/en/tutorials/geolocation/trip_mete... [5]: https://developers.google.com/mobile/articles/fast_buttons https://developers.google.com/mobile/articles/fast_buttons