Back to Top

Dream City Music

In late 2017, Dream City Music wanted to build a performance management tool for its growing number of 100+ contracted musicians playing at various venues and events. I was responsible for designing and building the performance management tool through production.

Dream City Music mockup banner

Roles

UX & UI Designer, User Researcher, Front-End Developer

Timeline

10 months

Team

Bennett Huffman, Dream City Music

Tools / Methods

Sketch, Flinto, HTML/CSS, Ionic Framework

Vision

Create an internal performance management tool for 100+ contracted musicians.

Discover

Overview

Dream City Music (DCM) is a live musician service that provides live music for weddings, parties, corporate events, and more. DCM hand-picks auditioned musicians and curates the perfect ensembles for client events. Our founder, a self-taught coder, already had a web application for clients and an internal management system for musicians. However, many musicians need to access information on-the-go, and the web application was not designed to accommodate for quick access to performance details or facilitate communication between musicians at gigs. How might we solve this?

This is exactly why we built a mobile application, enabling musicians to accept performances faster, find important performance details, facilitate easier communication, and manage their respective accounts.

Define

Defining User Needs

Knowing our users is incredibly important. We had many discussions with the musicians, including our experienced musician/founder to guide me through user needs and requirements. Walking through his needs as a freelance musician helped construct a list of features and base functionality required of the mobile application.

Features

Information Architecture

I used this information to sketch out a site map illustrating a general structure and navigation of the different pages.

IA diagram

Design

Low-fidelity Wireframes

I first sketched out multiple solutions for each feature and page of the application.

Sketches

Mid-fidelity Wireframes

I then created greyscale mockups after reviewing the low-fidelity wireframes with the founders to ensure they made sense, fit the requirements, and would be intuitive for musicians. I started using Justinmind but switched to Sketch for higher-fidelity wireframes.

Wireframes overview in Sketch

Interactive Prototype + User Testing

After creating the first round of high-fidelity mockups for the app, I put together an interactive prototype in Flinto to test on musicians. I sat down with two currently on the platform that would be beta testing the app to get feedback.

User testing

After a combined 90 minute session with musicians, we received very positive feedback, but also some notable suggestions. We wrote down thoughts, improvements, and potential features for future releases to iterate on before building the final application.

Some changes reflected from feedback include:

Other requests, such as dark mode (due to eye-strain in low-light venues), were labeled as v2 features.

Deliver

Final Prototype

I created a final interactive prototype for the deliverable, and went on to develop the app over the summer using the Ionic Framework.

Reflect

This was my first mobile application. The process was enlightening. Looking back, there’s lots of things I would do differently, but that’s a part of the learning process.

I was able to share this experience with 110+ community members in my high school through my capstone presentation senior year, speaking about entrepreneurship and product development as student-creators.

Unfortunately, we ultimately decided not to move it onto the app store—instead we created BookLive to make performance management available to everyone. DCM is now managed on BookLive, where I designed an even larger-scale performance management effort. I’m incredibly amazed at what we’ve accomplished to help hundreds of musicians around the country. :)

Check out that project here.