Duration
6 Weeks
Methods
Product Design
iOS Development
User Testing
National Public Radio (NPR) is a media organization that produces and distributes news and cultural programming on both radio and digital platforms.
My Role
I worked with a project manager and designer on NPR’s iOS playlist feature, and coded a native iOS prototype for user testing. I coordinated with our user testing facilitators at Applause to install the iOS build on user testing volunteer phones.
Design Challenge
When NPR relaunched its news app in spring 2018, the playlist feature was removed from the design. Based on the feedback and the vocal support for the playlist, the decision was made to bring back the playlist and the design team quickly created a set of designs that needed to undergo testing.
In an effort to streamline the NPR News app experience, the decision was made to remove the playlist feature (shown on the right).
Because we were taking a feature that had existed previously, it was crucial to recruit users who were familiar with our previous app. We created a native iOS prototype that our users who were located all around the US would be able to download onto their phones.
Insights
Values of a Coded Prototype
The prototype offered real iOS features such as a functional tab bar with separate screens, buttons with working outlets, and the key feature for testing:
a playlist where one could add items and edit the queue instantly.
Technical Difficulties
I needed to account for a range of issues, from development bugs to accommodating the different iOS devices that the users owned. Helping users onboard with the app was also tricky - thankfully I had the help of our user testing providers at Applause.
Most importantly,
Because the elements on the prototype were essentially real objects within the app, users didn’t have to follow a specific path to access one particular screen. This also benefited our user testing process as our user testing moderator was also able to keep the script vague enough for the users to explore and discover features for themselves.
Final Thoughts
Work Efficiency & Code Design
Through this process of ongoing development and design iterations, I learned to value my work efficiency: I learned keyboard shortcuts and tools for debugging, as well as routinely reflecting on how to improve my debugging process. Given the short timespan of the project, I needed to balance creating a quick and dirty prototype and also methodically stepping through my bugs so that it wouldn’t be costly in the long run. It wasn’t just about having my program compile–my code needed to retain a clear and readable structure for future development.
An exciting moment where I watched a remote user giving live feedback through the prototype and testing the playlist feature freely.
At the end of the day, a prototype is there to help communicate ideas with your users more easily and help your team identify the pain points that you’re looking to solve. For our team and the resources we had on hand, it made the most sense to use a coded prototype. The valuable feedback we received allowed us to iterate on our playlist design decisions, advocate for the playlist to be prioritized in the product roadmap, and ultimately ship the playlist feature in Fall 2018.