The author of this article @子木yoyo posted it on his personal blog. Whether on a web page or a mobile app, information often cannot be displayed entirely on one page, which requires the use of some interactive modes that can expand page information: pagination and continuous scrolling. Pagination and loading are very common interaction modes that we encounter every day. Precisely because they are so common, we don’t even feel their existence. When we browse to the bottom of the page, we click on the pagination when we see it, and continue reading when it loads automatically. But it is this small point that will bring users a very different and subtle feeling. This article will talk about the big differences these small differences bring. Pagination Pagination can divide large content into small pieces and display them on separate continuous pages, making it easier for users to understand and find. It allows users to clearly know how much content they want to browse, which part they have browsed, and how much is left. Pagination allows users to have clear expectations about the content they are browsing. Longer articles will definitely require pagination. First, it gives users an expectation of how much content there is, and second, it provides a pause for viewers. How frustrating it would be if a user has scrolled through more than ten screens while reading an article and the scroll bar is still stuck in the upper middle of the browser. ![]() ![]() The paging control actually creates a natural pause for the content of the website. If this pause is used well, it can make the product more rhythmic. However, when the user finishes browsing a page, he or she must stop reading and click to jump to get more content. It is undeniable that this pause will interrupt the user's thinking to a certain extent. When encountering pagination, users are likely to think about whether to continue browsing or leave the website. Therefore, when encountering pagination, some users will often be lost. Continuous loading Continuous loading is an interaction mode that is the opposite of paging, with no clear boundaries or pauses between messages. When the page scrolls to the bottom, new information will be loaded automatically. Various social networks particularly like to use this type of control, so users will not be interrupted and can browse smoothly and immerse themselves in it. ![]() When using paging controls, users must click to view more content, so information acquisition is actively requested by users. When using continuous loading, new information is loaded automatically and the user passively accepts it. Compromise method Paging and loading have their own advantages and disadvantages. Many websites nowadays will also take some compromise methods: paging and loading together. For example, Quora will display a “More” button after automatically loading 4 times, giving users a pause after the continuous flow of information, allowing them to actively obtain more information. ![]() ![]() ![]() ![]() ![]() |
>>: Super detailed tutorial to implement Vue bottom navigation bar TabBar
This article records the installation and configu...
Clustering is actually relative to the InnoDB dat...
1. First, let's review the relevant knowledge...
When designing table structures, numeric types ar...
Stored Functions What is a stored function: It en...
Solution to MySQL failure to start MySQL cannot s...
Table of contents Preface - Vue Routing 1. The mo...
Table of contents Function Introduction Rendering...
There are three date types in MySQL: date(year-mo...
In this article, we would like to share with you ...
Table of contents Install tinymce, tinymce ts, ti...
1. Use CSS, jQuery, and Canvas to create animatio...
This article shares the specific code of js to re...
Table of contents MyISAM and InnoDB Reasons for p...
1. Put the mask layer HTML code and the picture i...