The idea of a good web mobile application framework

Web page Production WEBJX article introduction: Web Mobile application framework concept.

IUI, JQTouch, Wptouch, PhoneGap, Xui, Iwebkit, Rhodes, Gwt-mobile ... When we've started to marvel at the fact that Web mobile apps are flooded with a variety of frameworks and libraries, the big Web frameworks are just beginning their mobile domain: Yahoo's YUI3.2 touch version, jquery's Jquerymobile, ExtJS integration Jqtouch and Raphaël Library launch of the Sencha touch frame ...

ExtJS renamed to Sencha indeed let me shocked a lot, after all, I was also a extjs frame fans, such a heavyweight framework suddenly turn to mobile touch direction, it is not an easy thing, we can not help but marvel at mobile applications brought about by the major changes.

OK, I'm not here to tell you about the usage and performance comparisons of various Web mobile application frameworks. Just being influenced by ExtJS and wondering how far I've come to, and the better accumulation of the front-end experience, I began to think about how a good Web mobile application framework should be and start trying to get started. Repeating the wheel is just forcing yourself to learn more about the field, not the arrogance to challenge anything. So the analysis of the comparison, summed up as follows:

1. Lightweight

This should be the most important mobile application framework, do not think about the popularity of 3G and WiFi What, the national conditions are national conditions, to a large department users in 3 seconds to download your 100K of CSS and JS file is an imposition. So our mobile application framework must be as lightweight as possible, and all the naming and function implementations should be as concise and highly compressed as possible. Throw away the effects and components of Web apps on your PC, and don't add 7,80k jquery.js to your page for a menu effect.

2. Mainstream mobile browser compatibility

With so many mobile platforms and browsers, it's hard to make your mobile apps behave like all browsers, and sometimes you need to load different style files for different browsers, or function differently to achieve results. So our framework must have a way to identify the various mainstream browsers, specifically, your framework must be able to differentiate such as iphone, IPad, Android, Windows phone, OK, then a little more national, QQ Mobile browser and UCWeb. The final note is here as far as possible without the AU method to judge, because the avigator.useragent of the browser are very unreliable, here you can refer to the next mooltools to judge the idea of the browser, applied to our mobile field.

3. A powerful selector

Selectors can be said to be a framework soul, in future Web mobile applications will use a lot of CSS3 advanced pseudo class, so our framework must be able to traverse as soon as possible to navigate to as many HTML5 tags and CSS3 pseudo class, even if it is like E: First-of-type this kind of jquery selector does not support the structure.

4. Page animation effect

Unlike desktop Web apps, mobile apps have a lot more to do with page transitions, such as: sliding, masking, fading, flashing, zoomin,zoomout effects on the iphone. Look at the CSS definition of Fadein and zoomin animations:

[1] [2] [3] [4] Next page