What is a single page application?
A single-page application is an application that runs in a browser that does not reload the page during use. Like all applications, it is designed to help users complete tasks such as "writing a document" or "Managing a Web server." You can think of a single page application as a rich client loaded from a Web server.
What are the benefits of a single page application to a traditional Web site?
Compared to traditional web sites, we think that the main benefits of single page applications are:
It provides a more compelling user experience. Single-page applications can do both: the immediacy of desktop applications and the portability and accessibility of web sites.
Single-page applications can be rendered as desktop applications-one-page application only needs to redraw the parts of the interface that need to be changed. By contrast, many user actions redraw the entire page, and as a result, when the browser gets the data from the server, the page is suspended from animation and has a "flashing" phenomenon, and then redrawing everything on the page. If the page is large, the server is busy, or the network connection is slow, the "flashing" phenomenon lasts for several seconds or even longer, and users have to guess when the page will be used again. This is a scary experience compared to the quick rendering and instant feedback of a single page application.
Single-page applications can have the same response speed as desktop applications-moving (temporary) work data and processing from the server to the browser side as much as possible, minimizing the response time from a single page application. Single-page applications have most of the data and business logic needed to make decisions locally, so it's quick. Only data validation, authorization, and persistent storage must be on the service side, as we discuss in chapters 6th through 8th. Most of the traditional Web site application logic on the server, for most of the user input response, they must wait for a "request/response/redraw" cycle. This takes a few seconds compared to a single page application that is close to instant response.
A single page application can be used as a desktop application to notify the user of its status-when a single-page application does have to wait for a response from the server, it can dynamically display the progress bar or busy indicator, so the user is not confused by latency. Compared to traditional Web sites, users can actually only guess when a page is loaded and available.
See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/web/Skills/
Single-page applications, like networks, can be accessed almost everywhere-unlike most desktop applications, users can access a single page application through a task network connection and an appropriate browser. Today, the list includes smartphones, tablets, televisions, laptops and desktop computers.
A single page application can be updated and published as quickly as a Web site-users do not need to do anything to understand its benefits: they simply reload the browser. The hassle of maintaining multiple concurrent versions of the software is largely eliminated. Authors who develop a single page application can build and update many times in one day. Desktop applications often need to download and install new versions that require administrative access, and the gap between versions can be many months or years.
Single-page applications, like Web sites, are cross-platform-unlike most desktop applications, well-written single-page applications can run on any operating system that provides a modern HTML5 browser. While this is often considered a benefit to developers, it is useful for many users who use multiple devices at the same time, such as working with Windows, home mac,linux servers, Android phones and Amazon tablets.
All of these benefits mean that you might want to make the next application a single page application. After each click will be a full page of the clumsy Web site, easy to increasingly alienated experienced users. A well-designed single-page application has an interactive and responsive interface with access to the network, which helps us keep our customers where they belong: using our products.
About single-page Web applications
One-page Web application (Single page Web Application,spa) is undoubtedly the current web development technology of the people, many traditional sites are or have been transformed into a single-page Web application, New Single-page Web application sites (including mobile platforms) have sprung up in front of people, such as Gmail, Evernote, and Trello. If you're a web developer who hasn't developed or even heard of a single page application, you've been out for a long time.
Single-page Web applications are closely related to front-end engineers because the main change occurs in the browser side, the technology is actually html+css+javascript, all browsers are natively supported, and of course some browsers have advanced features This enables a single page Web application user experience to a higher level. On the advantages and disadvantages of one-page application, there are a lot of articles on the Internet, this is not discussed. A single page Web application, as the name suggests, is only one Web page application. The browser initially loads the necessary HTML, CSS, and JavaScript, and then all of the operations are done on this page, which is controlled by JavaScript. Therefore, a single-page Web application will contain a lot of JavaScript code, the complexity is conceivable, the importance of modular development and design is self-evident.
This digest is from the upcoming "one-page Web application: JavaScript from front to back"
Author: csdn Blog Chi-min