Answer the question
In order to leave comments, you need to log in
Page navigation or loading?
Page navigation or loading?
What is better to use on the site?
Desirable pros and cons in terms of:
- programmatic point of view
- from the point of view of PS (SEO)
- from the point of view of the user (convenience, personal opinion)
Thank you in advance!
Answer the question
In order to leave comments, you need to log in
Definitely pagination. It will be better on mobile devices. And then I remember the brainstorage scrolling down and the iPad starts to slow down, accidentally poked from the edge, and he lifted it up. I loaded a lot by scrolling down, but it already hangs and closes the browser. And it’s easier to navigate, remember that yesterday there were 3-4 pages, today you scroll through 3-4-5-6. And don't miss your eyes.
Again, it depends on the project, if these are pictures for schoolchildren, then it will go like that, by loading. And if there is serious content, then pagination.
of course it's IMHO
Obviously, if there was something better, then the other would not be used.
The question is very general. It all depends on a combination of the factors listed in the question.
- How quickly a particular team in a particular project will be able to implement.
- How much a specific project depends on search engine optimization and how labor-intensive it is to make friends with approaches
- What is more convenient for target users
For example, twitter, at least once upon a time, rendered the first page in a standard way, and then it worked like a SPA.
Why does everything depend so much on the project? For example, Yandex published an article on Habré, where they checked what was faster - to render JSON on the client or to transfer pieces of HTML over the network. It turned out that in their case it is faster to transfer HTML, because in a particular situation, the user channel was good, and rendering so much JSON took a long time.
I'll add my two cents for convenience.
Such a funny thing happens, even on fairly popular resources.
There are a number of links in the footer that are not duplicated at the top of the page. And there is no standard page navigation on the site. So, when you try to get to this footer, then, of course, nothing comes out, it constantly runs away. It looks very funny.
The browser may start to slow down if there is a lot of content, or even crash completely.
Perhaps it makes sense to implement this "fashionable feature" where there is a constant flow of operational information and it is not very important what happened a week or two ago, because. it's comfortable. If clear navigation through a certain set of information is required, then this will be quite difficult to do. Alternatively, you can make a separate page for the archive with standard navigation.
Not necessarily either pagination or endless scrolling.
You can make pagination for the search engine, and endless scrolling for users.
Look at the post about the correct pagination in the product catalog . Perhaps you will also find something interesting for yourself. In particular, the issue of paginator design is also touched upon there.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question