Home / Honda × Parkopedia
Case Study — In-Vehicle UX · Proof of Concept

Honda × Parkopedia

POC for reserving and payment for a parking space through CarPlay and Android Auto.

Honda x Parkopedia in-vehicle parking concept
Client
Honda R&D Innovations
Product
In-vehicle parking search and payment
Role
Lead Product Designer
Duration
About 3 months, 2017

Honda R&D Innovations wanted a proof of concept to integrate with Parkopedia to find and pay for parking inside the vehicle.

01

Overview

I led the flow architecture, in-vehicle interface design, and interactive prototype for this proof of concept with Honda R&D Innovations.

The result was a working POC that clarified the full problem and gave the team a concrete path forward, not just the happy path.

Team, tools & scope

  • Team: I was the only TribalScale designer and worked alongside a Honda in-house designer. I also collaborated with TribalScale engineers and consulted Parkopedia's technical team.
  • Tools: I used Sketch for flows and mockups, and InVision for the prototype.
  • Methods: Design audit, driving-state modeling, technical discovery, competitive review, and prototyping.
  • Scope: Build a POC covering three driving states, technical exploration of car payments, and error states for both lanes.
02

Problem

Honda's in-house team had designed the happy path for a car approaching its destination, but it didn't cover the full journey.

It missed steps like getting into the car, sitting in place, and driving to the destination. It didn't include direct user validation, since Honda's team handles that.

Honda was deciding if in-vehicle parking payment was viable, if Parkopedia was the right partner, and if payment inside a moving vehicle was more of a safety issue than a UX issue. I identified pain points based on the driving context instead of confirming them with drivers.

Why it had stalled

  • Only the happy path was designed. The Honda in-house team still needed to consider the entire customer journey to build a functional POC and assess whether the concept could move forward.
  • The in-motion and out-of-car stay haven’t been considered. This is a different problem the existing designs missed.
  • Payment security was unclear across both platforms. The tech was new, and there was no clear documentation on CarPlay or Android Auto payment capabilities.
03

Research

The research focused on technical discovery. I used a design audit, competitive review, review of automotive app design principles, and technical investigation.

The audit compared Honda's work to all driving states. The competitive review showed that most systems and parking apps assume the user is stationary and holding a phone. I also went through the driving-to-parking process myself and documented each step.

I reviewed the prototype with Honda and Parkopedia stakeholders and TribalScale engineers, while the in-house Honda team took over user testing.

Key findings

  • The driving state, not the user type, organizes the problem. The same task becomes three different products depending on whether the driver is moving, approaching, or stopped.
Existing Honda in-vehicle parking flow, audited against the full set of driving states
Fig. 01 The two driving states I added to Honda's original happy path are an in-motion, voice-driven flow and a parked, touch-driven flow.
04

Process

  1. 01

    I reviewed Honda's existing designs and identified what was missing. I divided the experience into three driving states: moving, approaching the parking spot, and stopped. Honda's happy path covered the approaching state, so I designed the other two. While moving, the system uses voice-driven confirmation, and when stopped, it allows touch-driven search and payment.

  2. 02

    I led the payment-security discovery and confirmed that Parkopedia's system needed to handle payment. This set the constraint early, before it could affect the design, and clarified the integration path for the team.

  3. 03

    I built an interactive prototype to show what was possible. TribalScale engineers used it to create a proof of concept for Honda in Android Auto, helping move the concept from design into implementation.

05

Solution

I designed a complete in-vehicle parking concept for three driving states, with payment handled by Parkopedia's system.

While driving, the interface highlights key actions, uses short sentences, and reads instructions aloud. It suggests nearby lots and accepts voice confirmation, without map use or payment entry. When parked, it allows map search, price and ETA comparison, and touch-confirmed payment. The third state, approaching the parking spot, builds on Honda's original happy path. These three states together cover the full journey: driving, choosing where to park, and parking.

I simplified the screen to show only what matters for decisions: price, ETA, and a garage or street toggle. If drivers read more, they might not watch the road. I also designed the error states instead of leaving them for later.

Parked-state interface showing price, ETA, and a garage-or-street toggle
Fig. 02 In-vehicle infotainment mockup: price, ETA to destination, and a garage/street toggle, with reserve and navigate as the two primary actions.
06

Impact and results

TribalScale engineers used my prototype to build a proof of concept for Honda in Android Auto.

I created the in-motion and error-state flows, which were new and essential to the build. After in-house user testing, the POC was handed over to MXNavi, a tech company in China, for further development. Since the 2021 launch, the app has approximately 3 million users.

What came after

  • Parkopedia launched in-vehicle parking payment for Honda in mainland China in October 2021. This happened four years after the proof of concept explored the same idea with MXNavi, showing that the concept moved from exploration to production.
  • Expanding beyond Honda. In March 2026, Parkopedia published a parking data benchmarking report. BYD will start using Parkopedia-powered parking payments in production vehicles from early 2027, beginning in Europe.

What worked

Reviewing Honda's in-house designs and pointing out what was missing shifted the project from execution to problem definition, clarifying the business need. I helped set the scope and work through edge cases and integration scenarios with the product and engineering teams, strengthening the foundation for the build.

What I'd do differently

The POC was tested internally at Honda’s headquarters. I suggested using cameras in the front and back seats to track eye movement and see what users focus on, along with voice narration.

What I learned

Context limits a design more than any brand or platform rule. By designing for the toughest situations, this concept worked well with engineering and strengthened the overall solution.

Strengths

Contextual design under constraint Gap analysis & problem definition Design–engineering collaboration Emerging-platform fluency Prototyping for prioritization Partner ecosystem navigation