EV charging service app: from booking an install to paying for a session

A mobile service system for EV owners: book an installation by city district and follow it through to "installed", report a fault with photos and have the result filed automatically, charge through pick, queue, session, invoice and WeChat Pay, and read the numbers at charger, month and order level. Five entry points cover private cars, ride-hailing, logistics fleets and special-purpose vehicles.

Industry
EV charging services · charger operation and after-sales
System type
Driver-side mobile app (iOS / Android) + operations back office + device and payment interfaces
Key technology
Phone-number sign-in · booking state machine · fault tickets with photo upload · charging sessions · queue and wait estimates · time-of-use tariffs · WeChat Pay · billing and reconciliation
Jiding's role
Requirement shaping, interaction and visual design, app and back-office development, device and payment integration, testing and launch, maintenance
5 tabsEntry points: Home, Stats, Charge, Inbox, Account — install, repair, charge, bill, ask
4 statesBooking states a driver can follow: under review, connected, installed, closed
6 typesNotification types: announcements, repairs, bookings, feedback, charge alerts, payments
4 typesVehicle scenarios: private, ride-hailing, logistics fleet, special-purpose

The Whole Picture

Five things a driver cares about, five tabs on the phone

Book an install, report a fault, start a charge, read the bill, reach a human — that is the whole of it. The interface is not sliced along the operator's org chart; it is sliced along those five actions. Home carries the shortcuts and the live session, Stats carries the money, Charge carries the controls, Inbox carries the notices, Account carries the paperwork. Device management, dispatch and reconciliation stay in the back office and take no tab.

Architecture: five tabs for five actions, never more than one level deep Home Book installation Report a fault Live session News & guides Manuals one landing page, one login Stats Switch charger Monthly bills Session list Time-of-use split Orders overview → detail → order Charge Pick · see the queue Start / end Cancel a queue Invoice: kWh / min / cost WeChat Pay the only live-state screen Inbox Announcements Repair updates Booking notices Charge alerts Payments & feedback each points back to a record Account Devices Vehicles Orders Bookings Repairs · feedback Five tabs stay fixed, and no screen sits more than one level below them — a driver is either installing or charging, never browsing a menu tree.
Architecture: five tabs for five actions — install, repair, charge, bill, ask

Why the live session sits on Home

Drivers open the app at three moments: charging now, just finished, about to charge. The session sits directly under the four shortcuts, so kWh, cost and time left are visible without tapping through. Booking and repairs are low-frequency and only need a shortcut; charging is the high-frequency action and needs the real estate.

Why Account is nothing but records

No settings maze — just four kinds of records a driver may need to pull up: orders, bookings, repairs, vehicles. Every interaction leaves a document behind, so the question "where did my booking get to" is answered by the app rather than a support call.

Installation Booking

Booking: one form, four states, from request to power-on

Installing a charger is not an order that completes itself: it needs a district, a site survey, wiring and a network connection. The booking therefore has to be a trackable ticket, not a message that vanishes on submit.

1

Pick the device

Charger type by vehicle and power sets the frame for everything after.

2

Address & time

Province, city, street address and a preferred slot; the district decides who comes.

3

Contact

Name, phone and a verification code, so the crew can confirm before leaving.

4

Review

Capacity, parking bay and property rules get checked; the state reads "under review".

5

Install & connect

Wiring, mounting, network; the state moves to "connected" then "installed".

6

Close & keep

The booking keeps the crew's name and number, so a later repair has a contact.

App home: vehicle hero image, four shortcuts for booking, manuals, fault report and platform guide, plus announcements, live session and news
Home booking comes first of four shortcuts
Booking form with province and city, street address, device type, installation time, contact name, phone, verification code and a submit button
Booking form seven fields, one pass
StateWhat the driver seesWhat the back office does
Under reviewRequest received, waiting for confirmationChecks the address and capacity, assigns a district
ConnectedThe charger is on the platformBrings the device online and binds its number
InstalledDone, ready to chargeRecords the crew and the completion time
ClosedFiled, retrievable from bookingsSettles the ticket into the after-sales file

Splitting the address into "province and city" plus "street" is not cosmetic: the district decides dispatch, the street decides how much cable the crew loads. Merge them into one field and someone has to read addresses by hand to guess a district — which breaks the moment volume arrives.

Fault Report

Fault reports: three lines and a photo, and the ticket becomes a record

Eight faults in ten can be diagnosed by looking: a scorched connector, a frayed cable, an error code on the screen. So the photo sits beside the text as a first-class field, not buried in an attachment picker.

Repair loop: one report, three steps, result filed against the device ① Submit device · fault type · notes photo of the site ② Dispatch by district and fault type driver gets a notice too ③ On site reads the charger's history loads the right parts ④ Close & file result + photo + time lands in the repair record next report on this charger starts from what was replaced last time The archive is keyed to the device, not the ticket — the history of one charger reads as a timeline, and a repeat offender shows up immediately.
Repair loop: submit → dispatch → attend → file, with the photo running through all four
Fault report form: device, fault type, problem description, photo upload and a submit button
Fault form four fields and submit
Repair record list: cards in reverse chronological order with description, site photos and a date
Repair record photos and dates, newest first

Why the photo cannot be optional

"It won't charge" could be a corroded connector, an offline charger or a vehicle-side refusal. One photo of the connector and the screen tells the dispatcher whether to send a part or a tester. One visit versus two is a doubled cost.

Why drivers see the repair record

Plenty of systems file the ticket where only staff can see it, leaving the driver in the dark after submitting. Opening the record is both an answer and evidence: when, what was replaced, who came. Fewer arguments, fewer calls.

Charging Session

Charging: two escape hatches between picking a pile and paying

Two moments cause trouble: the queue stops being worth it, and the driver has to leave mid-session. The state machine makes both explicit — a queue can be cancelled, a session can end at any time, and settlement follows the kWh actually delivered.

Charging state machine: five states, two dashed escape hatches Idle · pick 01 / 02 / 03 piles load & queue shown Queued est. 25 min can cancel Charging kWh · cost accrue end anytime To pay invoice ready time · kWh · cost Done order into bills reconcile monthly free your turn end session WeChat Pay queue not worth it? cancel and pick another A session does not wait for the driver to press "I'm done": the charger stopping, the plug being pulled, or the target kWh being reached all move it to settlement — the button only makes it happen sooner.
Charging state machine: queue cancellable, session endable, settlement by delivered kWh
Charging screen for picking a pile: 01 / 02 / 03 tabs, device model, remaining capacity, queue size and a start button
Pick a pile queue size and state on one screen
Charging screen in queue state: waiting, estimated 25 minutes, with a cancel option
Queued wait estimate plus a way out
Charging screen mid-session: kWh and duration updating live, with an end-session button
Charging kWh and minutes tick along

Why show "estimated 25 minutes"

The hard part of a queue is not the wait, it is not knowing how long the wait is. A rough estimate from the vehicles ahead — their power draw and remaining charge — is enough for a driver to decide whether to stay or move on. Without it, people stand at the charger refreshing a screen.

Why the invoice lists start and end

Nine disputes in ten are about time. Start, end, kWh, duration and cost sit side by side, so the driver can do the arithmetic: how much, how long, at what rate. Written plainly, it saves the explanation later.

Billing

Billing: overview, detail, order — all three reconcile

The failure mode in charging bills is rarely arithmetic; it is reconciliation — the monthly total not adding up to the line items, or a line item not matching the payment record. So billing drills down three levels, each landing on a document.

LevelWhat it showsQuestion it answers
OverviewSwitch by charger, last month's total spend and session count, daily bars"How much this month, and which days were heavy"
Session detailPer day: kWh, session count, cost; tap a day for device number, duration, kWh"Which session was this charge for"
Tariff splitBand, rate, session count and amount, peak versus off-peak"Why was this one more expensive"
OrderOrder number, created at, paid at, payment method"Was it paid, when, and how"
Stats screen: charger tabs, last month's total of 29345.37 yuan, daily bar chart and a session list
Overview per charger, monthly total and daily bars
Session detail: device number, duration, kWh, tariff breakdown by time band, and order information
Session detail tariff bands, order at the bottom

Time-of-use tariffs are what make a bill add up: the same charger costs different rates by day and night, so the bill must split by band. Otherwise the total matches, the rate does not, and the driver still argues. Band, rate, count and amount sit in four adjacent columns so the arithmetic can be checked.

Notifications

Notifications: six event types, each with a way back

The usual failure is "I was told, but I cannot find it". Notices are grouped by event type, each carrying a time, a summary and a route back to the document — an announcement opens the article, a repair opens the ticket, a payment opens the order.

Announcements

Outages, tariff changes, campaigns. Opening one gives the full text, laid out by heading.

Repair updates

Accepted, dispatched, completed — one notice each, so nobody refreshes the record list for status.

Booking notices

Review result, changed visit time, completion — all attached to the same booking.

Charge alerts

Session started, finished, aborted; a nudge to move the car once the target is reached.

Payments

Invoice generated and payment succeeded, each keyed to an order number.

Feedback

When someone replies to a suggestion, the driver hears about it — closing the loop instead of a void.

Inbox: announcements, repair updates, booking notices, feedback, charge alerts and payment messages, each with a timestamp
Inbox six event types in one timeline
Announcement detail page with title, publish time and body text
Announcement title, time and full body

Vehicle & Records

Vehicles and records: one vehicle, one file — swap the car, keep the history

A household may run two cars; a fleet may run twenty. Vehicles are multiple profiles under one account, and orders, bookings and repairs hang off the account — changing cars adds a record, it does not erase the bills.

Vehicle list: Tesla Model 3, BYD Han EV and NIO ES8 cards with plates and owners, plus an add-vehicle button
Vehicles one card per car, side by side
Add-vehicle form: brand, plate, model, owner, phone, verification code, registration document and vehicle photo upload
Add a vehicle documents and photos together
Booking records with four state filters and cards showing the installer's name and phone number
Bookings four filters, installer contactable
Feedback screen with a multi-line text field and a submit button
Feedback a paragraph and a button

Why upload the registration document

Charger power and connector type track the vehicle closely, and brand, model and plate are what let the back office judge whether a pile fits. The document and photo are the check, and later the evidence of whether a fault is vehicle-side.

Why records belong to the account

If orders hung off the vehicle, changing cars would wipe the history — disastrous for ride-hailing and fleet users. The account is the key, the vehicle is an attribute: sell, add or swap a car and the bills and repairs remain, so reconciliation does not restart.

Screen Gallery

Screen gallery: from sign-in to feedback, screen by screen

Delivery-build screens below, de-identified, with demo vehicles and details. One visual system runs end to end: green as the primary colour, card-based blocks, five fixed tabs, a red dot on messages — a driver is never lost, on any screen.

Account screen: avatar and phone number, device and vehicle entries, then orders, bookings, repairs, feedback, support line and sign out
Account four record types and a support line
Home live-session block showing kWh and cost for the current charge
Home · live session the current charge, pinned
Manual article page with installation steps and a reading progress bar
Manual illustrated steps while installing
Platform guide article: a long-form EV charging safety guide
Platform guide long-form safety content
Home screen with shortcuts, announcement, live session and news sections
Home shortcuts, notice, session, news
News list with thumbnails and dates
News thumbnails, titles and dates
Order list: device model, duration, kWh, cost, order number and a pay button
Orders unpaid ones carry a pay button
Payment sheet after a session: start and end time, kWh, duration, cost and a pay button
Payment the sheet appears at session end

Eight screens here; queue, mid-session and tariff detail appear earlier in the page.

Scenarios

Four kinds of vehicles, four different habits

The same system feels different to a private owner and a fleet. The difference is not features but frequency, timing and sensitivity to the bill — which is why billing is built more finely than the charging screen itself.

Private cars: overnight, low effort

Once or twice a week, mostly at night. They care when the install happens and what the month cost; queues are irrelevant. Bookings, monthly bills and charge alerts do the work; the charging screen is rarely opened.

Ride-hailing: daytime, high turnover

Two sessions a day, and time is income. Queue size and wait estimate are the core information, and cancelling or switching piles decides whether the shift pays. Alerts have to arrive at "your turn", not later.

Logistics fleets: many vehicles, reconciliation

A dozen cars under one account, split by vehicle and month at close. Multi-vehicle profiles plus monthly bills and order detail keep finance out of spreadsheets.

Special-purpose vehicles: site power, response time

Chargers on construction sites, harsh conditions, frequent faults. Photo reports, a repair archive and a crew phone number decide whether downtime is half a day or an hour.

Deliverables & FAQ

What was delivered, and four common questions

Deliverables

  • Driver app: Home, Stats, Charge, Inbox, Account — iOS and Android
  • Booking: seven-field form, four-state tracking, installer hand-back, filtered records
  • Fault reports: device, type, notes and photos; repair record with images
  • Charging: pile selection, queue and estimate, cancellation, start and end, invoice
  • Payments and billing: WeChat Pay, order number and paid-at, monthly bills, tariff split
  • Records: multiple vehicles, documents and photos, orders, bookings, repairs
  • Notifications: six event types, announcement pages, feedback replies
  • Back office and interfaces: devices and chargers, dispatch, reconciliation, device and payment integration

How it was run

One interaction designer, two mobile developers, two back-end developers, one tester and a project manager. Design started with state machines — four booking states, five charging states, three order states — because screens drawn before states are the ones that get redrawn.

Visually the app is deliberately "de-back-officed": no spreadsheet grids, no stacked filters, information carried in cards, one question answered per screen. That is the real difference between a driver app and an operations console — the console offers everything, the app offers what to do next.

As agreed, no client name, pricing or hours appear here; screens are delivery builds with demo data.

How does this relate to the charger vendor's own platform?

The vendor platform runs the hardware: online state, power, fault codes, remote start and stop. This system runs the driver: booking, repairs, sessions, billing and payment. The two meet over a device interface — state is read from the vendor platform or the device protocol, and sessions are opened here and written back. If the vendor already exposes an API, this system is the driver-side layer; if not, a device-access service sits in between and translates each brand's protocol into one data shape.

How is WeChat Pay integrated, and what is required?

A merchant account, API key and certificates, integrated either directly or through a service provider. The flow is: invoice generated, payment invoked, asynchronous callback confirmed, order marked paid, bill written. The critical part is idempotent callbacks — retries deliver the same notification more than once, and double-booking is the most common production incident. Refunds follow the same rule: return to the original channel and record a separate transaction.

Why review a booking instead of dispatching on submit?

Installing a charger is not a courier drop. Capacity, parking bay, permission to chase walls and distance to the meter all need a human judgement, and dispatching without it sends a crew on a wasted trip. The review settles whether and how, so the visit succeeds first time. Making the review visible also tells the driver where it is stuck, rather than leaving them to assume the request was lost.

With only a few chargers, is an app worth it?

At small scale the priority is "it works", not "it has everything". A mini program fits better: no download, scan and use, easy to share, cheaper to build and maintain than two native apps. Move to an app when there are fleet customers, a need for multi-vehicle files and monthly reconciliation, or an existing system to integrate with. The module order here follows that logic — charging and payment first, records and billing next, notifications and operations last.

MORE CASES

More Related Cases

EV charging service app
EC AppSmart charging pile

EV charging service app

A mobile service system for EV owners: book an installation by city district and follow it through t...

View Details →
Pool-cleaning robot companion software system
EC AppIntelligent robot, intelligent cleaning

Pool-cleaning robot companion software system

Companion software for a pool-cleaning robot: a PC back office plus Android / iOS apps; devices come...

View Details →
Curated mall app for a health-retail brand
EC AppE-commerce platform, distribution platform

Curated mall app for a health-retail brand

A shopping app for a health-retail brand: self-operated quality assurance, curated and daily-plus zo...

View Details →

View All Cases →

Planning a similar production line or enterprise system?

Start with our pricing logic, then let's talk requirements — cost structure, technology comparison and acceptance criteria, all laid out in the open.