3 ms·
What's the point? The two example native components don't seem to do anything that HTML5 can't do just as easily/effectively. Do they somehow get you better per
by kevingadd 15y ago
What's the point? The two example native components don't seem to do anything that HTML5 can't do just as easily/effectively. Do they somehow get you better performance/responsiveness on Android/iOS by not going through the browser stack?
- amirnathoo 15y agoThe point is to get better results for the same effort. Instead of having to spend time styling the top bar and tab bar to look native, and battling with fixed positions and mobile browser inconsistencies, you just drop a line into your config. Many people seem to think fixed position elements and dealing with scrolling in mobile web views is a pain: http://bradfrostweb.com/blog/mobile/fixed-position/ http://bradfrostweb.com/blog/mobile/fixed-position/ http://www.kylejlarson.com/blog/2011/fixed-elements-and-scrolling-divs-in-ios-5/ http://www.kylejlarson.com/blog/2011/fixed-elements-and-scro... http://blog.millermedeiros.com/ipad-is-the-new-ie6/ http://blog.millermedeiros.com/ipad-is-the-new-ie6/