Service · App development

Custom EV charging app development.

A custom EV charging app for your 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 more than a white-label app.

OCPP 1.6 / 2.0.1OCPI roamingFleet dashboardSmart charging

An EV app is not a standalone app.

The charging-point 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 it also 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 operate their own charging network, and for property managers who want to neatly organise charging at office and retail car parks. Almost always in combination with fleet management software and a robust IoT backend for charger telemetry.

What we keep seeing: a white-label app from a hardware supplier gets you part of the way, but falls short once you connect a second charger type, want your own tariff structure, or need fleet flows specific to your business. Custom development is then not about the technology, but about the combination of flows: your own brand, your own contracts, your own integrations with lease agreements 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 support both versions in parallel and ensure a clean upgrade path per charger type.

OCPI 2.2 is the open peer-to-peer standard for roaming between networks, so a charging card from one provider works on another provider's charge point. We implement both the eMSP side (the card provider calling a foreign charge point) and the CPO side (the charge point owner accepting someone else's card).

ISO 15118 Plug & Charge: the vehicle authorises itself at the charger using certificates, so no card or app is needed. Great for user experience, but it requires careful PKI implementation and integration with OEM back-ends.

Hubject (OICP) and GIREVE: eRoaming hubs that provide wide coverage without you having to sign separate contracts with every network. Where it makes sense, we implement the Hubject and OICP connection 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 back-end, or all three at once. In the first conversation we advise which layer should take priority.

EV driver · public or private

Customer app for the EV driver

The app that lets your end user find a charge point, start a session, pay and receive the invoice in their inbox. Includes authorisation via charging card, app token or Plug & Charge (ISO 15118), live charge point status, and recognition of business versus private charging when the car belongs to the company.

Finding a charge pointStarting a sessioniDEAL / cardPlug & ChargePush notifications
Fleet · business charging

Fleet dashboard with cost per session

Which car charges where, how many kWh, at what tariff, and from which charge point owner? The dashboard combines OCPI roaming data, home charger sessions and public charge point sessions in one overview. Includes mileage reading, 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 back-end 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 each audience. We build the flow around practice rather than a generic template; below are a few patterns that recur across projects.

Fleet

Business-private split and fuel card replacement

The car belongs to the company, but the employee sometimes charges at home or privately at the weekend too. The app recognises where and when charging takes place, separates business from private use according to your policy, and produces one monthly statement that replaces the fuel card. Includes a gateway integration with the leasing company.

Home charging

Own solar panels and dynamic tariffs

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

Office

Employee versus visitor flow

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

Audience

Roaming and transparent tariffs

For public charging, trust is everything: customers need to know upfront what a session will cost, no matter which card or app they authorise with. We build the tariff display transparently, including roaming surcharges, in line with AFIR regulations on price communication at public charge points.

What you receive at the end of the project.

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

  • Driver app + fleet dashboard + backendNative 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, hosted in your cloud or with 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, subscriptions or post-paid billing, plus automatic invoices to end users or employers. Business versus private splitting for fleet use.
  • Documentation, runbooks and source codeThe full codebase, an architecture overview, a runbook for production incidents (a charge point going offline, an OCPI hub being down) and a handbook for your own team.
  • Maintenance and ongoing development contract (optional)Monitoring of charger uptime, session success rate and OCPI integrations, security patches, OCPP version upgrades and new features on a fixed sprint cycle. Fixed monthly price, with four response-time levels. We see ongoing development as the norm for a charging platform: the market changes too quickly for an app to be delivered once and then left alone.
  • Test laboratory and hardware validationWe test against real charge points before going live: a test charger in our lab, plus access to the test portals of the major hardware manufacturers and OCPI hubs. That way edge cases (a session interrupted halfway, a charge point going offline, an OCPI CDR arriving later) don't surface for the first time in production.
Not yet sure about a large project?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.

Explore OneDayBuild →

Who we build for.

The EV charging chain has a handful of distinct roles. Our charging app projects usually serve one of these profiles. If you recognise yourself here, we're happy to talk through what works best in your context.

CPOs

Charge Point Operators

Parties that own and operate charge points, at the scale of networks such as 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 charging cards and charging subscriptions that don't own charge points themselves, but use someone else's network 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 leasing companies

Top Google Search Console query for this page: scalable charging infrastructure for fleet management. We build the dashboard that shows you, per vehicle, where it charges, at which tariff, and what share is business or private, linked to your fleet management system.

Property and home

Housing associations, office and retail car parks, installers

For charging environments at homes or workplaces: employee versus visitor flows, feeding back from your own solar panels, load balancing per building connection, and cost allocation between tenants or employees. Includes an installer flow for the initial handover.

How a charging app project runs.

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 we can define a scope we can plan.

2

Architecture and proof of concept

We get the first OCPP connection working with one charger type, validate the OCPI connection with 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

A working build you can test yourself every two weeks. 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 ongoing development

Phased rollout: a pilot location first, then scaling up. Monitoring of charger uptime, OCPP errors and payment flows. Further development based on what your drivers and operations team run into 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 OCPP 1.6J (JSON over WebSocket), but newer hardware and anything supporting ISO 15118 Plug & Charge requires 2.0.1. We build the backend so 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 logging per charger showing which version and which profiles it supports: security, smart charging, local auth list, reservation, and so on.
How do you work with 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 wide coverage. For your drivers, this means one card or app works at chargers from, for example, Allego, Fastned and Vattenfall, depending on who you have contracts with. We also handle the less glamorous side: tariff mark-ups, CDR reconciliation (Charge Detail Records that don't match), and a disputes flow for when sessions are charged twice or incorrectly.
What is the difference between a public 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 tariffs. A fleet app is private and tied to your vehicle fleet: the vehicles and employees are known, costs go directly to the employer, and the dashboard shows per-session costs across all the chargers used, whether public, at home or at the office. We often build both on a shared backend so that data only needs to live 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 such a project?
The biggest variables are: how many user groups you serve at once (drivers only, or fleet too, or CPO), which roaming partners and payment methods you need, how many charger types you connect, 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 aren't faced with surprises halfway through.
Do you also build integrations with our existing systems?
That is the case on almost every project. Think of leasing company APIs for vehicle and licence plate data, ERP and accounting for invoicing, identity providers for single sign-on for employees, energy contracts for procurement tariffs, and sub-meter data for billing per building or tenant. See also our page on smart API integrations for how we approach that.
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 charge-point tariff display we follow the AFIR regulation, and for smart charging we agree on PKI standards in line with ISO 15118.

Talk to us about your EV charging point app.

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

Edit content