Some hard skills of mobile web Front-end (1) about mobile devices and web Front-end

Some hard skills of mobile web Front-end (1) about mobile devices and web Front-end

Mobile web is actually the web of small-size touch screen devices, which contains two words: 1. Small-size devices; 2. Touch Screen. If you can solve these two problems, you are already a qualified mobile web Front-end development engineer. For front-end engineers, the road ahead is long, the development is too fast, and there are so many things to learn. It is right to learn anything. However, we have to step by step. Next we will discuss some of the hard skills necessary to become a mobile web Front-end engineer.

 

I. Differences between Touch devices and desktop Devices

Mobile terminals are mainly mobile phones, small tablets, and large tablets. One of these three types has numerous sizes, and browsers are displayed in full screen on these devices, therefore, the problems with mobile terminals mainly lie in the matching between devices and the adaptation between horizontal and vertical directions.

Desktop devices, that is, PCs. browsers can adjust the size at will. Different sizes do not have an obvious span and can be controlled in segments. Different parsing engines exist between desktop browsers, therefore, browser compatibility is the biggest problem.

Conclusion: mobile web focuses on the device size, while desktop web focuses on compatibility with various browsers.

 

Ii. Hardware problems

Mobile terminal hardware is much inferior to PC hardware, and its computing power is also weaker than PC. Therefore, for mobile web Front-end, the performance should be considered more, but the performance should be considered less, performance is much worse.

 

Iii. user perspective

PC users have a strong sense of purpose, such as work, entertainment, learning, and so on. They spend a whole period of time using them. Therefore, users will spend a certain amount of time waiting while mobile terminals are different, most mobile terminals use fragment time, so users do not spend much time waiting for empty page loading, as fast as possible.

 

Iv. browser kernel problems

Currently, most mobile system built-in browsers are webkit kernels, including iOS, Android, and blackberry, but windows phone 8 is IE10, but HTML5 is also supported. The support for HTML5 is not the same as that for parsing. The standards are the same. Therefore, we will still see many "abnormalities" during testing, and these "abnormalities" are developed on the PC, that is to say, using the simulator can not find the problem, but can only guess, infer, This is a headache. By the way, there is also a browser Opera mobile, Opera browser that performs extremely well on the pc, because of its powerful error correction capabilities, which I used to love most, but some of them are shown on mobile terminals, when I first started to build a mobile terminal, I used its mobile simulated version to simulate the mobile terminal on a pc. Later I found that some parts need to be processed separately. There is also Firefox, which supports HTML5. It is not a problem that sometimes requires special processing.

 

V. HTML standards

Mobile Terminals almost fully support HTML5, so you don't have to worry too much about unsupported features. However, because HTML5 standards are determined late, browser vendors try to implement them earlier, so there will be some specific prefixes or some features that you open separately. As the specifications are determined, they will become more and more unified in the future.

However, I still see a lot of mobile web statements using HTML4.0 and XHTML1.0. I have to say one thing here-now there are scripts to implement pc-to-mobile conversion, in fact, this should also happen. Of course, if they can be properly displayed and operated, these are not big issues, but they may be an obstacle for future upgrades.