When a song ends and the next one begins, there is ambiguity in how the AudioView should update. It currently displays the last navigated file, but automatically progressing to the next track raises questions about the appropriate behavior of the interface.
Considerations:
Updating the SharedUI to reflect the current track could provide a seamless experience, though this requires synchronization between components.
Implementing a separate navigation event for the next song could maintain clarity in user actions.
Modifying the page title to reflect the current playing content is a simpler, yet potentially less integrated solution.
Preventing automatic progression to the next track is an option, but this could hinder user experience.
Limitations:
Windows MediaTransportControls lacks a title field for currently playing content, preventing straightforward display of song titles.
Proposed Solution:
A custom media player maintained by the audioservice could overcome this limitation.
Audio Navigation and Playback Handling
Current Challenge:
When a song ends and the next one begins, there is ambiguity in how the AudioView should update. It currently displays the last navigated file, but automatically progressing to the next track raises questions about the appropriate behavior of the interface.
Considerations:
Limitations: Windows MediaTransportControls lacks a title field for currently playing content, preventing straightforward display of song titles.
Proposed Solution: A custom media player maintained by the audioservice could overcome this limitation.