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

Remove 'previous chapter' button #6568

Open
3 tasks done
keunes opened this issue Aug 6, 2023 · 6 comments
Open
3 tasks done

Remove 'previous chapter' button #6568

keunes opened this issue Aug 6, 2023 · 6 comments
Labels
Functionality: Chapters Needs: Decision Proposal and most arguments are clear, but needs a verdict. Type: Feature request

Comments

@keunes
Copy link
Member

keunes commented Aug 6, 2023

Checklist

  • I have used the search function for open and closed issues to see if someone else has already submitted the same feature request.
  • I will describe the problem with as much detail as possible.
  • This request contains only one single feature, not a list of multiple (related) features.

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:

is a back button really needed for chapter navigation (over timeline)? Not having a back button helps omitting unwanted taps and assumption is, users are listening from left to right so rather unlikely want to go back via the chapter navigation above timeline, resulting in only a forward option being shown.

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

@keunes keunes added Type: Enhancement Good first issue Can be addressed without deep knowledge of the AntennaPod code. But exploring the code may be needed Functionality: Chapters labels Aug 6, 2023
@ByteHamster
Copy link
Member

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)

@ByteHamster ByteHamster added Needs: Decision Proposal and most arguments are clear, but needs a verdict. and removed Good first issue Can be addressed without deep knowledge of the AntennaPod code. But exploring the code may be needed labels Aug 6, 2023
@foss-
Copy link

foss- commented Aug 6, 2023

back button might be useful if you want to listen to the current chapter from the start

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.

@keunes
Copy link
Member Author

keunes commented Aug 6, 2023

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.)

@keunes
Copy link
Member Author

keunes commented Aug 11, 2023

Somewhat related (reduces the risk): #5331

@foss-
Copy link

foss- commented Aug 11, 2023

@distante
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Functionality: Chapters Needs: Decision Proposal and most arguments are clear, but needs a verdict. Type: Feature request
Projects
None yet
Development

No branches or pull requests

4 participants