maxrave-dev / maxrave-dev/SimpMusic
Improved Queue Management for Playlists
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 11.4k
- Forks
- 599
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 7
Description
Problem:
When adding multiple songs to the queue using "Play Next," songs are inserted in reverse order compared to the selection.
Songs added with "Play Next" do not appear visibly in the queue, which creates confusion about what will play next.
Using "Add to Queue" adds songs at the end of the queue, forcing users to wait or rely on shuffle to hear them.
Proposed Solution:
Allow "Add to Queue" to insert selected songs immediately after the currently playing song, preserving the original order of selection.
This behavior would be similar to the functionality found in Spotify, where "Add to Queue" places songs directly after the current track, providing a clear and predictable listening experience.
Additionally, improve the "Play Next" feature by making songs added this way visible in the queue interface, so users can easily see and manage what will play next, reducing confusion and enhancing control over playback order.
Current Workaround:
Adding songs one by one with "Play Next," which is inefficient for multiple songs.
Additional Notes:
The behavior of "Add to Queue" changing to "Play Next" when "Endless Queue" is enabled is confusing.
Suggest making this behavior optional in settings, allowing users to choose default actions.
Consider implementing swipe gestures (e.g., swipe right for "Play Next," swipe left for "Add to Queue") for easier control.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Play Next and Add to Queue actions and the queue interface, then check how Endless Queue changes their behavior. Clarify the intended scope before implementation, including selection order, queue visibility, optional settings, and swipe gestures. Done should make queue placement predictable and make Play Next items visible for management.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100