The Watch Lists are actually very long, there are dozens of items, the performance is this: Each page shows only 5, can be displayed in a screen, and then flip.
We know in the design of PC web pages: put more content on a page display, better than the jump page, the user easier to see. A few meters long portal home is so come.
Suddenly the mobile application may be for some designers a little overwhelmed, I feel the phone screen is small, single-finger operation is characterized by, and so I am not very clear reason, finally came to the conclusion that each page Can not scroll. This conclusion is obviously a bit wrong, and it is almost impossible to achieve strict implementation.
Constantly on the next page next page, and then on the previous page, each time you turn pages and need to load a new page, obviously not easy to use, by contrast, "self-selected shares" such a long list will be good some.
To handle a long list, it would be better to scroll up and down than to split multiple pages. Well, this conclusion may be a bit early.
One of the big problems with "short lists + page turning" is that every time a page is loaded, the display of the next page takes some time and is not fluent. For a long list if the scroll is not smooth, will card, of course, people feel uncomfortable, that the short list of pages, you can see it is a bigger card, apparently even more upset.
So, if a short list + page flip, but not card it? Prior to loading, but do not have to scroll the form, each page is not a scroll bar, a page is very smooth turn, is not ok?
Feedly, that's it.
Every page just shows a screen, do not scroll, slide up to the back of a page.
If "short list + page flip" is preloaded, then the difference between "short list + page flip" and "long list" is only that the user's performance model is different: one is a boxed tissue, One; the other is a roll of toilet paper. Both models are easy to understand.
However, similar to http://www.aliyun.com/zixun/aggregation/11189.html"> Feedly this form of expression need to solve an additional problem: If I have turned page 12, then want to go back to see the first 4 Something on the page, how can I get it fast?
For a large page, the current screen can only show part of it, how to tell the user which part of the whole page is currently displayed; what functions should be provided so that the user can efficiently return to the top of the page, go to the bottom of the page, or Reach a specific location in the page. This series of questions on the PC is responsible for solving the scroll bar by the window, not elaborate, we are all too familiar.
The scroll bar in the phone system is degraded, only showing the location of course, but can not provide the operation. Android can make a one-time scrolling farther rolling, IOS point to the top of the seams quickly back to the top, rapid scrolling can also scroll more, but it seems no effect of android obvious. These are for navigation within the page, but also not as powerful as the scroll bar on the windows on the pc.
Feedly cut the whole roll of toilet paper into sheets, turning the original navigation problem in the page into a jump between pages, so that even the little navigation within the page provided by the phone system did not work. If I turn to page 12 and want to go back and look at page 4, I have to go back a few more times, or go back to the first page and then back down three times. Which method is not very efficient.
Because of the small cell phone, the overall design direction is simplified, minus the natural should be a few users, a few times the function will be used. For feedly this mobile version of the reader, most users just look at the news every day, do not need to often find a precise article, you can even say that there is no need to quickly return from page 12 to page 4 features, But other products may be more needed, for example, a list of 100 stocks.
A stock watch list that uses feedly short list + page flip might be able to do its own navigation for its own piece-wise long list service to make jumps between sections more efficient.
Since so troublesome, then simply "self-selected shares" so long list directly, simple, straightforward, but also save those troubles. The simplest form has its simple charm, but it is really a long list of 100 items, from the 12th screen back to the 4th screen is not very fast, it has to roll a few times, and the operation is not easy very accurate, you Also do not expect to roll out in the end a few times.
There may be navigation in the phone's address book, which is quickly reachable by letter, and should probably be used extensively; we may also need to do some separate on-page navigation for our long list, which is not always enough for the common functionality provided by the operating system .
Source: http://ucdchina.com/snap/12755