-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
Buttons/gestures to go to next/previous article #382
Comments
Most common request is swipe horizontally. Personally I don't want it but I can see how others could. Any solution would be complicated though (in code) because of the question: what's next? it would depend on how you navigated to the story in the first place. so adding ux tag |
How about a 2 finger swipe? |
As the article is always navigated to from some kind of list (list of one feed, of a feed group, ...) it would make sense to me to remember this list and go to the article which is below the current one in this list. There should be an option to decide if read articles in the list should be skipped. The option could be placed in the options menu of the article view.
I would prefer something that can be done with the thumb only while holding the phone with one hand. My personal idea would be an additional navigation bar at the bottom of the screen, permanently visible, with one button left for previous and one button right for next, both buttons spanning over the half width of the navigation. Position of the buttons may be switchable for left-handed people. Horizontal swiping is of course another option. |
Checklist
App version
2.6.32
Where did you get the app from
F-Droid
Feature or improvement you want
When viewing a single article there should be a way to go to the next or previous article (maybe only to an unread article) using additional navigation buttons (and/or maybe a gesture) without going back to the article list first and selecting the next article.
Why should this be added?
It can avoid the tedious "back to article list, select next article" routine.
Screenshots / Drawings / Technical details
No response
The text was updated successfully, but these errors were encountered: