UX/Product Design

UX Research

EV charging app: Ivygo

EV charging app: Ivygo

Designing a seamless end-to-end experience for hosts and guests across Ivygo’s community EV charging app.

20 min read

Project: 9 weeks, Internship: ongoing

work

about

blog

contact

genevieve hall.

Overview

Overview

Ivygo is an Australian startup building a peer-to-peer network for electric vehicle charging. I first worked on the project through a 9-week UX challenge with Harness Projects, focused on improving the host booking approval and payout experience.


Following the final presentation, Ivygo’s CEO invited me to continue as a UX Design Intern, where I’ve been refining the guest booking and check-in/check-out flows, collaborating with the development team, and preparing my designs for launch.

Role

UX Researcher & Designer

(Harness Projects -> Internship)

Tools

Deliverables

Competitor analysis, journey mapping, persona, wireframes, high-fidelity prototypes

Problems & opportunities

Problems & opportunities

Opportunities

Host-side (Harness Projects)


Hosts struggled to approve bookings, view guest details, and manage payouts due to a shared interface and lack of real-time updates.



Guest-side (Internship)


Guests faced limited feedback during booking and unclear check-in, check-out, and session progress, reducing clarity and trust.

Problems

Host-side (Harness Projects)


I designed a host dashboard with a host–guest toggle, booking details, and live session updates, plus simplified payouts and an earnings dashboard for transparency.



Guest-side (Internship)


I improved booking feedback, clarified check-in/out, added live session tracking, and unified visuals for a cohesive, trustworthy experience.

Host-side (Harness Projects)


I designed a host dashboard with a host–guest toggle, booking details, and live session updates, plus simplified payouts and an earnings dashboard for transparency.



Guest-side (Internship)


I improved booking feedback, clarified check-in/out, added live session tracking, and unified visuals for a cohesive, trustworthy experience.

Jump to Solutions

Research & discovery

Research & discovery

Stakeholder insights

Business goals


  • Build a fair, community-powered EV network

  • Encourage host to guest crossover

  • Scale with a simple intuitive product



Key challenges


  • Hosts unclear where to accept bookings

  • Dual-role users confused by mixed terminology

  • Limited trust/safety signals

“We want to make EV charging accessible, affordable, and financially rewarding for all”

Competitor analysis

Feature

ChargeFox

PlugShare

Joosup

Airbnb

Uber

Camplify

Trust & Safety Signals

Real-Time Oversight

Booking Confidence

Booking Management

Dedicated Host Dashboard

To understand how other platforms support peer-to-peer services, I analysed competitors with similar features and flows to identify UX patterns relevant to Ivygo’s host experience. With no direct competitors in Australia, I focused on indirect and analogous platforms to gather insights from comparable models.

User interview insights

Trust Signals are Essential

Trust Signals are Essential

100%

Wanted a rating & review system

"I’d want a rating or photo — something to show they’re not dodgy."

I interviewed five users — current or potential Ivygo hosts and guests — to explore their expectations, concerns, and what would make them feel confident and motivated to use the app.

Passive Hosting is the Goal

Passive Hosting is the Goal

60%

Wanted a passive experience

"If it just ran in the background, I’d actually use it."

Clear Role Separation

Clear Role Separation

80%

Wanted clear host navigation

"I don’t know where to go to approve a booking, it just feels like a charger search tool."

Real-Time Session Visibility

Real-Time Session Visibility

60%

Wanted session oversight

"I’d want to know when they arrive and that it’s working — otherwise I’m just guessing."

Flexible Payout Options

Flexible Payout Options

40%

Wanted an in-app credit option

"I’d rather earn credit first than give my bank details upfront."

Host persona

Jordan Miles

Jordan Miles

An eco-conscious, tech-savvy EV owner who works remotely and sees hosting as a hands-off way to earn passive income.

Journey map

To better understand the host experience, I mapped out their journey from sign-up to payout. This helped identify where frustrations occur and where design could better support their needs.

Low-fidelity prototypes

Low-fidelity prototypes

Sketches

After identifying key pain points, I began sketching ideas to improve the host journey — from managing bookings to completing sessions — exploring layouts and content priorities.

Host dashboard concepts

Host dashboard concepts

These screens aim to give Hosts a clearer view of their bookings, availability, and recent session activity — all from a streamlined dashboard.

Booking request & approval

Booking request & approval

I explored how a Host might receive a booking request and what confirmation would look like once the booking is approved, ensuring key actions are intuitive.

Declined requests & session in progress

Declined requests & session in progress

These screens focus on keeping Hosts informed with real-time feedback — whether a booking is declined or a session is underway.

Session complete & payment confirmation

Session complete & payment confirmation

Finally, I sketched how the session wrap-up would look, including confirmation of payment to give Hosts closure and transparency.

Peer feedback suggested separating the session summary and review, which led to an updated wireframe (below) with a clearer, more focused flow.

Wireframes

At this stage, I created clickable low-fidelity prototypes (referred to as wireframes throughout this case study) to simulate key workflows and validate my hypotheses.

User testing

User testing

Before refining the visuals, I conducted usability testing on the low-fidelity prototype to uncover pain points, confusion, and opportunities to improve the flow. Each insight directly informed updates that I implemented in the final prototype.

Issues & solutions

High-fidelity prototype & solutions

High-fidelity prototype & solutions

After usability testing, I refined the interface into a high-fidelity prototype focused on simplicity, control, and clarity for Hosts. The following screens highlight key interactions and design decisions.

Dedicated host dashboard

The Solutions


  • A toggle to switch between Host and Guest views, giving users clarity and separating the two workflows.

  • A clean dashboard with Host-relevant features: a scrollable calendar to view bookings by day, clearly labelled booking statuses, and an earnings summary for quick financial oversight.

Rationale


Hosts don’t need a map view like Guests do, they care more about upcoming sessions, earnings, and availability.

After

Before

1

2

3

4

5

6

7

8

Booking request clarity

The Solutions


  • Booking requests show on launch to avoid missed actions

  • Pending approvals are highlighted and in notifications

  • Scrollable cards reveal overlapping bookings

  • Car details help identify guests quickly

  • Ratings and verification build trust

Rationale


These updates streamline the booking flow by improving visibility, reducing uncertainty, and supporting Host confidence.

After

Before

1

2

3

4

5

6

7

8

Booking decline user flow

The Solutions


  • A structured decline flow where Hosts select a reason and can include an optional message.

Rationale


This approach keeps interactions polite and transparent, helping Hosts feel more comfortable and Guests stay informed — reducing friction and potential misunderstandings.

After

Before

1

2

3

4

5

6

7

8

Booking approval user flow

The Solutions


  • Replaced the checklist with a simple information section and added an auto-filled message that Hosts can edit before sending.

Rationale


This keeps Hosts informed and reassured without extra steps, while saving time and maintaining flexibility in communication.

After

Before

1

2

3

4

5

6

7

8

Session in progress oversight

The Solutions


  • Designed a live session card showing check-in time, duration, estimated usage, and finish time, along with options to message the guest or report issues.

  • Easily accessible from the dashboard.

Rationale


This gives Hosts real-time clarity and support options, reducing uncertainty and improving confidence during active sessions.

After

Before

1

2

3

4

5

6

7

8

Session complete summary

The Solutions


  • Created a summary screen with session details, usage, and total earnings.

Rationale


This gives Hosts peace of mind and a clear end point for each session.

After

Before

1

2

3

4

5

6

7

8

Guest review & auto-approval

The Solutions


  • Added a star rating flow and written review option to help Hosts share feedback and support future trust-building.

  • Introduced an auto-approve toggle so Hosts can automate bookings for trusted guests.

Rationale


These features improve transparency, reduce repetitive tasks, and give Hosts more control over how they manage repeat bookings.

After

Before

1

2

3

4

5

6

7

8

Payout preferences & earnings dashboard

The Solutions


  • Added the ability for Hosts to choose between bank transfers or Ivygo credit for receiving payments.

  • Designed an earnings summary dashboard with views for weekly, monthly, and all-time totals.

Rationale


This gives Hosts flexibility in how they manage income and a clear understanding of their financial performance.

After

Before

1

2

3

4

5

6

7

8

Implementation

While implementation wasn’t a core focus of this project, I mapped each feature based on assumed value vs. development effort to support prioritisation. These are high-level assessments, as I didn’t have access to exact dev cost estimates.

Feature prioritisation

Feature prioritisation

Feature prioritisation

  1. Review & rating system

  • Essential for trust; medium–high effort.

  • Essential for trust; medium–high effort.

  • Essential for trust; medium–high effort.

  1. Host-guest differentiation

  • Improves clarity; higher effort due to dual UI.

  • Improves clarity; higher effort due to dual UI.

  • Improves clarity; higher effort due to dual UI.

  1. Notification badge

  • High value, likely low effort — improves visibility.

  • High value, likely low effort — improves visibility.

  • High value, likely low effort — improves visibility.

  1. Payments dashboard

  • Strong value; may require moderate–high effort.

  • Strong value; may require moderate–high effort.

  • Strong value; may require moderate–high effort.

  1. Session summary screen

  • Low–moderate effort if based on existing data.

  • Low–moderate effort if based on existing data.

  • Low–moderate effort if based on existing data.

  1. Session progress screen

  • Valuable but usage estimates may raise effort.

  • Valuable but usage estimates may raise effort.

  • Valuable but usage estimates may raise effort.

  1. Auto-approve functionality

  • Low-effort, optional feature for convenience.

  • Low-effort, optional feature for convenience.

  • Low-effort, optional feature for convenience.

Future recommendations

Future recommendations

Future recommendations

  • Time-blocked visuals for overlapping bookings (like Google Calendar or Teams)

  • Gamified progress bar for Host milestones and earnings

  • Option to download earnings summaries as PDFs

  • In-app messaging for direct communication and increased confidence

  1. Ivygo credit system

  • Low user interest; high effort — lower priority.

  • Low user interest; high effort — lower priority.

  • Low user interest; high effort — lower priority.

Key takeaways

This project gave me the opportunity to…

This project gave me the opportunity to…

This project gave me the opportunity to…

  • Design for both user needs and business goals in a dual-role app environment

  • Balance feature scope with technical feasibility

  • Apply feedback from usability testing to improve clarity and reduce friction

  • Strengthen my ability to prioritise and justify design decisions

Some key challenges I faced were…

Some key challenges I faced were…

Some key challenges I faced were…

  • Designing for two user types in one app: balancing the needs of Hosts and Guests without overwhelming the interface required careful workflow separation and prioritisation.

  • Working without technical constraints: without direct access to developers, I had to make educated assumptions around implementation effort and feasibility.

  • Avoiding friction in the Host flow: small UX details like how and when Hosts approve bookings made a big difference — it took iteration and testing to get the right balance of clarity and simplicity.

If I had more time, I would have loved to…

If I had more time, I would have loved to…

If I had more time, I would have loved to…

  • Conduct another round of testing on the high-fidelity prototype

  • Collaborate with a developer to better understand technical constraints

  • Further explore gamification and messaging features

Dedicated host dashboard

The Solutions


  • A toggle to switch between Host and Guest views, giving users clarity and separating the two workflows.

  • A clean dashboard with Host-relevant features: a scrollable calendar to view bookings by day, clearly labelled booking statuses, and an earnings summary for quick financial oversight.

Rationale


Hosts don’t need a map view like Guests do, they care more about upcoming sessions, earnings, and availability.

After

Before

1

2

3

4

5

6

7

8

Dedicated host dashboard

The Solutions


  • A toggle to switch between Host and Guest views, giving users clarity and separating the two workflows.

  • A clean dashboard with Host-relevant features: a scrollable calendar to view bookings by day, clearly labelled booking statuses, and an earnings summary for quick financial oversight.

Rationale


Hosts don’t need a map view like Guests do, they care more about upcoming sessions, earnings, and availability.

After

Before

1

2

3

4

5

6

7

8

Booking request clarity

The Solutions


  • Booking requests show on launch to avoid missed actions

  • Pending approvals are highlighted and in notifications

  • Scrollable cards reveal overlapping bookings

  • Car details help identify guests quickly

  • Ratings and verification build trust

Rationale


These updates streamline the booking flow by improving visibility, reducing uncertainty, and supporting Host confidence.

After

Before

1

2

3

4

5

6

7

8

Booking request clarity

The Solutions


  • Booking requests show on launch to avoid missed actions

  • Pending approvals are highlighted and in notifications

  • Scrollable cards reveal overlapping bookings

  • Car details help identify guests quickly

  • Ratings and verification build trust

Rationale


These updates streamline the booking flow by improving visibility, reducing uncertainty, and supporting Host confidence.

After

Before

1

2

3

4

5

6

7

8

Booking decline user flow

The Solutions


  • A structured decline flow where Hosts select a reason and can include an optional message.

Rationale


This approach keeps interactions polite and transparent, helping Hosts feel more comfortable and Guests stay informed — reducing friction and potential misunderstandings.

After

Before

1

2

3

4

5

6

7

8

Booking decline user flow

The Solutions


  • A structured decline flow where Hosts select a reason and can include an optional message.

Rationale


This approach keeps interactions polite and transparent, helping Hosts feel more comfortable and Guests stay informed — reducing friction and potential misunderstandings.

After

Before

1

2

3

4

5

6

7

8

Booking approval user flow

The Solutions


  • Replaced the checklist with a simple information section and added an auto-filled message that Hosts can edit before sending.

Rationale


This keeps Hosts informed and reassured without extra steps, while saving time and maintaining flexibility in communication.

After

Before

1

2

3

4

5

6

7

8

Booking approval user flow

The Solutions


  • Replaced the checklist with a simple information section and added an auto-filled message that Hosts can edit before sending.

Rationale


This keeps Hosts informed and reassured without extra steps, while saving time and maintaining flexibility in communication.

After

Before

1

2

3

4

5

6

7

8

Session in progress oversight

The Solutions


  • Designed a live session card showing check-in time, duration, estimated usage, and finish time, along with options to message the guest or report issues.

  • Easily accessible from the dashboard.

Rationale


This gives Hosts real-time clarity and support options, reducing uncertainty and improving confidence during active sessions.

After

Before

1

2

3

4

5

6

7

8

Session in progress oversight

The Solutions


  • Designed a live session card showing check-in time, duration, estimated usage, and finish time, along with options to message the guest or report issues.

  • Easily accessible from the dashboard.

Rationale


This gives Hosts real-time clarity and support options, reducing uncertainty and improving confidence during active sessions.

After

Before

1

2

3

4

5

6

7

8

Session complete summary

The Solutions


  • Created a summary screen with session details, usage, and total earnings.

Rationale


This gives Hosts peace of mind and a clear end point for each session.

After

Before

1

2

3

4

5

6

7

8

Session complete summary

The Solutions


  • Created a summary screen with session details, usage, and total earnings.

Rationale


This gives Hosts peace of mind and a clear end point for each session.

After

Before

1

2

3

4

5

6

7

8