Choosing the platform
Before any kind of design, we had a major decision to make – whether to design in iOS or Android. Restaurants used Android’s Kindle Fire, while drivers use iPhones. We selected iOS for these reasons:
1. The developer currently develops in iOS, so the familiarity established from the designs will make developing easier
2. Based on research, it’s easier to migrate from iOS to Android. iOS code is proprietary but Android isn’t, making it much easier to develop an app.
What should we bring to life?
Each member of my team created individual style tiles to present to our client. I designed three divergent concepts that encompassed friendliness, organization, and accommodation.
I explored some styles I felt matched our new art direction. The first style resonated well with the client. They felt the blue and green colors blended well. The subtle usage of iconography acted as a prompt in the journey. The client declined the second and third options. They felt its bright colors, outdated graphics, and text felt overcrowded. For my next iteration, whitespace and colors became important to ensure glance-ability and professionalism.
What takes priority?
To make sure our final designs aligned with functionality, we did a few rounds of usability testing with two group of people. Restaurant users were mostly managers that like to quickly track their orders, while the driver’s point of view is based on simplicity in the text, maps, and finding items quickly. These tests will answer a few key questions in mind:
1. Is glanceability achieved with the combination of color, white spacing, and text?
2. Does the user understand what to do?
3. Are too many options given that will confuse and increase learning time?
Get initial showing perspective on Restaurant
We conducted a 20 sec gut test to get initial reactions from users on Restaurants Interface: