Cross-terminal Web and terminal web

Cross-terminal Web and terminal web

I recently tried to read some of the chapters in the book "cross-terminal Web". It is a good habit to get a book and record what I learned after reading it.

The title is "cross-terminal Web first", which is the most appropriate for me. Before that, my Web development was based on PC Web pages. I hope to have a good start and a good depth.

At the beginning of this book, the author points out that he will talk about "cross-terminal" rather than "cross-device". We often hear "cross-device" (or "cross-platform "), the first impression of this word is that this page can be opened on both PC and mobile devices, in most scenarios, "cross-terminal" and "cross-device" can be replaced with each other, but there are some minor differences. The author has already made it clear that, "Cross-device" is simply to adapt to different clients, and "cross-terminal" may be subdivided into Device Applications, in different applications, including browsers, should be able to open normally (at least I understand it ).

"Cross-terminal Web" is designed to meet our access experience requirements. We hope it can make the web on the terminal reliable and interactive. Of course, it must have a good display effect, we don't want him to be as boring as the previous wap web page, which may be a bit difficult, because it needs to adapt to different devices and applications, including different screen widths, different operation methods.

The author clarified a concept-"mobile first. The concept of "mobile first" covers the surge in mobile traffic, focusing on the nature of business, and the expansion of human-computer interaction. Mobile devices are becoming more and more important to people, and people are increasingly dependent on mobile networks, this trend is even more important than PC. In the past, people designed web pages first to design PC web pages and then to design mobile Web pages, even only the web pages on the PC end are designed. the compatibility of these web pages on the Mobile End often fails to achieve the desired effect. Focusing on the nature of the business is the core of this concept. Imagine that we need to plan well to move the business of the entire website system to a small mobile screen, we need to display the core business to users on the screen. But human-computer interaction expansion is even more cutting-edge. At present, most of this aspect may belong to mobile terminals and tablets.

The author also mentioned several methods for implementing "cross-terminal web", especially "response". Before reading this book, I, not just me, may still have many people, all of them regard "responsive" as "cross-terminal". In fact, it is only one of the methods to achieve "cross-terminal, the "responsive" requirement is that it must be compatible with different devices and be displayed on various screens of different sizes. Because of this self-adaptation, it is no wonder that many people regard it as "cross-terminal ", it seems to be easy to use, but its problems are also obvious, which limits it. I think it is not suitable for use on large website systems. Otherwise, that will make people dizzy.

I also mentioned several other methods to achieve "cross-terminal": multi-site, multi-template, and multi-platform. What about the solution? Each method has two sides. Maybe we can refer to the methods of big companies-using multiple solutions at the same time.

The following sections may have good content.

What is mobile terminal web? I am a newbie. Could you give me an analysis?

I learned programming there. Now I work in a company, and I don't earn much money. In short, IT is a hot topic. This course is designed and recorded for web development engineers who currently have the most needs for Internet companies.

What are the differences between remote desktop access and TS Web access on the terminal server?

The Remote Desktop running program (mstsc.exe) of the local server does not need to run the program on the Web page.