The first knowledge of cross-terminal web

It is a very good habit to probation a section of the book "Cross Terminal Web" in the near future, both to get the book and to record what is harvested after reading it.

The title is "first knowledge across the terminal Web". For me the most appropriate, before this, I do the web development is based on the PC Web page, I hope I can have a good start, good depth.

At the beginning of the book, the author points out that the next thing he wants to say is "cross-terminal" rather than "cross-device", and we often hear the word "cross-device" (or "cross-platform"), which gives us the first impression that the page will open normally on the PC and on the mobile device. "Cross-terminal" and "cross-device" are often interchangeable in most scenarios, but with subtle differences, the authors have made it very clear that "cross-device" is simply about adapting to different clients, and that "cross-terminal" may be subdivided into device applications, including browsers in different applications. Should be able to open normally (at least I understand that).

"Cross-terminal Web" is designed to meet our requirements for an access experience. We want it to make the web on the endpoint reliable and interactive, of course. Also have a good display effect, we do not want him like once WAP Web page as dull, this may be a bit difficult, because it to adapt to different devices, different applications, here contains different screen width, different modes of operation and other differences.

The author sets out a concept--mobile first.

The concept of mobile priority covers the growth of mobile traffic, focusing on the nature of business and human-computer interaction expansion. Mobile devices are becoming more and more important to people. And people's reliance on the mobile network is growing, even beyond the PC, not only that, the trend is still maintained, its importance is self-evident. In the past, people designed web pages to design mobile Web pages that were designed for PC-side web pages. Even if you just design a PC-side Web page, the compatibility of these pages on the mobile side is often less than ideal.

Focusing on the nature of the business is at the heart of the idea, just imagine. We want to move the entire site system business to a small mobile screen. This requires very good planning, we have to put the most core business on the screen to show to the user. The human-Computer interaction expansion is the forefront, for the moment, I am afraid that most of this aspect belongs to mobile and tablet.

The author also mentions several means for us to implement "cross-terminal web". In particular, "responsive" is mentioned. Before I read the book, I was. Not only I, but also a lot of people, will be "responsive" as "cross-terminal" it. In fact, it is only one of the means of achieving "cross-terminal". The "responsive" requirement is to be compatible with different devices. It should be displayed on screens of all sizes, because of the self-adaptation, it is no wonder that very many people will consider it as "cross-terminal". It seems to look very useful. But its problem is also very obvious, which also limits it, I think it is not suitable for large site system use it, otherwise, it would have to let people see dizzy dizzy.

The author also mentioned several other ways to achieve "cross-terminal" is multi-site, multi-template and multi-platform, then the solution? There are two sides to each approach, and perhaps we can take a big company approach-using multiple scenarios at the same time.

Perhaps the following chapters will also have good content.

The first knowledge of cross-terminal web