powernerd / bwa-u4-feature-request Goto Github PK

When adding an audio playback feature, users should always have a clear indication of what is playing and a way to easily stop it. In the case of a very long list of search results, it may be difficult to find the currently playing track in order to stop playback after scrolling around. Perhaps there should be an always-visible status bar added to the application. This status bar will enable the user to quickly see what’s playing and stop it.

Yes! 💯

Absolutely. Don't make the user have to scroll for a song buried deep within a list in order to pause a song. Or have to play another song in order to pause that song when really they just need to quiet their browser altogether.

Granted, you've made a valid point that the current number of search results is not great enough to warrant the concern of the user not being able to find playing track... But is this number of search results optimal to the user?

Keep exploring this caveat. Consider the most simple UI that will clearly communicate to the user that they have control of the currently playing track while also giving them the most utility for their goals.

The Spotify Web API includes this easy to use audio sample URL in the track schema described here: https://developer.spotify.com/web-api/object-model/#track-object-full

Excellent work researching the Spotify API to figure out how you might you implement this feature.

Playing one Track will need to automatically stop playback of any other Track. Since we will be only playing one track at a time, we can have the Play / Pause methods reside in App/App.js.

Great thinking. You definitely don't want multiple tracks playing over eachother. There should definitely be a single component keeping track of the currently playing track. The play button on the individual Track components can just set or reset the state of the App component 👍

Enable users to hear audio samples right from the search results list.

Excellent idea for a potential new feature 👍

Users may feel uncertain about the content of a track when adding items to their playlist.

Enable users to make better musical selections.
Encourage users to give various unknown songs a try.
Keep users engaged in our application.
Prevent tabbing back and forth between our application and an optional player application.

These are all great motivations to implement this feature.

It's definitely a flaw in the current application that the user may need to commit to saving a song to a playlist before being certain that that's the song they're interested in. Likewise, keeping a second tab open to play some song is just not an attractive solution when wanting to quickly create a playlist.

Great working putting thought into this feature 👍