Originally created by @burntoc on GitHub (Sep 4, 2022).
Describe the feature/enhancement
It would be awesome if you jump elsewhere in a book, or “lose your place” to know the very farthest progress point and to have a one-click method of returning to it. When I’m jogging, for example, sometimes a notification may trigger the screen to pop of the media control and I accidentally skip to someplace else in a book unintentionally. I can’t find any easy way to see that I got to the 4’3” mark of Chapter 5, but now I’m suddenly on Chapter 7 or 3.
I know I can lock the player or use other workarounds but those are really limiting the phone to mitigate something ABS can address. My goto for non-streamed audiobooks was Listen AudioBook player and it would show bookmark-like points from a little “history” UI control that would allow you to select points like this and it could get you back in good shape quickly.
Regarding implementation, I realize it’s not simply record the farthest point as an unintentional skip ahead then makes that the new farthest point, but capturing and showing multiple events in the history would allow you to select the previous “correct” one and requiring some short period of playback after a skip to record that point would prevent the history from showing a bunch of skip events if someone is simply trying to jump ahead several chapters.
Happy to try to explain better if I’ve thoroughly murked this up.
Originally created by @burntoc on GitHub (Sep 4, 2022).
### Describe the feature/enhancement
It would be awesome if you jump elsewhere in a book, or “lose your place” to know the very farthest progress point and to have a one-click method of returning to it. When I’m jogging, for example, sometimes a notification may trigger the screen to pop of the media control and I accidentally skip to someplace else in a book unintentionally. I can’t find any easy way to see that I got to the 4’3” mark of Chapter 5, but now I’m suddenly on Chapter 7 or 3.
I know I can lock the player or use other workarounds but those are really limiting the phone to mitigate something ABS can address. My goto for non-streamed audiobooks was Listen AudioBook player and it would show bookmark-like points from a little “history” UI control that would allow you to select points like this and it could get you back in good shape quickly.
Regarding implementation, I realize it’s not simply record the farthest point as an unintentional skip ahead then makes that the new farthest point, but capturing and showing multiple events in the history would allow you to select the previous “correct” one and requiring some short period of playback after a skip to record that point would prevent the history from showing a bunch of skip events if someone is simply trying to jump ahead several chapters.
Happy to try to explain better if I’ve thoroughly murked this up.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @burntoc on GitHub (Sep 4, 2022).
Describe the feature/enhancement
It would be awesome if you jump elsewhere in a book, or “lose your place” to know the very farthest progress point and to have a one-click method of returning to it. When I’m jogging, for example, sometimes a notification may trigger the screen to pop of the media control and I accidentally skip to someplace else in a book unintentionally. I can’t find any easy way to see that I got to the 4’3” mark of Chapter 5, but now I’m suddenly on Chapter 7 or 3.
I know I can lock the player or use other workarounds but those are really limiting the phone to mitigate something ABS can address. My goto for non-streamed audiobooks was Listen AudioBook player and it would show bookmark-like points from a little “history” UI control that would allow you to select points like this and it could get you back in good shape quickly.
Regarding implementation, I realize it’s not simply record the farthest point as an unintentional skip ahead then makes that the new farthest point, but capturing and showing multiple events in the history would allow you to select the previous “correct” one and requiring some short period of playback after a skip to record that point would prevent the history from showing a bunch of skip events if someone is simply trying to jump ahead several chapters.
Happy to try to explain better if I’ve thoroughly murked this up.
@advplyr commented on GitHub (Jan 14, 2023):
We are going to implement listen history so we'll make #466 the main issue for this