Services · Mobile app development · EV charging apps
Codeeo provides EV charging app development USA networks can roll out across many states: driver apps for finding, paying for and tracking sessions, operator consoles that manage chargers from different manufacturers, and the reporting federal and state programs expect. In the US, a charging network answers to federal minimum standards for funded stations, to state weights and measures and consumer rules, and to a patchwork of privacy laws, so the software has to carry rules that vary by site without confusing the driver.
We design for growth from a handful of sites in one state to a network on several interstate corridors, with open protocols at the core so you can change hardware vendors, add roaming partners and meet new reporting rules without replacing the platform.
200+ companies across the US and the UAEFrom a first store to a listed developer
Platform capabilities
Most of the hard work in a US charging product sits below the driver screens. The federal minimum standards in 23 CFR Part 680, which apply to chargers funded through federal highway programs, set expectations for open communication protocols, payment without membership, price display, uptime and data reporting. States add their own layers: California has reliability and payment rules, Texas registers chargers through its licensing agency, and most states regulate how energy is measured and sold. Utilities differ in rates, demand charges and make-ready programs. A platform built for one state rarely scales cleanly to the next unless these differences were expected from the start. These are the capabilities we treat as the core of a national build, and the ones we bring forward when a network is planning interstate expansion.
A charger management layer built on OCPP, with support for version 2.0.1 alongside 1.6 for older hardware, so you can run chargers from several manufacturers under one console. Each model's quirks are documented and handled in the integration layer, not hardcoded into the app. Firmware updates are scheduled and tracked from the console.
Freedom to choose or change charger vendors as the network grows.
OCPI connections share locations, tariffs, sessions and settlement data with other networks and roaming hubs. Your drivers charge elsewhere with your app, and drivers from partner networks start sessions at your sites with theirs. Data sharing with third parties follows the same open approach federal standards expect.
Wider reach without asking drivers to install yet another app.
Guest payment through contactless cards, Apple Pay, Google Pay or a web checkout reached by QR code, alongside member accounts with stored payment. Pricing is shown per kilowatt-hour before the session starts, with idle and other fees listed clearly. Card data stays with your processor under PCI DSS.
Any driver can pay at any site, in every state you serve.
Support for ISO 15118 so compatible vehicles authenticate and pay automatically when plugged in, with certificate handling managed in the back end. Drivers whose cars do not support it keep using the app or a card, and the experience is consistent either way. Vehicles using the SAE J3400 connector and CCS are both supported.
Fewer steps for drivers whose vehicles already support automatic authentication.
Every status change, fault and failed session is logged per port, with excluded downtime tagged and evidenced. The console calculates uptime the way federal and state programs define it and produces the exports your state DOT or energy agency requests, on the schedule they set.
Reporting is accurate and ready before the deadline arrives.
Each site carries a profile for its state: required receipt fields, price disclosure wording, registration identifiers, reporting format and privacy notice. When a state changes a rule, you update its profile once and every site in that state follows, without a new app release.
Expansion into a new state is configuration, not a rebuild.
States regulate charger metering as weights and measures, generally following NIST Handbook 44 and the method of sale guidance in Handbook 130, which expect energy sold by the kilowatt-hour. The platform keeps metered values from the charger, shows them on receipts and flags sessions where readings look wrong.
Receipts that hold up to a driver complaint or a state inspection.
Sites sit under different utilities and grid operators, from ERCOT in Texas to CAISO in California and PJM across the Mid-Atlantic. The platform stores tariff periods and demand limits per site and schedules flexible charging accordingly, responding to utility demand response signals where you take part.
Lower energy cost across a network that spans many tariffs.
App screens built to WCAG guidance with screen reader support, large touch targets and clear contrast, plus site information that tells drivers about accessible spaces and reach ranges. This supports your ADA obligations and the accessibility guidance the US Access Board has published for charging stations.
Drivers with disabilities can find and use the right charger.
A help button on every session screen sends support the charger, port and last error automatically, with chat or call options. Every contact is logged against the site, which matters when programs require you to show how quickly driver problems were handled.
Faster help for drivers and a record your funders can check.
Who this is for
National charging is not one market. A highway network funded through a state NEVI plan, a retail chain adding chargers at stores in a dozen states, and a fleet electrifying depots in several regions share protocols but little else. Below are the starting points we see most, and what changes in the first release for each. Codeeo's team of 80+ works from Dubai, Riyadh and Karachi with clients across the US by video call, without local offices, and has delivered 200+ projects across the UAE and the US.
Operators building fast charging on designated alternative fuel corridors under state NEVI plans must meet 23 CFR Part 680 in full. The platform needs OCPP and ISO 15118 support, OCPI data sharing, guest payment, uptime tracking, customer service records and the reporting each state DOT requests. Because each state administers its own plan, reporting formats and contract terms vary. We build the shared core once and add state profiles as you win awards. Station data can also be shared with public locators such as the Department of Energy's Alternative Fuels Data Center so drivers find your sites in trip planners.
Federal standards in the core, state differences as configuration.
Retailers, hotel groups and convenience chains adding chargers across many locations want a branded experience tied to loyalty programs, consistent pricing logic and a single view of every site. They often use a third party network for operations and want the app to sit on top. We integrate with that network's APIs or build a platform you control directly. Store managers get a simple view of their own chargers, while head office sees the whole estate.
One brand, one console, many states.
Delivery, service and logistics fleets with depots in several states care about vehicle readiness, depot load limits and one bill for depot and public charging. The platform connects with telematics and maintenance systems, sets charging targets per route and handles utility demand charges that differ between depots. Drivers who charge at home can be reimbursed through the same platform using metered session records.
Readiness and energy cost across every depot.
Charger manufacturers increasingly sell a companion app and management platform with their equipment. We build white label driver apps and consoles that work with your hardware first but remain open to other chargers through OCPP, which buyers of funded projects often require.
Software that helps your hardware win funded projects.
How we engage
A fixed scope first release covers the core platform and a pilot state. After that, most networks move to a retainer that adds states, sites and roaming partners in planned increments. Larger operators often add a dedicated team that works alongside their own engineers over a longer program. In every model you get regular demos by video call, direct access to the repositories and project board, and written decisions on scope and timing. When federal guidance or a state rule shifts mid project, we assess the impact and agree any change in writing before work begins.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
Native or cross platform driver apps in Swift, Kotlin, Flutter or React Native. Back ends in Node.js or Laravel on AWS or Azure with message queues for charger traffic, OCPP and OCPI services, certificate handling for ISO 15118, and data pipelines for program reporting.
01Mobile
02Data and cloud
03Marketing and tracking
It depends on the number of states, charger models and reporting duties in the first release.
A single state pilot with one charger brand is a much shorter project than a platform launching across several states with roaming and federal reporting. We agree timing after discovery, once we have tested sample chargers and reviewed the reporting each program needs. Timelines most often slip on charger firmware quirks, so we test hardware first and tell you early if something will move the plan.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
Swift
Kotlin
Flutter
React Native
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio