Battery UI Design: Inspirations & Resources for Designers A battery indicator is a tiny element carrying high-stakes information. Users need to know how much energy is left, how urgent it is, whether charging is working, and what to do next.

This guide covers smartphones, widgets, wearables, EV charging apps, battery management systems and energy dashboards. A good-looking gauge still fails if it communicates the wrong thing. Below you'll find examples worth studying, the principles behind them, resources for research and production, and a practical workflow.

Key Takeaways

  • Pick a pattern by the decision the user must make, not by visual trend.
  • Pair every indicator with a label, accessible colour and context.
  • Study both consumer and energy-product dashboards.
  • Test normal, critical, disconnected, stale-data, charging and error states before polishing.

What Makes Battery UI Design Useful, Not Just Attractive

Start with the decision the user needs to make

Ask first: what does the user need to know or do next? Someone glancing at a phone wants a rough sense of how long they have. Someone responding to an EV charging fault needs the fault and the fix. Someone watching a stationary battery system needs trends and alerts.

Separate two kinds of information:

  • Immediate action: remaining time, charging status, fault state.
  • Long-term monitoring: battery health and degradation.

The terms matter. IEEE defines state of charge as remaining electrical energy as a percentage of total usable capacity. State of health compares the battery's current condition with its beginning-of-life state, and a 2024 review notes it can be measured through capacity, energy, usable energy or resistance. So a displayed health score should say which measure it uses.

Match the visual encoding to the information

  • Icon: tiny and universal, but low precision.
  • Percentage: exact, but says nothing about urgency.
  • Bar or ring: quick to read, needs space, handles one value well.
  • Time estimate: closest to the user's real question, but only honest when reliable.
  • Trend line: best for health and history, too heavy for a glance.

Oleg Frolov's UX Collective exploration of a battery charge widget (2022) is a useful case study. It proposes time-to-empty beyond a bare percentage and pays attention to clearance, stroke consistency and hierarchy. It is a concept, not a validated product, so treat it as a critique exercise.

Design for context, uncertainty and changing conditions

The same 30% means different things at different consumption rates. Phone APIs reflect this: Android's BatteryManager exposes capacity as a percentage, and its charging-time estimate can return -1 when it can't calculate one. Apple's UIDevice.batteryLevel can also return -1.0 when monitoring is off.

EV range is similarly conditional. A Coventry University study lists driving style, speed, traffic, road profile, temperature and HVAC use as factors. Show estimates as estimates.

Design explicit treatments for:

  • Disconnected devices
  • Cached or delayed readings
  • Uncertain estimates
  • Temperature warnings
  • Interrupted charging

Five battery interface edge cases requiring explicit status treatments

Even a small "Updated 2 hours ago" label prevents a stale number from being trusted.

Battery UI Design Inspirations to Study

Minimal and energy-aware interfaces

Fast Company's 2018 piece on FriendUI showed a mostly black, thin-typography, monochrome smartphone concept built around OLED. The article claims black pixels use less energy but doesn't report a controlled test of FriendUI itself.

Real measurements are more nuanced. Purdue's 2021 tests across six apps and four OLED phones found dark mode saved 3-9% of power at 30-50% brightness and 39-47% at maximum brightness. Those are power-draw results, not a runtime guarantee, and LCD backlights behave differently. Verify any energy claim against your target displays.

OLED dark mode power savings by screen brightness level

Widgets and glanceable battery status

Apple's Batteries widget shows the charge of a connected Apple Watch alongside the iPhone. Key lessons from that pattern:

  • Group related devices together
  • Identify each device clearly
  • Keep labels readable in compact space

Apple's widget guidance also notes the system controls refresh timing, so a widget is glanceable, not a live instrument.

Ordering depends on the likely action:

  • By percentage: good for "what needs charging?"
  • By time remaining: good for planning the day
  • By urgency or user priority: good for critical devices

No universal rule exists. Pick the order that matches what the user does next.

EV, battery management and energy dashboard patterns

Product What it shows
Geotab EV charge monitoring Charge status, SoC, charging power, estimated time to 90%, range with an uncertainty range
Tesla Powerwall app Energy flow among solar, battery, home and grid; reserve level
Enphase app Production, consumption, battery charge and operating profile
Victron smallBMS NG SoC, voltage, current, time remaining, cell limits, alarms

Geotab notes its charge-time estimate assumes current charging power continues. That kind of caveat is worth copying.

The pattern across all of them: immediate status first, actionable alerts second, supporting diagnostics third.

Battery dashboard information hierarchy from status to diagnostics

In our own EV battery work at What if Design, such as the Batteryze health dashboard, a colour-coded state-of-health gauge sits beside a cycle count (140 of 1,200), keeping condition and age distinct.

Battery UI Design Resources for Research and Production

Inspiration galleries and case studies

  • Mobbin's Tesla charge stats flow: real product captures, though third-party screenshots may be copyrighted.
  • Behance's EV Charging mobile app and Dribbble's Tesla Battery Dashboard concept: creator work, with no verified reuse licence.
  • Figma Community's Battery Settings Page and Energy Management System Dashboard: both indicate CC BY 4.0, so check attribution terms.

Use galleries for pattern discovery and critique, not copying. For each reference, note:

  • Product context and user goal
  • Data shown and interaction model
  • Accessibility choices and weaknesses you spot

Platform and technical guidance

  • Apple Human Interface Guidelines: Widgets, Progress Indicators, Dark Mode and Accessibility
  • Material Design 3 progress indicators
  • Android app widgets and dark theme documentation
  • Android BatteryManager and iOS UIDevice battery docs
  • MDN's Battery Status API, labelled "Limited availability", so don't assume cross-browser support
  • Open Charge Alliance's OCPP and ISO 15118-20, which are communication standards rather than UI specs

Check links and API versions before you build, since platform docs change.

Prototyping, accessibility and testing tools

  • Figma variables and modes: test light and dark themes and token reuse.
  • WebAIM and Stark contrast checkers: validate text and graphic contrast.
  • TalkBack and VoiceOver: confirm the status is spoken sensibly.
  • Apple Accessibility Inspector: check hierarchy, order and spoken descriptions.
  • Real devices: test text scaling, touch targets and loading behaviour.

A Practical Workflow for Designing a Battery Interface

Define the product requirements and data model

Start with users, devices, environments and decisions. Then list the data you actually have: SoC, SoH, charging state, time remaining, power, temperature, faults, update frequency and confidence.

Build a state inventory:

  1. Normal use and charging
  2. Fully charged
  3. Low and critical charge
  4. Disconnected, stale or unavailable data
  5. Charging failure
  6. Thermal or safety warning

Six-state battery interface testing inventory from normal use to safety warning

Mark which states demand user action.

Build the information hierarchy and interaction model

Decide what lives in the glanceable summary, detail view, notification or diagnostic screen. Make a number primary when precision matters, a bar or ring when speed matters, and a trend when condition matters.

Define colour, icon, type and motion rules that still work without colour or animation. For multiple devices or packs, sort by urgency and actionability.

Prototype, test and refine

Wireframe hierarchy and state coverage before visual polish. Then check whether users can identify status, judge urgency, recognise uncertainty and find the next action without you explaining.

Test text scaling, touch targets, contrast, screen-reader labels, reduced motion and both themes. For Indian users, also check languages and unit formats.

India's Constitution lists 22 languages in its Eighth Schedule, and an IAMAI/Kantar report found 98% of internet users accessed content in Indic languages in 2024. That figure covers general internet use, not battery apps, but it still supports long-label and multilingual testing.

Battery interface localization testing requirements for Indian users

Climate-tech, EV and battery teams that want a senior partner to connect technical product understanding with UX, brand and business goals can look to What if Design.

Common Battery UI Mistakes and How to Avoid Them

Treating percentage as the complete story

A percentage doesn't tell you runtime, health, charge speed or urgency. Pair it with time remaining, charging state, a trend or a short label when that data is reliable.

Using colour and motion as the only warning language

WCAG 2.2 requires that colour not be the only way to convey state (1.4.1), and meaningful graphics need 3:1 contrast (1.4.11). The US National Eye Institute says colour blindness affects about 1 in 12 men. Practical safeguards:

  • Back red and green with icons and text
  • Avoid flashing more than three times per second
  • Let users disable nonessential motion

Ignoring operational and localisation edge cases

Design for the states that break a clean percentage readout:

  • Offline, delayed telemetry and missing values
  • Charging errors and low-power mode
  • Long labels, 200% text scaling, different units and multiple languages

Test on realistic Indian devices, languages and patchy connectivity.

Frequently Asked Questions

What is battery UI design?

It is the visualisation and interaction design for charge, health, charging, runtime, alerts and related battery data. The term isn't a formal standard.

How should battery level be displayed: percentage, icon, bar or ring?

It depends on space, needed precision, urgency and whether you show one device or many. Icons suit tight spaces, percentages suit precision, and bars or rings suit quick reading.

What is the difference between state of charge and state of health?

State of charge is the energy available now. State of health is long-term condition against a new battery. Give them different labels and visual treatments.

How can dark mode improve battery UI design?

It can improve visual comfort and hierarchy, and may cut power draw on OLED screens. Savings depend on brightness and display type, so don't promise them on LCDs.

What resources can designers use for battery UI inspiration?

Use official platform guidelines, UX case studies, Mobbin, Figma Community files, accessibility tools and real EV or energy products such as Geotab, Powerwall and Enphase.

How do you design a battery dashboard for an EV or energy system?

Lead with live status, then actionable alerts, then charging or energy-flow context. Show uncertainty, safety states, historical trends and clear escalation paths.