Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing scroll indicator in article list #399

Closed
cemrich opened this issue Aug 30, 2015 · 3 comments
Closed

Missing scroll indicator in article list #399

cemrich opened this issue Aug 30, 2015 · 3 comments

Comments

@cemrich
Copy link
Contributor

cemrich commented Aug 30, 2015

Since the last update (I believe) the scroll indicator of the article list went missing. Scrolling by itself works just fine. I'm using v0.9.6.1 with cyanogen mod 11 (Android 4.4.4).

@David-Development
Copy link
Member

Yes this is correct. I've just implemented a new loading strategy which loads the data on demand e.g. you reach the "end (200 items)" of the list. So the scrollbar would jump then. That's the reason why I disabled it. Is it really needed? Probably we have to find another solution for the progress. Maybe something vertical at the top? (Like the loading indicator in the Detail View?) @jancborchardt @schaal @Raydiation

@cemrich
Copy link
Contributor Author

cemrich commented Aug 31, 2015

I miss it, but I never encountered the "end" of the list where more loading happens. From my perspective a jumping scrollbar should be preferred over no scrollbar, especially when the user will be informed about the dynamic loading at the end of the list. When I understand this issue correctly, the pull to refresh gesture at the bottom of the list would solve this issue elegantly.

I think a vertical indicator would be a poor choice from UX perspective because scrolling a vertical list is strongly associated with vertical scrollbars.

@jancborchardt
Copy link
Member

Yeah, I agree that a jumping scrollbar is better than no scrollbar. It at least gives some kind of anchoring. Of course when using lazy loading, the next batch of articles should be loaded early enough so you are not faced with a loading spinner but the experience is seamless. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants