Figma Design File : https://www.figma.com/design/HQiowSEZWtefmjVP5cqZuY/ZENO?node-id=0-1&p=f&t=ZuWU0JArTeGN7yjv-0

How I Turned a Data-Heavy EV App Into a Four-Second Experience.

ℹ️ Confidentiality note. Zeno is a portfolio-safe recreation of a product I designed for a Copenhagen-based EV startup. With the company's permission, I rebuilt it under a new brand. Every decision, constraint, and insight here is real. Only the branding changed.


Project at a Glance

Role Platform Timeline
Sole UX/UI Designer, Freelance iOS Mobile App + Android 2 months to MVP

A4 - 1.png

35+ Screens 5 Core Flows 2 Month MVP 1 Designer 2 months Timeline

What Zeno Does

Electricity prices change every hour. Most EV owners charge at the wrong one.

Zeno's algorithm monitors real-time prices, finds the cheapest window before your departure, and charges your car then. You set two things: when you need to leave, and how full you want the battery. The app handles everything else.

💬 "You set the departure time. You set the target charge. The algorithm finds the cheapest hour and does the rest."


My Role

Sole designer from day one. No existing product, no design system, no prior work to inherit. Only a vision from the CEO and CTO and a blank Figma file.

I was early in my career when this started. What I know now about design systems, component thinking, and stakeholder communication came directly from the pressure of this project. Everything here was built from scratch.


01. The Problem

Dense data. A complex algorithm. An audience that needed simplicity.

Must show Why
Battery % + time remaining + ready-by Core reason users open the app
Target State of Charge The charge ceiling set by the user
Departure time What the algorithm schedules around
Auto Mode, On/Off, Cable Lock The three primary controls
Charger and vehicle selector Context for multi-device users
Connection status Confirms the system is live