ITADN

Reconsider concept of User Queue and Context Queue

#688Openbhajneet 创建于 2026-05-01
B
bhajneetcommented
<img width="1920" height="1049" alt="Image" src="https://github.com/user-attachments/assets/d59ff755-9214-4560-bd81-e7d18aadce71" /> The idea of a "queue" is that you're playing something. Currently this playlist is referred to as User Queue. In this User Queue (when looking at the inspector, which really is just a "queue" playlist viewer), there is for no apparent reason a "previous" and "next" section. The User Queue could easily just be a single list and have an indicator for what is currently playing. <img width="263" height="391" alt="Image" src="https://github.com/user-attachments/assets/325524d5-d5c4-4dfa-a0c7-34e0e09eccd5" /> It could look just like this and be a lot cleaner. Use the album art on the left hand side, no problem, just overlay this "playing" icon. If I add the same playlist to the User Queue, I get this: <img width="1920" height="1049" alt="Image" src="https://github.com/user-attachments/assets/c2376ce0-f151-4a02-8fa9-01c5123b80eb" /> Hitting "next" in the bottom bar, just removes these from the Queue (does not go to the "previous" list) and actually "appending" the list did not append to the user queue. It ended up being the next up. So what is "user queue"? Clearly it's not defined properly. In addition to all this confusion, there is a "Context Queue", which is something that is auto-generated ? I'm not sure what this is. But it doesn't need to be something we append to or insert above of. Just let us create our own "queue". And from that Queue we should be able to create playlists and such. Suggest looking at YouTube Music more than Spotify for this. Spotify has plenty of issues with their Queue system as well. For example try shuffling things around and playing them, then try going "back" on Spotify. It let's you infinitely go backwards (and not in the same order you were playing). It doesn't have a proper concept of a queue. However YouTube Music does. You'll have your playlist/queue at the top and then an "autoplay" section below that. You can "play next", "add to queue", and "remove from queue". My two cents, do the same thing here for simplicity and clarity. Have a "Queue" which is what you're playing (whether it's an album, artist, directory, etc.) have that labelled as Queue or "Now Playing" in the inspector (which should be renamed Queue honestly). Let there be a context menu on that title for Queue/Now Playing which can have options such as: - Shuffle - Repeat - Save as Playlist - Download / Cache for Offline Use - Toggle "Autoplay"? - Clear (resets Queue to nothing) Below the users queue just have the contextual queue, but don't let us mess with it. Rather let us pick items from there to add to user queue ("play next" or "add to queue" makes it more obvious where it's being added. It shouldn't be "top" or "bottom". The queue should be a flat list. If I'm listening in the middle and then pick "play next" it should add it to the queue after my currently playing item. These are my subjective ideas, so please feel free to pick and choose what you like, modify it, or dismiss the whole thing! Personally do not believe that "contextual queue" should be a concept in this app. But that's because I don't see the point of it. It will simplify another menu for you too, you can just make it two items instead of a nested menu: <img width="468" height="336" alt="Image" src="https://github.com/user-attachments/assets/574ed498-7232-4ca5-aec5-4aa0aaab86ee" /> Music Queue could just be replaced with: - Play Next - Add to Queue
0 条评论