-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Make it possible to "bookmark" specific parts of a podcast-episode #989
Comments
This might be a little off topic, but do you really think it is a good idea to interact with your smartphone while driving? ;) |
Please don't get me wrong. I don't want a feature which will distract anyone from driving. Maybe I should have chosen a different example scenario. The feature could be used in many other situations too. However, the interaction of the user with the described feature in an in-car situation could be seen as a challenge. Imagine you could use the media buttons of the steering wheel to trigger the creation of an bookmark. As far as I know AVRCP allows to handle fast-rewind and fast-forward events that could be used for it. |
Duplicate of #851 |
I suppose this may not be an exact duplicate of #851 as it would save the episode time as well. However, #861 is very close to what you describe. You can share the episode with position to yourself. It has the benefit of already being merged in to 1.3. The situation you describe with the media controls in your car would likely be far too fiddly to actually implement. |
Closing this in favor of #1946 |
Imagine you drive in your car and hear some interesting things in a podcast that you like to google later, because you want to read more background information to a specific part of the episode that were not provided in the podcast itself.
I would love to have a button which will create an entry with the playback time and the name of the podcast-episode which was played. This would give me the possibility to hear the minutes around the "bookmarks" again after I arrived at home.
The text was updated successfully, but these errors were encountered: