On the mobile side, we've found:
1. Fetching is harder than scrolling
2. Different devices can support different sized lists; keep the list
size smaller than the max size for the device (surprise!)
3. Applications can do dynamic loading of lists ... see the Gmail app:
when you get near the bottom
2008/10/2 David Farkas [EMAIL PROTECTED]:
… I am curious as to what
guidelines others use to determine when a list is too long and when the
'view more' link should be implemented within these two different
applications.
As a side-issue you might want to consider using a link title like
The article The Impact of paging vs. scrolling on reading online
text passages of The Usability News is still available with .asp
and not .html...
http://psychology.wichita.edu/surl/usabilitynews/51/paging_scrolling.asp
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted
I do a lot of work developing interfaces that provide similar material in
both standard browsers and mobile devices. A lot of the data lends itself to
lists such as dates, events, and what not. I am curious as to what
guidelines others use to determine when a list is too long and when the
'view
