User Testing and Wireframes
Process and User Interview Testing
I presented three ideas for a potential feature for more exposure and engagement for the Music category to 2 viewers and 2 creators that use Twitch.
During the ideation process I was testing key screens:
Left to right:
One is requesting songs to be played by a music creator through modal/pop up screen.
The second approach users can request songs to be played in a toggle on the chat.
Thirdly, a similar idea was creating a collaborative playlist regardless of a streamer playing the requested songs. The songs are played live and users can suggest next songs. These are lo-mid fidelity wireframes of the song request presented idea and a mid-hi fidelity sketch:
Key Learnings:
- 100% preferred the song request idea rather than the collaborative playlist feature
- 100% appreciated the "liking"/ "bidding" on songs to get them into a queue for control purposes
- 100% preferred the new feature attached to the chat as a toggle
- 50% disliked creating a new gamification currency/points that is purely related to Music.
- 25% valued additional interactions such as 'play song again' and more
Design Iterations
Feature Scalability Improvements
While designing and journey mapping it occurred that there might need to be improvements since new problems were needed to be addressed in relation to the feature.
Challenges:
Scalability - What happens if there are more than 400 viewers in the stream?
Threshold - How many songs would be queued if everyone liked all the songs suggested?
Opportunities:
Channel Points - for liking and suggesting new songs channel points will be reduced.
Time - Open song request time limit by creator and there will be a time limit for a song to be liked upon