Updated October 2026 · Written and maintained by the Progression Agency strategy team
An EV charging app development company designs and builds the software that runs a charging network: the driver app that finds a charger, starts a session and takes payment, the charging station management software that talks to every charger over OCPP, roaming links to other networks and the dashboards operators and site hosts use. Progression builds this software for charge-point operators, charging startups, fleets, utilities, property owners and charger makers. Progression Agency is based in New York City and works with clients across the United States and worldwide.
On this page · 16 sections
- What does an EV charging app development company build?
- EV charging management software: what the back office must do
- OCPP explained: what is OCPP software?
- EV roaming with OCPI: letting drivers charge on other networks
- Payments and authorization: app, RFID, card readers and Plug and Charge
- NEVI-funded stations: the federal rules your charging software must meet
- EV charging API: open data for maps, apps and partners
- Load management, smart charging and fleet depots
- White label EV charging software or a custom build?
- Uptime, monitoring and support after launch
- AI answers: how charging buyers ask assistants for a developer
- How EV charging app development runs, phase by phase
- How much does EV charging app development cost?
- How to choose among EV charging software providers
- Why Progression as your EV charging app development company
- Related software and app development services
The short answerEV charging software has two halves: a driver-facing app and a back office that manages chargers, sessions, prices and payments. We start from your charger models and business model, choose the OCPP version and roaming approach, design payment and authorization paths, and build for the federal uptime, pricing and data rules when sites are publicly funded. You can start on a white label platform and add custom parts, or own the full stack. Each build is quoted after a written scope.
Protocol details are described from the Open Charge Alliance and EVRoaming Foundation pages, and federal requirements from the text of 23 CFR 680, as read in October 2026. This is general information rather than legal advice, and prices come only after a written scope.
What does an EV charging app development company build?
It builds the software layer of a charging business: driver apps, the back office that controls chargers, operator and site-host tools, fleet charging and the links to partner networks. The charger hardware comes from its maker; everything a driver, an operator or a finance team touches is software.
EV charging mobile app for drivers
The ev charging mobile app shows nearby chargers with live status and price, starts and stops a session, handles payment and receipts, and sends a notice when charging is done. EV charging station app development then adds reservations, favorites and charging history once the basics work. Our Android and iOS app development teams build these apps, often from one cross-platform codebase.
Charging station management software behind the app
Charging station management software, often shortened to CSMS, is the back office every charger connects to. It registers chargers, authorizes drivers, records sessions, applies tariffs, pushes firmware and configuration, and raises faults. The app is only a window onto it.
Operator dashboards and site-host portals
Operators need a live map of charger status, fault queues and uptime by port. Site hosts such as property owners and retailers need revenue, energy and usage reports, and sometimes control of their own prices and access hours.
EV charging station development: what we build and what we do not
EV charging station development spans site selection, electrical work, hardware and software. We cover the software: apps, back office, integrations, data and support. Installation and electrical work belong to qualified contractors and the charger maker.
EV charging management software: what the back office must do
EV charging management software must keep every charger reachable, every session billed and every fault visible. The table lists the core functions and who relies on each one.
| Function | What it does | Who relies on it |
|---|---|---|
| Charger onboarding | Registers each charger, its ports and connectors | Operations |
| Authorization | Accepts app users, RFID cards, roaming tokens and card payments | Drivers, partners |
| Session records | Start, stop, energy, power and errors for each session | Finance, support |
| Tariffs | Prices per kWh, time or session, by site and customer type | Pricing, site hosts |
| Remote commands | Start, stop, unlock, reset and change availability | Support desk |
| Firmware and configuration | Schedules updates by model and logs results | Operations |
| Smart charging | Sets power limits per port or site | Site hosts, energy managers |
| Reporting | Uptime, utilization, revenue and program data | Owners, funders, states |
EV charging station management software for public networks
Public networks add roaming, one-off card payments, real-time pricing on maps and, for funded sites, uptime and data reporting. The back office has to treat a driver from a partner network the same way it treats its own customers.
Charge point management system for workplaces and multifamily sites
A charge point management system for private sites focuses on access: which employees or residents may charge, at what price, and how costs are split or billed back. Reports go to facilities and finance rather than to drivers.
OCPP management software across mixed charger fleets
Most networks run chargers from more than one maker, each with its own firmware quirks. OCPP management software has to accept small differences in how each model reports status and errors, and keep a per-model profile so support staff are not guessing.
OCPP explained: what is OCPP software?
OCPP software is any program that speaks the Open Charge Point Protocol, most often the back end that chargers connect to. The Open Charge Alliance describes OCPP as the global open communication protocol between charging stations and charging management systems, intended to make infrastructure interoperable and less dependent on proprietary systems.
| Version | Released | What it adds |
|---|---|---|
| OCPP 1.6 | 2015 | Smart charging for load balancing with charge profiles, local list management, SOAP and JSON versions |
| OCPP 2.0.1 | 2020 | Device management, improved transaction handling, added security, smart charging, ISO 15118 support, display messages |
| OCPP 2.1 | 2025 | ISO 15118-20 bidirectional charging, DER control, ad hoc card and dynamic QR payment, prepaid cards, local cost calculation |
OCPP 1.6J or 2.0.1: which should a new back end support?
Both, in most cases. The alliance notes that OCPP 1.6 remains widely used, that 1.6 and 2.0.1 are not compatible, and that 2.0.1 is on its way to replacing 1.6. A new back end that speaks only one version will either strand older chargers or miss the security and device management of the newer one.
OCPP backend software and the OCPP server
The OCPP backend is a server that holds a live connection to every charger, receives status and meter messages, and sends commands back. OCPP server software has to handle thousands of long-lived connections, reconnect storms after a power cut and chargers that send messages out of order, which is why it is tested against simulated chargers before real ones.
Is OCPP open source?
OCPP is an open protocol, published by the Open Charge Alliance for anyone to implement; the protocol itself is not a piece of software. Open-source back ends exist, and some are good starting points. We assess any open-source component on license, maintenance activity and version support before building on it.
OCPP certification and test laboratories
The alliance runs OCPP certification through independent test laboratories. For OCPP 1.6, the program opened in 2019, with a core profile that is mandatory for both chargers and management systems, smart charging mandatory for management systems, and advanced security optional. As of April 1, 2025, the alliance listed a maximum fee of €6,500 for one management system test run for non-participants and €3,000 for participants.
What OCPP 2.1 adds for new projects
OCPP 2.1 builds on 2.0.1 and keeps its application logic compatible. It adds bidirectional charging, control of distributed energy resources, payment by a built-in or stand-alone card terminal, secure dynamic QR codes, prepaid cards and the ability to resume a transaction after a forced reboot.
EV roaming with OCPI: letting drivers charge on other networks
EV roaming lets a driver use one app or card across many networks. The open standard for it is OCPI, which connects the companies that serve drivers with the companies that run chargers.
What OCPI carries
The EVRoaming Foundation describes OCPI as a free, independent protocol between eMobility service providers, who have drivers as customers, and charge point operators, who manage stations. Its functions include authorization, reservation, tariff information, real-time charger status, session and charge detail records, billing, and remote start and stop for use from a mobile app.
Roaming hubs or peer-to-peer connections
OCPI works both bilaterally and through roaming hubs. Direct connections suit a few key partners; a hub suits operators who want many partners through one contract. The back office should support both, because partners rarely all choose the same route.
OCPI versions to plan for
The foundation lists 2.3.0 as the current version, in the process of becoming a CENELEC technical specification, with OCPI 3.0 in draft and a target release in mid 2027. Federally funded US networks are held to OCPI 2.2.1 under 23 CFR 680, so a US back end plans for 2.2.1 and a path to newer versions.
Payments and authorization: app, RFID, card readers and Plug and Charge
Drivers start sessions in several ways, and a network that supports only its own app turns away paying customers. The table compares the common methods.
| Method | How it works | What the software must do |
|---|---|---|
| Mobile app | Driver picks the charger and taps start | Remote start over OCPP, live status, payment on file |
| RFID card or fob | Driver taps a card on the charger | Token lists, local cache on the charger, account billing |
| Contactless bank card | Driver taps a card on a built-in or stand-alone reader | Pre-authorize, capture the final amount, issue a receipt |
| QR code | Driver scans a code on the charger to pay in a browser | Dynamic codes per session, no app install |
| Plug and Charge | Car and charger authenticate with ISO 15118 certificates | Certificate handling and contract lookup |
| Roaming token | Driver uses another network’s app or card | OCPI authorization and charge detail records |
Why do EV chargers need apps?
Many chargers do not have a payment screen, so an app is the simplest way to identify the driver, show the price and take payment. Apps also show live availability and send a notice when charging ends. Federally funded sites, though, must also accept contactless cards and cannot require a membership.
Plug and Charge and ISO 15118
The federal rule defines Plug and Charge as a method where the driver plugs in, identity is authenticated through ISO 15118 digital certificates, and the session and payment happen automatically. For funded chargers, software had to conform to ISO 15118-2 and be capable of Plug and Charge by February 28, 2024.
Card data stays with the processor
Card payments run through a certified reader and the processor’s own kit, so card numbers never reach the app or the back office. The PCI Data Security Standard covers any entity storing, processing or transmitting cardholder data; keeping that data out of your software keeps most of that work with the processor.
Launching a charging network?Tell us the charger models, the sites and how drivers will pay. A free proposal follows with the back office, app and roaming plan, scoped and estimated in writing.
NEVI-funded stations: the federal rules your charging software must meet
Chargers funded under the National Electric Vehicle Infrastructure program, and other publicly accessible chargers funded under Title 23, must meet the minimum standards in 23 CFR 680. Most of those standards land on software.
| Requirement | Section | Software work |
|---|---|---|
| OCPP 2.0.1 between charger and network (1.6J or higher before Feb 28, 2024) | 680.108 | Back end speaks OCPP 2.0.1 |
| OCPI 2.2.1 between networks | 680.108 | Roaming interface and partner onboarding |
| Switch network providers without hardware changes | 680.108 | Standard protocols, documented charger configuration |
| Contactless card plus a toll-free number or SMS; no membership | 680.106 | Card reader flow, phone or SMS session start |
| Remote monitoring, diagnostics, control, smart charge management | 680.114 | Operator tools and power controls |
| Keep charging when the network connection drops | 680.114 | Local authorization and offline session handling |
| Price in $/kWh shown before the session, fixed during it | 680.116 | Real-time pricing in app, charger and API |
| Average annual uptime above 97 percent per port | 680.116 | Uptime calculation and outage records |
| Free third-party API with station, port, status and price data | 680.116 | Public data API in OCPI terms |
| Quarterly and annual data submittal | 680.112 | Reporting exports |
- Every charger on OCPP 2.0.1, with the version recorded per unit
- OCPI 2.2.1 interface tested with at least one partner network
- Contactless card reader flow plus a toll-free number or SMS start
- Price in dollars per kWh shown before the session and held during it
- Uptime calculated per port each month with documented exclusions
- Public data API published and documented for third-party developers
- Quarterly data export produced from the billing records
Uptime above 97 percent and how it is counted
Each charging port must average more than 97 percent annual uptime, calculated monthly over the previous twelve months. A port counts as up only when its hardware and software are online and it dispenses the minimum required power. Outages caused by utility interruptions, vehicle faults, scheduled maintenance, vandalism or natural disasters are excluded, provided the operator can show the port would otherwise work.
Price shown before the session and held during it
The price must be displayed before charging starts, based on dollars per kilowatt-hour, and must be the real-time price; the price at the start of a session cannot change during it. Any other fees have to be clearly displayed and explained.
Quarterly data submittal
States and other direct recipients submit data quarterly: station and port identifiers, session start and end times with error codes, energy dispensed, peak power, payment method, port uptime and outage duration. The back office should produce that file from the same records it bills from.
Where the utility angle is covered
For grid-edge, demand response and how utilities handle these rules, see energy software development. For dealer, service-lane and fleet software around vehicles, see automotive software development.
EV charging API: open data for maps, apps and partners
An ev charging API publishes your stations, ports, status and prices so maps, navigation apps, fleets and partners can show them. For funded stations, the federal rule makes a free API mandatory.
Fields the federal rule requires
For funded stations, states and other direct recipients must ensure data is available free of charge to third-party software developers through an API, including station name or identifier, address and coordinates, operator and network names, status, access type and hours, number of ports, port identifiers, connector types, charging level, power rating, pull-through access, real-time port status and real-time price, with status and price in OCPI 2.2.1 terms.
APIs your own partners will ask for
Fleets want session and cost exports by vehicle, site hosts want revenue and energy by month, and finance wants settlement files. We build these as documented, versioned endpoints; see our API development page.
Load management, smart charging and fleet depots
Smart charging keeps a site inside its electrical limits and its energy budget. The software decides how much power each port gets, minute by minute.
Power sharing at a single site
The federal rule defines power sharing, also called automated load management, as dynamically limiting the output of individual ports at a station so the total power to all charging vehicles stays below a maximum. In OCPP this is done with charging profiles sent from the back office.
Depot charging and EV fleet management software
Fleets need vehicles charged by departure time at the lowest cost. EV fleet management software for depots schedules charging against routes, tariffs and site limits, and reports energy cost per vehicle. Telematics and maintenance belong with the wider fleet systems on our automotive page.
Utility programs and demand response
Some sites earn money by cutting load when the grid is stressed. That needs a link from the charging back end to the utility or aggregator platform; the rule also requires funded networks to be capable of secure communication with utilities, energy providers or local energy management systems.
White label EV charging software or a custom build?
White label ev charging software gets a network open quickly under your brand; a custom build gives you control of data, features and cost at scale. Many operators run a white label core and add custom apps, reports or billing around it.
| Approach | What you get | Good fit | Watch for |
|---|---|---|---|
| White label platform | A vendor back office and app under your brand | First sites, standard tariffs | Per-charger fees, data access, roadmap |
| White label plus custom parts | Vendor core with your own app, reports or billing | Most needs fit, a few do not | API limits of the platform |
| Custom back office and apps | Software built for your model and owned by you | Larger networks, fleets, charger makers | Needs certification planning and support |
When a white label ev charging app is the right start
If you have a few sites, standard pricing and no unusual billing, a white label ev charging app gets drivers charging fastest. Check that you can export all customer and session data, and that the contract lets you leave with it.
When custom ev charging software solutions pay off
Custom work pays off when fleet billing, energy contracts, depot schedules or charger resale do not fit any platform, when per-charger fees across a large network outweigh a build, or when the software is a product you sell.
Comparing ev charging software and platforms
Ask every vendor the same questions: which OCPP versions and certifications, which OCPI version and hubs, which payment methods, how uptime is calculated, what data you can export and what it costs to leave. Written answers make the comparison fair.
Uptime, monitoring and support after launch
A charging network is judged on whether the charger works when the driver arrives. Monitoring and support decide that more than any feature does.
Fault routing and first-line fixes
Error codes from chargers become tickets with the site, port and model attached. Many faults clear with a remote reset or an availability change, so the support desk tries those first and sends a technician only when needed.
Firmware updates by model
Updates are scheduled by charger model, during quiet hours, with results logged per charger. A failed update rolls back or is flagged before the morning rush.
When the network connection drops
Funded chargers must keep starting and finishing sessions when their link to the network is temporarily lost. The back office then reconciles the sessions the charger stored locally once the link returns.
Testing with simulated chargers
Before a release reaches real chargers, it runs against simulated ones that misbehave on purpose: dropped connections, late messages, odd error codes. Our DevOps services team runs that pipeline.
AI answers: how charging buyers ask assistants for a developer
Charge-point operators and fleet managers put questions to ChatGPT, Claude, Perplexity, Gemini, Microsoft Copilot and Google AI Overviews: which ev charging software providers support OCPP 2.0.1, who builds white label charging apps, or what a NEVI site needs from its software. Answers lean on pages that state specifics.
What assistants tend to cite
The Open Charge Alliance and EVRoaming Foundation pages, the federal rule text, certified product listings, vendor pages that name protocol versions and payment methods, and comparison tables. Pages that only say they build charging apps are rarely the ones quoted.
- Which ev charging software providers support OCPP 2.0.1 and OCPI?
- Who builds a white label ev charging app for a small network?
- What does a NEVI-funded site need from its charging software?
- How do I add roaming to my charging network?
- Which companies build depot charging software for fleets?
- How much does a charging station management system cost?
What a charging company should publish
Your supported OCPP and OCPI versions, certifications, payment methods, how you count uptime, your data API and a plain answer on pricing for site hosts. Our answer engine optimization work builds those pages.
How EV charging app development runs, phase by phase
We build in phases that each end in something you can test, starting with simulated chargers and ending with a pilot site. You see a working build every two weeks, with a short note on what changed.
| Phase | What happens | What you receive |
|---|---|---|
| Discovery | Charger models, business model, payment and roaming choices, funding rules | Written scope with acceptance tests |
| Protocol layer | OCPP back end against simulated chargers | Charger connections, sessions and commands working |
| Apps and portals | Driver app, operator dashboard, site-host portal | Installable builds every two weeks |
| Payments and roaming | Processor, card reader, RFID and OCPI partner links | Tested payment and roaming flows |
| Pilot | Real chargers at one site, logs reviewed each day | Issues fixed and a launch decision |
| Launch and support | Monitoring, alerts, firmware schedule, reporting | A support plan in writing |
What we need at the start
Charger make, model and firmware for each site, the business model (public, fleet, workplace or multifamily), payment processor preferences, any roaming partners and, for funded sites, the state program’s requirements.
Electric vehicle app development beyond charging
Some clients add trip planning, vehicle data or loyalty features. Electric vehicle app development of that kind reuses the same account, payment and map services, so we design them once.
Outgrowing a white label platform?List what the platform will not let you do: tariffs, fleet billing, data exports, branding. We will say whether an extension, a migration or a custom back end fits, in writing.
How much does EV charging app development cost?
Cost depends on how many charger models and OCPP versions you support, the payment and roaming methods, the portals, the funding rules and the support plan. A price follows the written scope.
| Driver | Lower effort | Higher effort |
|---|---|---|
| Charger models | One model on one OCPP version | Several makers on 1.6J and 2.0.1 |
| Apps | Driver app on one platform | iOS, Android, web, operator and site-host portals |
| Payments | App payments through one processor | App, RFID, card readers, QR and Plug and Charge |
| Roaming | None | OCPI with hubs and direct partners |
| Funding rules | Private sites | NEVI uptime, pricing, API and reporting |
| Energy | Fixed limits | Dynamic load management and utility programs |
| Starting point | Extend a white label platform | Full custom back office |
Keeping the first release lean
Launch with one charger model, app and card payments, one tariff structure and the operator tools support staff need every day. Add roaming, fleet billing and advanced smart charging once real sessions show where the value is.
Hardware and installation are separate
Chargers, electrical work and installation are quoted by the charger maker and qualified contractors. Our quote covers software, integrations and support.
How to choose among EV charging software providers
Choose a team that names protocol versions, payment paths and the uptime method before it shows screens, and that puts support in the scope. Every item in the table can be verified before a contract is signed.
| Requirement | How to check it |
|---|---|
| OCPP versions and test plan | Ask which versions they support and how they test against simulated and real chargers |
| Certification planning | Ask how they would prepare for Open Charge Alliance certification |
| OCPI roaming | Ask which version and how a new partner is onboarded |
| Card data kept out of your software | Ask for a diagram of the card’s path from reader to processor |
| Funding rules mapped | Ask for the 23 CFR 680 requirement-to-feature list |
| Uptime method | Ask how a port’s uptime is calculated and what is excluded |
| Code and data ownership | Read the IP clause: code, data and accounts should be assigned to you |
- A live demo of a simulated charger connecting, charging and disconnecting
- The list of charger models already tested and on which OCPP version
- A sample uptime report with its exclusions explained
- A sample charge detail record from a roaming session
- The support plan with response times and escalation
Questions to ask on the first call
What happens to a session when the charger loses its connection? How is a firmware update rolled back? How does a driver from a partner network get billed? Where does card data go? Who owns the code? Specific answers sort vendors quickly.
Why Progression as your EV charging app development company
One team covers discovery, apps, the back office, integrations, launch and support. Code, data and cloud accounts are yours from the first day, and a written scope and estimate come before any development.
Built on mainstream technology
The stack is mainstream: TypeScript with React and Next.js for web screens, Node.js and Python services, PostgreSQL and Redis, and React Native, Flutter, Swift or Kotlin for mobile, so hiring engineers to run it later is straightforward.
Product, launch and marketing in one place
A charging network also needs drivers and site hosts. Our SEO services and app launch work help the network get found once the software is live.
Related software and app development services
Charging software connects to vehicles, energy systems and connected devices. These pages cover the work around it.
- Automotive software development for dealers and fleets
- Energy software for utilities, grid-edge and demand response
- Enterprise apps for internal operations
- IoT apps for connected devices and telemetry
- Cross-platform app development
- SaaS development for charging platforms you license
- Cloud app development for charging back ends
- Operator and site-host dashboards
- Embedded software development
- MVP development for a first charging pilot
- Software consulting before you choose a platform
- Custom software development
Plan your charging software with a written scope
Tell us your chargers, sites and how drivers will pay. A free proposal follows with the back office, app, payment and roaming plan, plus a scoped estimate in writing.
Getting found in search
AI, AEO and what is changing
Paid media and lead generation
Websites and design
Choosing and working with an agency
Software and app development
Website design by industry and type
Web development, platforms and hosting
Social, content and brand
By industry and by situation
Frequently asked questions
How much does EV charging app development cost to launch a network?
What is OCPP software, and is it the same as a CSMS?
Is OCPP open source?
Why do EV chargers need apps?
Should we choose white label or custom EV charging software?
Which parts does an EV charging app development company build and hand over?
Which OCPP version should a new charging network support?
OCPP and OCPI: what does each protocol do?
What does 23 CFR 680 require from charging software?
How is charger uptime calculated for NEVI sites?
What is Plug and Charge?
Can drivers pay with a credit card instead of an app?
What is a charging station management system?
How do EV charging networks offer roaming?
Do you build EV fleet management software for depot charging?
Do you get chargers certified with the Open Charge Alliance?
How does smart charging work in charging software?
What happens if a charger loses its network connection?
Can you add features to our existing charging platform?
How long is an EV charging software build, start to pilot?
Who keeps the rights to the charging platform you write for us?
Do you support charging networks across other states and countries?
Launching a charging network?Tell us the charger models, the sites and how drivers will pay. A free proposal follows with the back office, app and roaming plan, scoped and estimated in writing.
Get a free marketing proposal
Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.