Service · App development

Custom EV charging app development.

A custom charging app for your EV drivers, your fleet or your charging network. From starting and paying for charging sessions to fleet dashboards with cost per session, OCPP and OCPI integrations, and smart charging. For CPOs, EMSPs, fleet owners and property managers who want to go beyond a white-label app.

OCPP 1.6 / 2.0.1OCPI roamingFleet dashboardSmart charging

An EV app is not a standalone app — it is a protocol stack.

The charging market runs on a handful of open standards: OCPP for communication between charger and backend, OCPI for roaming between networks, ISO 15118 for Plug & Charge, and eRoaming hubs such as Hubject and OICP. A good charging app touches all of these layers at once — and still has to be easy to use for a driver who just wants to press a button.

We have been building that layer for years. For fleet owners with dozens of electric vans, for housing associations with a few hundred parking spaces, for CPOs who want to run their own charging network, and for property managers who want to organise charging at office and retail car parks properly. Almost always in combination with fleet management software and a solid IoT backend for charger telemetry.

What we see time and again: a white-label app from a hardware supplier gets you part of the way, but falls short as soon as you connect a second charger type, want your own tariff structure, or need fleet flows specific to your business. Custom software is then not about the technology, but about the combination of flows — your own brand, your own contracts, your own integrations with lease contracts or energy procurement.

The protocols we work with.

OCPP 1.6J and 2.0.1 — the standard between charger and backend. 1.6 runs on most of the Dutch fleet, while 2.0.1 is needed for Plug & Charge and advanced smart charging. We build backends that talk to both versions in parallel and provide a clean upgrade path per charger type.

OCPI 2.2 — the open peer-to-peer standard for roaming between networks, so a charge card from one provider works at a charger owned by another. We implement both the eMSP side (the card provider calling a third-party charger) and the CPO side (the charger owner accepting someone else's card).

ISO 15118 Plug & Charge — the car authorises itself at the charger using certificates, so no card or app is needed any more. Great for UX, but it requires a careful PKI implementation and integration with OEM backends.

Hubject (OICP) and GIREVE — eRoaming hubs for broad coverage without having to sign separate contracts with every network. We implement the Hubject and OICP connection where it makes sense, alongside direct OCPI.

Three types of EV charging apps we build.

Which combination you need depends on your role in the charging chain — driver app, fleet dashboard, CPO backend, or all three at once. In our first conversation we'll advise which layer should take priority.

EV driver · public or private

Customer app for the EV driver

The app your end user uses to find a charger, start a session, pay and receive the invoice in their mailbox. It includes authorisation via charge card, app token or Plug & Charge (ISO 15118), live charger status, and recognition of business versus private charging when the car is a company car.

Find a chargerStart a sessioniDEAL / cardPlug & ChargePush notifications
Fleet · business charging

Fleet dashboard with cost per session

Which car charges where, how many kWh, at what rate, at which charger owner? The dashboard combines OCPI roaming data, home charging sessions and public charging sessions in a single overview. It includes odometer readings, an expense-claim flow for the employee, and export to your accounting system or subscription billing.

Cost per sessionBusiness / private splitRoaming dataFuel card replacementExpense claims
CPO & EMSP · network operation

CPO backend and roaming integration

For those operating their own charging network: charge point monitoring via OCPP, fault management, dynamic tariffs, billing to end users, and integrations with OCPI hubs and Hubject so that charge cards from other providers work too. For EMSPs, we mirror that pattern from the card side. Almost always combined with energy software for purchasing and grid connection management.

OCPP 1.6 / 2.0.1OCPI 2.2HubjectSmart chargingBilling

Audience-specific flows we often build.

A charging app feels different for every audience. We build the flow around real-world practice, not a generic template — below are a few patterns that regularly come up in projects.

Fleet

Business-private split and fuel card replacement

The car belongs to the company, but the employee sometimes also charges at home or privately at weekends. The app recognises where and when charging takes place, splits business from private according to your policy, and delivers a single monthly statement that replaces the fuel card. This includes a gateway integration with the leasing company.

Home charging

Own solar panels and dynamic tariffs

For homes with their own PV installation, we charge only on surplus, or during the low-tariff hours of a dynamic energy contract. The system takes the home's main connection into account so there is no overload when the induction hob is on as well.

Office

Employee versus visitor flow

Employees charge at the employer's expense, while visitors pay for themselves. The app recognises the difference based on a token or QR code, and the facilities team has a dashboard to see which chargers are occupied, manage waiting lists and allocate costs per department.

Audience

Roaming and transparent tariffs

For public chargers, everything revolves around trust: it must be clear up front what a session will cost, regardless of which card or app is used to authorise it. We build in transparent tariff display, including roaming surcharges, in line with AFIR regulations on price communication at public chargers.

What you get at the end of the project.

A working charging app or charging backend, plus everything around it to run it in production and develop it further yourself.

  • Driver app, fleet dashboard and backendA native iOS and Android app for the end user, a web dashboard for fleet or CPO operations, and the OCPP backend that controls the charge points. Staging and production, in your cloud or hosted by us.
  • Working OCPP and OCPI integrationsTested integrations with the hardware manufacturers you use (Alfen, ABB, Wallbox, KEBA, Ennexos, etc.) and with OCPI hubs for roaming to Allego, Fastned, Vattenfall, Eneco and other networks.
  • Payments, billing and invoicingiDEAL, card payments, subscription or post-paid billing, plus automatic invoices to end users or employers. Business and private use can be split for fleet usage.
  • Documentation, runbooks and source codeThe complete codebase, an architecture overview, a runbook for production incidents (a charge point going offline, an OCPI hub being down) and a guide for your own team.
  • Maintenance and further development contract (optional)Monitoring of charge point uptime, session success rate and OCPI integrations, security patches, OCPP version upgrades and new features on a fixed sprint cadence. Fixed monthly price, four response-time levels. We see ongoing development as the norm for a charging platform — the market changes too fast to deliver an app once and walk away.
  • Test lab and hardware validationWe test against real charge points before going live: a test charge point in our lab plus access to the test portals of the major hardware manufacturers and OCPI hubs. That way, edge cases (a session aborted halfway, a charge point going offline, an OCPI CDR arriving late) don't first surface in production.
Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Who we build for.

The EV charging chain has a handful of distinct roles. Our charging app projects usually run for one of these profiles — if you recognise yourself, we'd be glad to talk through what works best in your context.

CPOs

Charge Point Operators

Parties that own and operate charge points — think networks on the scale of Allego, Fastned, Vattenfall, Eneco or Greenchoice. A dedicated driver app plus an operations backend for uptime monitoring, fault management and dynamic tariffs.

EMSPs

E-Mobility Service Providers

Providers of charge cards and charging subscriptions who don't own charge points themselves, but use other parties' networks via OCPI roaming. The app centres on cardholder flows: finding a charge point, authorising with your token, and seeing transparently what the session cost.

Fleet

Fleet owners and lease companies

Top GSC search query for this page: scalable charging infrastructure for fleet management. We build the dashboard where you can see, per vehicle, where it charges, at what rate, and which part is business or private — connected to your fleet management system.

Real estate & home

Housing associations, office and retail parking, installers

For charging environments at residential or work locations: employee versus visitor flows, feeding back energy from your own solar panels, load balancing per building connection, and cost allocation between tenants or employees. Including an installer flow for the first handover.

How a charging app project works.

1

Introduction and scope kick-off

We map out which role you play in the charging chain, which hardware you use, which roaming partners you want to connect with, and who the end users are. From that comes a scope we can plan.

2

Architecture and proof of concept

We get the first OCPP connection working against one charge point type, validate the OCPI connection to a hub, and set up the first driver flow. A working skeleton for your team to try out and give feedback on.

3

Building in sprints

Every two weeks, a working build you can test yourself. First the happy-path flows (starting a session, paying, invoicing), then smart charging and load balancing, then roaming edge cases. The MVP goes live after a number of sprints for your first target group.

4

Rollout, monitoring and further development

Phased rollout: a pilot location first, then scale up. Monitoring of charger uptime, OCPP errors and payment flows. Ongoing development based on what your drivers and operations team encounter in practice.

Frequently asked questions.

What clients usually want to know before we start.

Which OCPP version do you support: 1.6 or 2.0.1?
Both. Most chargers in the Netherlands still run on OCPP 1.6J (JSON over WebSocket), but newer hardware and anything that supports ISO 15118 Plug & Charge requires 2.0.1. We build the backend so that both versions can run in parallel, and we provide an upgrade path if you want to move to 2.0.1. In practice, that means one central OCPP layer with version-specific handlers and clear per-charger logging of which version and which profiles it supports: security, smart charging, local auth list, reservation, and so on.
How do you handle OCPI roaming and Hubject?
We implement OCPI 2.2 for direct peer-to-peer roaming with other networks, and connect to eRoaming hubs such as Hubject (OICP) or GIREVE for broad coverage. For your drivers, that means a single card or app works on chargers from, for example, Allego, Fastned and Vattenfall, depending on whom you have contracts with. We also handle the less enjoyable side: tariff surcharges, CDR reconciliation (Charge Detail Records that don't match), and a disputes flow for when sessions are billed twice or incorrectly.
What is the difference between a public app and a fleet app?
A public driver app is anonymous: anyone can download it, find a charger, start a session and pay, and the focus is on discoverability and transparent pricing. A fleet app is closed and linked to your vehicle fleet: the cars and employees are known, costs go directly to the employer, and the dashboard shows per-session costs across all chargers used, whether public, at home or at the office. We often build both on a shared backend so that data only needs to exist in one place.
Can you implement smart charging and load balancing?
Yes. For a building connection, we distribute available capacity dynamically across active sessions, so you don't exceed your main connection. This avoids the need for an upgrade and saves on the grid operator's peak tariffs. Optionally with dynamic tariffs (charging when electricity is cheap, based on your EPEX or dynamic contract) and, to a limited extent, vehicle-to-grid where the hardware and energy contract support it. For home charging, we link to solar surplus via the inverter API.
What determines the cost of a project like this?
The biggest variables are: how many target groups you serve at once (drivers only, or also fleet, or also CPO), which roaming partners and payment methods you need, how many charger types you integrate, and how deep the integration with your existing systems goes (ERP, lease contract administration, energy contracts, identity). We work with fixed sprint budgets and discuss scope per sprint, so you stay in control and don't run into surprises halfway through.
Do you also build integrations with our existing systems?
That's the case in almost every project. Think of lease company APIs for vehicle and licence plate data, ERP and accounting for invoicing, identity providers for employee SSO, energy contracts for purchase tariffs, and sub-meter data for billing per building or tenant. See also our page on smart API integrations for how we approach this.
How do you handle security and compliance around payments and personal data?
Payment flows run through PSPs that are themselves PCI compliant (Mollie, Stripe or Adyen), so we never touch card data. For personal data, we apply GDPR-compliant data minimisation, with audit logging on sensitive actions and encryption both in transit and at rest. For public charger tariff display we follow the AFIR regulation, and for smart charging we agree PKI standards in line with ISO 15118.

Talk to us about your EV charging app.

A half-hour introductory call, no obligation. Tell us where you sit in the charging chain (CPO, EMSP, fleet or property) and which flow is causing the most friction right now. We'll think along with you and point out where we can add value.

Edit content