Services · Mobile app development · EV charging apps
We handle EV charging app development London operators can put in front of residents, cabbies and delivery drivers on day one. That means apps for lamp column and on-street chargers in borough parking bays, shared charging in blocks of flats, and rapid hubs used by taxi and private hire drivers, all connected to your chargers over OCPP and to other networks over OCPI.
Codeeo has 80+ people in Dubai, Riyadh and Karachi and 200+ delivered projects across the UAE and the US. We have no London office; we work remotely with London clients, and discovery, design reviews and demos all take place on video calls. Our clients rate us 4.7 from 23 Google reviews.
200+ companies servedFrom a first store to an ADX listed developer
Built for London kerbsides
Most Londoners park on the street or in a shared estate car park, so a London charging app is less about motorway trips and more about the bay outside the front door. Many boroughs have rolled out lamp column chargers in resident parking bays, often around 5 kW, alongside fast and rapid units procured through borough partnerships under the LEVI programme. Lower power lamp column units can sit below the 8 kW line at which the 2023 regulations require contactless on new chargers, which makes the app, an RFID card or another payment route more important there, not less. At the same time, the ULEZ now covers every London borough and electric cars no longer get a full congestion charge exemption, so commuters, cab drivers and van operators are switching and asking more of the network. These are the features we build for that reality.
Start and stop for low power on-street units, with clear guidance on which socket and cable the driver needs, a QR code on each column for fast lookup, and overnight session summaries. Charging that runs for ten hours on a residential street needs different notifications from a twenty minute rapid stop, so we tune alerts to avoid waking anyone at two in the morning.
Residents charge overnight without fuss or late night pings.
One back office split by council, so a contract covering several boroughs can report usage, faults and income for each authority on its own. Council officers get read only access to their area, with exports that match the reporting their LEVI agreements ask for.
Each borough sees its own numbers without a manual spreadsheet.
Many chargers sit in controlled parking zones where hours, permit types and maximum stays differ from street to street. The app shows those rules next to each charger so a driver from outside the zone does not plug in and collect a penalty charge notice.
Fewer fines and fewer angry calls about parking tickets.
Driver accounts for licensed cabs and private hire vehicles at rapid hubs, with live queue position, dedicated bays where hosts reserve them, and receipts that a driver can hand to an accountant. Taxis licensed in London for the first time from January 2018 onwards have had to be zero emission capable, so cab drivers are a large and demanding audience at rapid sites.
Working drivers spend less time circling for a free rapid bay.
Housing associations and managing agents need charging in shared car parks where bays are not assigned. We build booking slots, per flat billing and load management that stays inside the building's grid connection, with a simple view for the estate manager.
Shared car parks charge fairly without overloading the supply.
London's drivers speak dozens of languages. We design the app so instructions, fault reports and receipts can be offered in the languages your users actually speak, starting with the few your data shows matter most, and keep wording plain for those reading English as a second language.
More drivers complete a session without phoning for help.
A driver standing next to a dead column in Hackney or Lewisham can report the fault in three taps with a photo, and the report lands with the right maintenance contractor for that borough. Status updates go back to the driver, and repeat faults on the same unit are flagged so the operator can push the hardware supplier or the council for a replacement.
Broken units are fixed sooner and drivers know someone listened.
Connector status pushed within seconds through OCPI 2.2.1, published free and machine readable as the regulations require, so map apps and route planners show London drivers the same availability your own app does. This matters on narrow streets where a wasted trip means another lap of the block.
Status shown in third party maps matches what drivers find.
Pence per kilowatt hour shown before plugging in, with any overstay fee spelled out, and the price held for the whole session. Off-peak resident tariffs and different rates for each borough contract are handled in one tariff engine.
No surprises on the bill, even after a night on charge.
Who this is for
London charging is shaped by density, councils and the people doing the driving. A borough contract for hundreds of lamp columns has little in common with a rapid hub in a retail park on the North Circular. We focus on four groups, each with a different first release, and we keep the list honest: if your project fits none of them, we will say so on the first call. Outer boroughs such as Croydon, Barnet or Havering have more driveways and longer trips than Islington or Tower Hamlets, so we also plan for differences inside London itself.
You run residential chargers for one or more councils and report to each of them. Your app has to explain parking rules street by street, take payment on lower power units, and route faults to the right contractor. We build borough specific reporting and resident friendly screens first, then add memberships and off-peak offers once the contract reporting runs smoothly.
Council reporting and resident clarity first.
Your sites fill up with working drivers at shift changes and drivers lose income while they wait. We build queue visibility, bay reservations where the host allows them, account billing for driver cooperatives and fault alerts that reach an engineer quickly. Contactless stays available for occasional users, as the regulations expect at rapid units.
Waiting time is the metric drivers care about.
Residents in flats are asking for charging and the car park has a fixed electrical supply. We build shared booking, per flat billing and load balancing, plus a dashboard that shows the managing agent which bays are in use and what has been recovered from residents. Leaseholders and tenants often have different rights, so we let the agent set separate rules and billing for each group, and we keep personal data limited to what the billing actually needs.
Vans that return to a depot in Park Royal or along the Lea Valley at night need scheduled charging, while drivers top up on public rapid sites by day. We combine depot scheduling, roaming access through OCPI and reports by van and route, so operations and finance work from the same records. Drivers who take vans home to boroughs without off-street parking can be given access to on-street sites near where they live, with costs charged back to the company account.
Working together
A fixed scope first release suits most operators starting a borough contract or a new hub. A retainer after launch keeps the app in step with new boroughs, hardware and roaming partners. Larger programmes, such as moving thousands of on-street chargers to a new back office, often suit a dedicated team. Every option runs remotely by video call, and you see the backlog, builds and test results as we go. For a custom EV charging app development London project with several boroughs involved, we plan council reporting into the first sprint rather than treating it as an afterthought. Council officers can join review calls when a contract requires it, so they see reporting screens before launch rather than after.
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
Driver apps in React Native or native Swift and Kotlin, OCPP and OCPI services on Node.js or .NET, and hosting on AWS or Azure in a London or other UK region when contracts call for UK data residency. We pick tools your own developers can maintain later. Offline caching keeps the charger list and a session receipt visible when signal drops in an underground car park.
01Mobile
02Data and cloud
03Marketing and tracking
It depends on contracts, hardware and payment routes, so we price after discovery.
The main drivers are how many borough contracts need separate reporting, how many charger models you run, whether we manage chargers directly over OCPP, and how many roaming partners connect over OCPI. Shared estate charging with load management and multilingual content add work. A resident app on an existing back office is the lighter end. We write the scope down first, then give a fixed quote for it.
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