Services · Mobile app development · EV charging apps

EV charging apps built for the rules every UK public charge point now follows.

Codeeo provides EV charging app development across the UK for charge point operators, site hosts, fleet owners and energy suppliers. We build driver apps, operator back offices and host portals that talk to your chargers over OCPP, share data with other networks over OCPI, and support the duties set by the Public Charge Point Regulations 2023, from contactless and transparent pricing to reliability reporting and open data.

Our team of 80+ works from Dubai, Riyadh and Karachi and has delivered 200+ projects across the UAE and the US. We work remotely with UK clients, running discovery, design reviews and demos by video call, with written decisions after every session.

Built for
Charge point operators, destination and forecourt hosts, fleet operators and energy retailers running networks across England, Scotland, Wales and Northern Ireland.
Typical timeline
Timing is set after discovery, once we know which chargers, back office systems and roaming partners the first release must connect to, and it is written into the scope.
What you own
Source code, app store accounts, cloud hosting, OCPI credentials and every driver and session record, held in accounts registered to your business.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

Features for a national network

What a UK charging product needs once it runs in more than one region.

A network that started with a few hubs in one county soon has sites on motorway services, retail car parks, hotels and council streets in several nations of the UK. Each site has a different host, tariff, power level and maintenance contractor, yet drivers expect one app that behaves the same everywhere. The regulations add their own layer: rapid sites must hit a reliability target across the network, prices must be shown in pence per kilowatt hour, and live availability data must be published openly. The features below are the ones we see operators needing first when they plan a product for the whole country rather than a single town. We group them so that your first release covers driver trust and legal duties, and later releases add fleet, host and energy features as the network grows.

Explain your project
  • OCPP charger management

    A charge station management layer that speaks OCPP 1.6J and 2.0.1, so hardware from different manufacturers can be started, stopped, reset and updated remotely. Firmware status, connector faults and heartbeat gaps are logged per site, which gives your operations team one view of every charger in the country instead of a separate portal for each hardware brand.

    Mixed hardware estates run from one control panel.

  • OCPI roaming and open data

    OCPI 2.2.1 connections to roaming hubs and partner networks, so your drivers can charge elsewhere and other apps can sell sessions on your sites. The same location and status data feeds a public, machine readable endpoint, which is how the regulations expect availability to be shared without asking anyone to sign up first.

    Roaming partners and map apps see accurate, current status.

  • Pricing in pence per kWh

    A tariff engine that shows the full price per kilowatt hour before a session starts, locks it once charging begins, and supports different rates by site, time of day or membership. Idle fees and overstay rules sit alongside the energy price so the driver sees everything they could be charged before they plug in.

    Drivers see one honest price and it does not move mid-session.

  • Reliability monitoring

    Uptime is calculated per connector and rolled up across your rapid network for each calendar year, with exclusions such as host closures or grid outages recorded with evidence. Alerts go to field contractors when a rapid unit drops, and a monthly view shows whether the network is on course for the 99% target.

    Reliability evidence is ready when the Secretary of State asks.

  • Helpline and fault tooling

    Tools for the staffed 24 hour helpline the regulations require: agents see the caller's charger, session and payment in one screen, can restart a unit remotely and log the outcome. Contact records are kept in the shape needed for the regular reports operators must submit.

    Calls are resolved faster and every contact is on record.

  • Fleet and depot accounts

    Company accounts with multiple drivers, RFID cards, spending rules and monthly invoices, plus depot charging schedules for vans that return at night. Fleet managers download session data by vehicle for mileage claims and benefit in kind records.

    Business drivers charge on account and finance gets clean data.

  • Host site portals

    A portal for supermarkets, hotels, councils and car park owners who host your chargers: session volumes, revenue share statements, opening hours and access rules for their site only. Hosts can mark a car park closed so that time does not count against reliability.

    Hosts self-serve and fewer emails reach your account team.

  • Smart home charging

    App control for home chargers sold in Great Britain, where the Electric Vehicles (Smart Charge Points) Regulations 2021 set default off-peak charging, a randomised delay and security requirements. We build the scheduling, override and tariff screens around those rules and your energy supplier's time of use rates.

    Home chargers meet the smart charging rules from day one.

  • Accessible driver app

    Screens built to WCAG 2.2 AA, with large touch targets, screen reader labels and site details such as bay width, kerb height and cable reach. This supports duties under the Equality Act 2010 and helps drivers who cannot easily reach a tethered connector find a bay that works for them.

    More drivers can use your network without asking for help.

Who this is for

Four kinds of UK charging business we build for.

The country has a mix of large networks, regional operators, hardware makers adding software, and businesses that host charging as a side line. Each starts from a different place. Some already own a back office and need only a better driver app; others are choosing a charge station management system and want an app built around it. The four situations below cover most of the enquiries we receive from operators in Britain and Northern Ireland, with the first priorities for each.

01

A rapid network expanding across several regions

Your hubs sit on trunk roads and retail parks from the South West to Scotland, and the reliability rule now applies to the whole rapid estate. You need an app that drivers trust, a back office that proves uptime per connector, and OCPI roaming so other apps can sell your sessions. We start with monitoring, pricing display and the helpline tools, then extend the driver app with route planning and memberships once the regulatory groundwork is in place.

Reliability evidence and pricing display come first.

02

A charger manufacturer adding its own software

You sell AC and DC hardware and customers keep asking for an app and a portal to run it. We build a white label platform on OCPP that your customers brand as their own, with separate tenants for each operator, firmware management and a public data endpoint each operator can switch on. Your hardware team keeps control of the protocol layer while we handle apps, dashboards and billing.

One codebase, many branded operators.

03

A fleet or leasing business electrifying vans and cars

Your drivers charge at home, at depots and on public networks, and finance needs one record of every kilowatt hour. We build an app that combines home charger control, depot scheduling and roaming access to public sites, with reimbursement for home sessions and reports by vehicle, cost centre and region.

Home, depot and public charging in one ledger.

04

A retailer, hotel group or landlord hosting chargers

Charging brings people to your sites, but you do not want to run a network yourself. We build a branded app or loyalty extension that finds your locations, links charging to rewards or room bookings, and pulls session data from your operator over OCPI. You keep the customer relationship while the operator keeps responsibility for the regulated duties.

Charging tied to your own customer programme.

How a national charging product is planned and released.

  1. 01Regulatory and estate auditWe list every site, power level and hardware model, then map which duties apply to each: contactless for new 8 kW units, reliability for rapid sites, open data and pricing display everywhere.
  2. 02Protocol and partner mappingOCPP versions per charger, OCPI modules per roaming partner, payment provider, energy supplier feeds and accounting systems are written into one integration plan with owners and test environments.
  3. 03Driver and operator designDriver screens for finding, starting, paying and reporting faults, plus operator, host and helpline views, reviewed with your team over video calls until every flow is signed off.
  4. 04Build in short releasesTwo week sprints with a working build at the end of each, tested against real chargers on your bench or a pilot site before anything reaches drivers.
  5. 05Pilot region then national rolloutOne region goes live first so tariffs, fault routing and roaming are proven, then the remaining sites join in batches with monitoring watched closely.
  6. 06Reporting and improvementUptime, helpline and session data feed a dashboard that shows where drivers struggle and which sites need attention, and that guides the next release.

Technology

What we build this with.

We work with React Native or native Swift and Kotlin for driver apps, Node.js or .NET for OCPP and OCPI services, and AWS or Azure hosting in a UK or EU region if you prefer data to stay close. The final stack depends on your hardware, existing systems and in-house team. Telemetry from chargers runs through a message queue so a burst of status changes on a busy bank holiday does not slow the driver app.

01Mobile

  • Swift
  • Kotlin
  • Flutter
  • React Native

02Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

03Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

What UK operators ask before commissioning a charging app.

It depends on how many systems the first release must connect to.

A driver app on top of an existing back office is far quicker than a new platform that manages chargers directly over OCPP and roams over OCPI. The number of hardware models, payment providers and roaming partners drives the timeline more than screen count. We agree the first release during discovery, write the dates into the scope and show a working build every two weeks so you can see progress against that plan.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews