Music Event App MVP

Rapidly designing a music event app

I was tasked with designing a search mechanism for an Electronic Dance Music (EDM) events app for people in the Netherlands.

  • Duration and Team: 1 day, 1 designer
  • Tools: Pen and Paper, Adobe Photoshop, Keynote

Discovery and Definition

The app is for EDM music lovers in the Netherlands to help them find events to go to. I started by investigating what else was on the market and getting to know the common interactions for apps that principally work off search and listing items.

I looked to answer these questions: 1) What are the ‘standard’ or intuitive ways of performing search in an iOS app? 2) What use case(s) are we trying to fulfil, and 3) what is the quickest way to getting to a minimum viable product?

I put together a user journey to under the sorts of decisions they would have to make.

Design and Testing

Sometimes I find thinking visually to be a powerful way of communicating possible solutions. This was the first sketch I made, identifying search, location-based search and listings. I went on to further understanding the user journey and discovering more about what the user will have to choose further on.

Once I had defined the needs of the project, I started sketching out solutions, ready to move on to the user interface design.

I now started to craft the user interface. Using Adobe Photoshop, I kept to a minimal palette, native styling to an iOS app and kept to common conventions to ensure that users could pick up the app easily.

The next morning, I iterated upon some of the forms I had used in the search area and pieced together the screens within a prototyping tool. I finally left some ideas for further iteration.

I tested the iOS app with a couple of users in InVision to understand the intuitiveness of it and whether they recognised the key interactions I had decided upon.


I noted in the design exercise that I should revisit the MVP criteria to ensure that we have achieved the MVP. Further usability tests would also help us understand whether we had achieved this. Finally, I noted that to continue development, we should use LEAN UX and Build, Measure and Learn to discover new hypothesis to test to.


In the retrospective, the agency loved my approach to solving challenges and the way I had communicated my ideas. I recognised the caveat to the project — I was doing this in isolation and that’s a far from perfect situation to be in. I wasn’t able to interview potential users or stakeholders or consider user needs authentically. However, had this been a real client project, gathering feedback during and after release would have been the right way to iterate the feature post-launch.

Show your support

Clapping shows how much you appreciated Ross Chapman’s story.