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
Remove 'previous chapter' button #6568
Comments
Hmm, I think the back button might be useful if you want to listen to the current chapter from the start (eg because you got interrupted) |
While certainly true, this question is somewhat difficult to discuss without metrics. I am sure Marco of Overcast has done his homework when evaluating which element to use in Overcast UI. Certainly that doesn't mean everything has to be copied and I think part of the reason there is no back UI element in Overcast is due to the fact that there is a dedicated Chapter view (without overlay and integrated into the top level UI without interfering or overlapping player controls) along with the option to rewind x seconds. I assume most users would either pause or just go back a minute (instead of the whole chapter) in case of distraction. |
I think so too. (And if they don't, they have 2 already mentioned fallback options: regular rewind and chapter list.) |
Somewhat related (reduces the risk): #5331 |
And the related forum discussion: https://forum.antennapod.org/t/user-feedback-swipe-navigation-from-player-screen-2-3-beta/1119 |
Funny enough, I found this issue because I sometimes mistake the Fwd button with the Next button and there is no Previous button on the android version that I have. |
Checklist
App version
3.0
Where did you get the app from
Google Play
Problem you may be having, or feature you want
As @foss- noted in #6249:
Suggested solution
Remove the 'back' or 'previous chapter' button from the chapter buttons on the main player screen as well as any other place it might be. Both in the UI and in the back-end (code).
Screenshots / Drawings / Technical details
No response
The text was updated successfully, but these errors were encountered: