Contract UX Design and UI Design for a Web and Mobile App for Travelers

UX Design, UI Design

The Project

My client had a remarkable travel product, with powerful technology and a top-notch team. When an unexpected make-or-break opportunity emerged on the horizon, they needed a user experience and interface design that was intuitive and conveyed the power and polish of the technology under the hood. And they needed it fast.

In this case, I'm not able to disclose the client. The work shown here has been altered and anonymized from it's original form, and the actual application design has matured greatly since this draft, under the expert direction of their growing internal team.

Results

The opportunity was successful, and as a result, the client is thriving.

The User Experience

The client's team had an excellent understanding of their primary users based on careful research and direct experience. We used that information to create early workflows that touched on each element of a successful experience. The design accounted for many roles, interrelated objects, scheduling, and user-provided content. This was a complex undertaking. And with the clock ticking, there was no margin for error.

Due to the client's preference for anonymity, and the strategic detail included in these early design documents (that would be too time-consuming to anonymize), I'm not able to include pre-final strategic UX deliverables in this case study.

Web Application UI

Working closely with my clients, I designed a sleek, flexible interface that allowed our client to build in increments, refine the design of each element independently as feedback was collected (a necessity with such a quick process), and maximize the experience for a wide range of user types and use cases.

iOS App UI

I designed a native iOS app as a counterpart to the web application, following the Apple Human Interface Guidelines, and erring on the side of simplicity to allow for an easy build and inevitable iteration. Each element was designed to be functionally independent, to allow each to adapt (or be removed) with as little impact on other functionality as possible, as the application matured in its early phases.