Ebay Motors Product

Client: Ebay Motors
My Role: Product Designer
Lead Designer: Thai Dang
Product Owner: Richard Sipe
Project Manager: Jake Martin
Design Research: Amelia Abreau

Built by enthusiasts, for enthusiasts

eBay Motors was the go to destination for buying and selling a used car 10 years ago. But market dominance fell by the wayside over time, and our teams mission was to bring it back to pole position, with a Native App to lead the refresh effort. It’s been a challenging project due to limited resources and a compressed timeline which requires a highly efficient and agile approach. Our tech team leveraged Flutter to accelerate development efforts – one code base deploys to both Android and iOS platforms, saving a lot of time, churn and rework.

On the design side we transitioned to Figma, which leveraged remote design collaboration in a cloud based environment. With Figma, we can design, prototype, review and iterate upon hundred of layouts. I’m proud to have worked with such a dedicated and passionate group of  folks, to produce the following work.

– System Design –
Building with Components

Designing in Systems

Our team has only two designers, and we’re constantly juggling different features which are in different phases of development. As such, it takes a lot of discipline, organization and leveraging a component based design library to  build out an app which evolves this quickly. We’ve also leveraged some amazing software this past year to build and collaborate as a remote team.

Software Suite: Sketch, Figma, Overflow, Zeroheight, Lookback

– UX Process –
Product Team Workflow

– Interaction Design –
Wireframing Features

Interaction Flows for new features
I helped to concept some of the smaller features on the app, and interaction flows are a key part of that. I’ll update this section, once this feature launches.

Software Suite: Sketch, Figma, Overflow

– Feature Iteration –
Documenting the Details

Outlining all scenarios in JIRA
The ability to clearly document and outline all use cases within a JIRA ticket is one of the key skills a product designer can have. The better you can document the design, the more likely it will be implemented as described. Since our design team was so small, often we had to create our own tickets in Jira. The small thumbnail graphics above,  shows the degree of documentation needed to show return values based on a range of Min and Max yearly inputs specified for a filtered query. There were eight scenarios in total. These graphics were then attached for dev to review in the Jira ticket. At right, the prototype example of the design realized in code by a developer. We work closely with developers to iterate quickly. It’s one of the key benefits of working in a small, centralized team.

Lead UX Designer: Thai Dang
Senior Developer: Tommy Kooi (Prototype, Build)

– Art Direction –
Icon Development

Icons for Category Navigation

Developing an icon set for vehicle categories was initially a daunting task. My strategy was to trace and simplify, rather than drawing an icon set from scratch. I felt that inventory at this price point warranted a premium set of icons. The initial step was to identify and select the most iconic vehicles from each category. For example, a Datsun 280z is a classic Japanese vehicle which no one could debate – it’s that iconic, within classic car history. The last step was to refine these tracings and strip away any non-essential elements so it read well at a tiny size. By this point, an illustration becomes a UI icon.

Role: Illustration, Art Direction
Credit: Thai Dang (Feedback)

– Art Direction –
Onboarding + Spot Illustrations

Introducing Escrow to First Time Users

Explaining Escrow to folks who have never heard of it, is a challenge. Escrow is an abstract concept and we wanted to quickly convince users of the benefits of registering and completing a sale through Escrow. While this illustration process went through many rounds and revisions, I find writing is always a good starting point before getting into visual design work. Writing is fast, efficient, and doesn’t lock you into the first solution. It forces you to explore the concept first. It maps out the ideas and the objectives we need to meet. By outlining my thinking to compare with the product team – a common framework is established beforehand. Plan first, then draw with confidence.

My Role: Illustration, Art Direction

Jake Martin (Copywriting)
Thai Dang (Feedback)

– User Testing & Collecting Insights –
Prototyping and Testing

Build, Test, Iterate
While the team moves at a brisk pace, it’s still crucial to build a feature which resonates with users and addresses their needs. With such a small team on both the design and development side, testing and iteration ensures our time and effort is spent wisely – building a feature that has value to both our users and our business.

Process wise, designs were built out in either Figma or Sketch, tested in Proto or Figma, and testing sessions recorded in Lookback.

Software Tools: Lookback.io, Trello, Figma

Design Research + Interviewer: Amelia Abreau
Observers: Product Team
My Role: Design Concepts, Build and Refine Prototype

Gathering Insights
The team analyzes our findings and compile high level insights in Trello. An impact matrix helps to prioritize new ideas and insights which emerge from these sessions. A low effort / high impact activity, will often be folded into the planning schedule. A side benefit of testing, is great ideas emerge outside of the initial closed loop experiment. As an agile team, we need to be open and responsive to our user’s suggestions.

Research Lead: Amelia Abreau
Support Role: Product Team


This is a unique website which will require a more modern browser to work!

Please upgrade today!