A two-sided EV charging marketplace

Redesigning the driver's journey, from sign-up to a charge worth paying for

SplitEV app demo playing inside an iPhone mockup
Timeline
Dec 2024 — Jan 2026
Impact
~60% less onboarding friction
Team
Founder
Product Designer (me)
Fractional UX Manager
UX Researcher
Engineers
Skills
UI DesignPrototypingUser TestingProduct StrategyHandoff

Overview

Introducing SplitEV

SplitEV is a Techstars-backed startup making EV charging accessible by letting hosts generate income from private chargers and letting drivers book safe, reliable, and nearby chargers. I joined as a fractional design partner to redesign the MVP.

SplitEV screens cycling inside an iPhone mockup: my vehicles, driver savings, and plan usage

Problem

Early flows were incomplete, so people dropped off before they found value.

Drivers couldn't reliably book chargers or tell what a subscription was worth, key flows were broken or circular, and onboarding took too long.

“There's a lot of info here so it'll take a while for me to make a decision.”

– Driver, user testing

Design challenge

How might we unify SplitEV into one coherent system that real users can test and engineers can actually build?

Strategy

Test early, fix fast, and rebuild the driver's core loop.

We ran rounds of user testing to uncover friction early, iterate fast, and validate improvements. Over more than a year, through dozens of iterations, we rebuilt how a driver signs up, finds and books a charger, and sees what they're saving.

Decisions

Onboarding

Onboarding was 200% longer than the industry average and was predicted to lead to high drop-off rates.

How should onboarding get people to value sooner?

I designed onboarding around progressive disclosure: ask only for what the next step needs. With a UX manager, we reduced onboarding friction by nearly 60%.

24 → 10
screens
119 → 53
form elements
Driver onboarding journey, current vs. new: the redesign cuts account creation, subscription, and vehicle setup into one shorter flow
Host onboarding journey, current vs. new
Onboarding before and after for drivers and hosts

Progressive disclosure reduced cognitive overload and decreased time on task. Completion rates increased meaningfully, and users consistently reached activation on the first attempt.

Finding and booking a charger

This user flow was incomplete and failed to surface key information needed to select a fitting station. By reducing friction in the Driver flow, we reinforced the high-retention charging loop that drives SplitEV's subscription revenue.

What should a pin tell a driver before they tap it?

I designed available pins to show price, and unavailable pins to switch off and show when they open. The original pins showed distance from user location, so price and availability were invisible until a driver tapped on a charger. A grey pin also clashed with the teal map and read as broken, not closed.

Option A: Distance

Option A: the map with every pin labelled “2 mi” and unavailable chargers as grey pins
Pro: Distance is visible at a glance.
Con: Every pin says the same thing, and grey on teal looks disabled rather than closed.
Final

Option B: Price

Option B: the redesigned map, lime pins with prices and dark unlit pins with opening times
Pro: Drivers can compare price and rule out closed chargers without tapping.
Con: Distance moves to the list below.
Three explorations for an unavailable charger pin on the map: a dark pin with an unlit bolt and opening time, a collapsed dot, and a dashed ghost pin
Exploring the unavailable state: off, collapsed, and ghost

How should the map and the list work together?

I designed a peeking bottom sheet, showing the nearest charger to give drivers a quick choice without leaving the map. Meanwhile, the original was just the map. To see details or compare chargers, a driver had to tap pins one by one.

Option A: map only

Option A: the map with pins and no bottom sheet
Pro: Maximum room for the map.
Con: No way to see or compare details without tapping each pin.
Final

Option B: peeking bottom sheet

Option B: the map with a bottom sheet peeking “12 chargers nearby” and the nearest charger
Pro: The best option is visible without leaving the map, and the list is one gesture away.
Con: The sheet covers the bottom of the map.

What should a driver see after they book?

I designed navigation to show directions first, with the reservation pinned underneath. The original design put the address, parking instructions, and two buttons over the map while the driver was still on the road, covering more than 40% of the screen.

Option A: everything on one sheet

Option A: the original navigation screen, with a tall sheet showing the address, parking instructions, and Call host and View details buttons
Pro: Parking instructions were right there as soon as the driver arrived, and users could easily call or view details without leaving the map.
Con: The sheet hid much of the route, and the driver had two buttons to weigh while driving.
Final

Option B: route first

Option B: the redesigned navigation screen, with the route on the map and a compact sheet showing time, distance, an End button, and the reserved spot
Pro: More of the route stays visible, and ending navigation is one clear action.
Con: Parking instructions aren't on this screen.

Seeing the value

Drivers had no way to understand their charging behavior, plan usage, or savings, so they doubted the value of their subscription.

“I don't know if this is a good deal or not.”

– Driver, user testing

How can a driver tell the subscription is a good deal?

I chose to highlight a key impact metric, then one comparison. The original design was visually cluttered and difficult to scan. For a dashboard, we wanted to show the most important information in a clear and concise way.

Option A: a card for every number

Option A: the original Savings tab, a purple card with $142 saved followed by many stat cards and a cost breakdown
Pro: Every figure was on one tab, down to energy cost and the subscription fee.
Con: Information density was high and it was difficult to scan.
Final

Option B: one comparison

Option B: the redesigned Savings tab, $142 saved with six months of bars, then SplitEV beside public charging and gasoline
Pro: Users can instantly identify whether or not SplitEV is a good deal
Con: Per-kWh and per-mile detail was removed to keep the dashboard clean and focused.

Solution

A driver can find a charger, get there, and know it's worth it.

The redesigned driver journey: the map with a peeking sheet, the station list, navigation to a reserved charger, and the savings dashboard
Map, station list, navigation, and savings

Nearly 60% less onboarding friction

24 screens down to 10, and 119 form elements down to 53

Chargers you can judge from the map

Price and availability sit on the pin, with the nearest charger one glance away

A clear answer on value

One number and one comparison tell drivers if SplitEV is a good deal

Reflection

Prioritize the sprint, not the backlog

Without a product manager to think about long-term vision and scalability, I prioritized tasks for each sprint rather than mindlessly accepting Phase 2+ backlog requests.

Think in systems

I envisioned how retrofitting new features would interact with the current infrastructure and cascade down, in order to save time and development costs. This way, I was able to shape the direction of the MVP so that we would have a successful and sustainable launch.