Tiger Charge: an EV charging app from map to payment
Tiger Charge lets drivers find a free charger, start it from their phone and pay from a prepaid wallet, and we built it. It covers the whole charge in one Android app, backed by OCPP links to the chargers.
- Android
OCPP chargersGoogle Maps Platform
- 10,000+downloads on Google Play
- 4.1 starsaverage rating from drivers
- Over 40%of charging sessions start in the app with no call to support
- 70%less manual billing work for the operator
The brief: make public charging feel simple
A charging network wanted one app that carries a driver through every step. Find a charger, check it fits the car, start it, watch it and pay. No call to the operator should be needed.
Drivers had real problems. Chargers went offline without warning, station details changed, and a wrong connector meant a wasted trip. Many drivers were new to electric cars and unsure how to start a charge.
The operator had problems too. Billing by hand took hours, and both sides needed a clean record of every session and payment. The app had to fix the driver’s day and the operator’s books at the same time.
Who the app is for
- The daily driver
Charges near home or work and wants a free, working charger with no detour.
- The first-time EV owner
Needs a start button that just works, with no technical steps.
- The long-trip driver
Looks for fast chargers along the route and short waiting times.
- The network operator
Needs every session, payment and invoice recorded without manual work.
Six problems and what we did about each
- 01The problem
Drivers struggled to find a working charger, and station details changed with no warning.
What we builtWe built map search with live availability, so drivers see the true state of each station before setting off.
- 02The problem
Cars use different connectors, and a mismatch wastes the driver’s time at the station.
What we builtFilters by connector, plus each charger’s details, let drivers confirm the fit with their car first.
- 03The problem
A failed payment could stop a charge before it even began.
What we builtWe built a prepaid wallet that drivers top up by card or digital wallet, so funds are ready before they plug in.
- 04The problem
New EV owners needed starting and stopping a charge to feel effortless.
What we builtWe designed a scan to charge flow with a choice of time or energy, so a session starts in a few taps.
- 05The problem
Drivers walk away while charging and miss the end, or a balance that is running low.
What we builtWe added live tracking and alerts for low balance, finished sessions and invoices, by push, text message and email.
- 06The problem
Drivers wanted to know about queues and fast chargers before choosing a station.
What we builtWe show estimated waiting times for stations within 25 km, and which ones offer fast charging.
What we built
Six screens carry the whole charge. They are designed screens with sample stations and prices, laid out to match the features of the app.
- 01
One map of every station
Drivers search a place and see the nearby stations on one map. Each pin shows how many chargers are free right now. Filter chips narrow the map to the connector their car uses, or to fast chargers.
A pin count is only useful if it is live. Each charger reports its own status to our servers, and the map reads that status from a fast cache. A charger that goes out of service turns grey within moments, not at the next manual update.
- 02
Station details before the trip
A station page lists every connector with its type, its power and whether it is free, in use or out of service. It shows the estimated wait, whether fast charging is available, and the rating from other drivers.
Ratings and reviews let drivers share what they found, such as a broken cable or a blocked bay. Other drivers then pick a better station, and the operator sees the problem too.
- 03
Scan, choose and start
At the charger, the driver scans its code. The app shows the charger it found, then asks how to charge: for a set time, or for a set amount of energy.
The estimated cost and the wallet balance sit on the same screen. If the balance is too low, the app says so before the start button, not after the cable is in.
- 04
Live charging status
Once charging starts, the screen shows the energy delivered, the power, the time so far and the cost so far. It also estimates when the charge will finish.
The driver can stop from the phone at any time. The app tells them when the charge is done, so they know when to return to the car.
- 05
A prepaid wallet
Drivers keep a prepaid balance and top it up by credit card, debit card or digital wallet. Every charge draws from that balance, so a session never fails at the payment step.
Payments go through a licensed payment gateway. Card details stay with the gateway; neither the app nor the operator’s servers ever hold them.
- 06
History, invoices and alerts
The history screen lists every charge and every top-up: where, when, how much energy and what it cost. Each session produces an invoice automatically.
Alerts arrive by push, text message and email: a low balance, a finished charge, an invoice and billing updates. The operator gets the same clean records for every session, station and payment.
Planning something like this? Talk it through with the team that built it, in a free 30-minute call.
Book a free 30-minute callHow it works
An EV charging app is really two systems that must agree. One talks to chargers in the field. The other talks to drivers and money. This is how we build both for a network like Tiger Charge.
The architecture
Chargers hold an open connection to the charger gateway. The app talks only to the API. Money moves only after a charger confirms what it delivered.
People and devices
Chargers on OCPP 1.6Report status, meter readings and session events
Newer chargers on OCPP 2.0.1The same events through the newer version
The app
Android appKotlin, for map, station, start, live status and wallet
- Code scannerReads the charger’s code through Google Play services
- Charging notificationLive progress while the car charges
Our system
OCPP gatewayHolds one secure WebSocket per charger and speaks OCPP 1.6 and 2.0.1
- Session engineTurns charger events into sessions and live status
App path
REST API in Node.jsOne entry point for the app, over HTTPS
- Stations and searchNearby stations, connectors, waits and ratings
- Alerts and invoicesPush through FCM, plus text message and email
- Wallet and ledgerTop-ups, holds and charges as ledger entries
Data
PostgreSQLStations, sessions, ledger and invoices
RedisLive charger status and nearby search
Outside services
- Payment gatewayTakes card and wallet top-ups
Google Maps PlatformMaps, places and routes, drawn inside the app
- The app to App path: Search, start, stop and top-up over HTTPS
- Payment gateway to Wallet and ledger: Signed payment events
- App path to OCPP gateway: Remote start and stop
- Chargers on OCPP 1.6 and OCPP gateway: OCPP-J over WebSocket
- Newer chargers on OCPP 2.0.1 and OCPP gateway: OCPP 2.0.1 messages
- OCPP gateway to Session engine: Status and meter values
- Session engine to Data: Live status and energy delivered
What happens when a driver scans and starts a charge
Eight steps run from the scan to the final bill. The wallet is checked before the charger is told to start, and the bill uses the charger’s own meter.
-
01Scan and chooseApp to APIThe app sends the charger code, the connector and the time or energy the driver picked.
-
02Hold the fundsAPI to WalletThe API checks the balance and places a hold for the estimated cost as a ledger entry.
-
03Ask to startAPI to GatewayThe API asks the gateway to start that connector for this driver’s token.
-
04Remote startGateway to ChargerThe gateway sends RemoteStartTransaction down the charger’s open WebSocket. The charger accepts or rejects it.
-
05Session beginsCharger to GatewayThe charger sends StartTransaction with its meter reading and gets a transaction ID back.
-
06Meter valuesGateway to APIMeter readings arrive at a set interval. The API turns them into energy, power and cost on the driver’s screen.
-
07Session endsCharger to GatewayThe charger sends StopTransaction with its final meter reading, when the driver stops or the target is reached.
-
08Settle the billAPI to WalletThe wallet charges the exact energy used, releases the rest of the hold, and the invoice goes out.
Talking to chargers with OCPP
OCPP, the Open Charge Point Protocol, is the open standard between a charger and the system that runs it. The OCPP 1.6 specification calls that system the Central System. Its JSON form, OCPP-J, runs over WebSocket.
The charger opens the connection and keeps it open. So the server can send commands at any time, and the charger can report the moment anything changes. That is what makes live status possible.
A charger starts with a BootNotification. The reply sets the heartbeat interval, and regular Heartbeat messages then show the link is alive. A charger that stops sending them is marked offline on the map.
Each connector reports its state through StatusNotification. OCPP 1.6 defines nine states: Available, Preparing, Charging, SuspendedEV, SuspendedEVSE, Finishing, Reserved, Unavailable and Faulted. We map them to three words a driver understands: free, in use and out of service.
Starting, metering and stopping a session
The app never talks to a charger. It asks our API, and the API sends RemoteStartTransaction with the driver’s token and the connector number. What happens next depends on the charger’s AuthorizeRemoteTxRequests setting, so we read it during setup.
When charging begins, the charger sends StartTransaction with its meter reading and a timestamp. The server replies with a transaction ID that ties every later message to this session.
During the charge, the charger sends MeterValues. MeterValueSampleInterval sets the time between samples, in seconds. The default measurand is Energy.Active.Import.Register, the meter reading of energy taken from the grid. We bill on that reading, not on an estimate.
At the end, StopTransaction carries the final meter reading. The difference from the start reading is the energy the driver pays for. Time-based charges stop on our side when the time runs out, with the same final reading.
Newer chargers speak OCPP 2.0.1. There, one TransactionEvent message replaces StartTransaction, StopTransaction and the transaction meter values. We write the session engine around our own session model, so both versions feed the same records.
Running the gateway in Node.js
Node.js suits a gateway that holds thousands of mostly quiet connections. We build on the open-source ocpp-rpc library, which implements the OCPP-J remote call layer for 1.6, 2.0.1 and 2.1. It can serve several protocol versions from one endpoint and validate every message against the official schemas.
Security comes in profiles. The Open Charge Alliance’s security guide says OCPP 2.x certification requires Security Profile 2, which is TLS with basic authentication. Security Profile 3 adds client certificates for the charger. ocpp-rpc supports all three profiles, and we never run Profile 1 on an open network.
Finding the nearest free charger
Station search must be fast, because drivers often search on the move. We keep each station’s location in Redis and use the GEOSEARCH command with BYRADIUS. It returns stations within a set distance, nearest first, such as the 25 km the app uses for waiting times.
Live charger status also lives in Redis, updated by every StatusNotification. PostgreSQL keeps the permanent records: stations, connectors, sessions, payments and invoices. Redis answers the frequent reads, and PostgreSQL keeps what must never be lost.
The map itself uses Google Maps Platform. On Android, the Maps Utility Library’s ClusterManager groups pins when the driver zooms out. Routes come from the Routes API, and directions open with one tap.
Google’s Places API can also return EV charging details for public places through the evChargeOptions field. That helps when an operator wants to show stations from other networks. For the operator’s own chargers, OCPP status is always the better source.
Scanning a charger without camera permission
Google’s code scanner API reads codes without the app asking for camera permission. Google Play services does the scanning and hands back the result. That means one fewer permission prompt for a first-time driver standing at a charger.
The code holds the charger and connector identity. We always confirm the found charger on screen before starting, so a driver never starts the wrong bay.
A wallet that always balances
Charging is a physical service, so Google Play billing does not apply. Google’s payments policy says Play billing must not be used for physical services. Top-ups therefore go through a regular payment gateway.
Every top-up request carries an idempotency key. Stripe’s API documentation, for example, explains that a key lets a client retry safely without performing the same operation twice. A dropped connection then never creates a second charge.
The gateway confirms payments through signed webhooks. Stripe’s guide says to verify each event’s signature and to track event IDs, because the same event can arrive more than once. Only a verified event adds money to a wallet.
The balance itself is a ledger, not a single number that gets overwritten. Each top-up, hold, charge and refund is a new entry. Stripe describes its own internal Ledger as built on double-entry bookkeeping, so every movement of money is fully accounted for. We follow the same idea at a smaller scale.
Two charges can try to use one balance at the same moment. We take a row lock with SELECT FOR UPDATE inside a PostgreSQL transaction, so the second charge waits for the first. The balance can never go below zero by accident.
Alerts while the car charges
Firebase Cloud Messaging delivers the push alerts: low balance, charge finished and invoice ready. Text messages and email carry the same alerts and the invoice, for drivers who switch off push.
Android now offers Live Update notifications for ongoing tasks the user started, such as active navigation or a delivery in progress. A charge in progress fits that pattern, so newer phones can keep its progress on the lock screen.
Roaming and open standards
Many drivers would rather use a single app and wallet across networks. OCPI, the Open Charge Point Interface, is the protocol for that. It connects the companies that run chargers with the companies that serve drivers.
OCPI covers real-time charger status, tariffs, sessions and billing, either directly or through a hub. Building our own session model around open standards means a network can add roaming later without rebuilding its app.
The stack and why we chose each part
| Layer | Technology | Why we chose it |
|---|---|---|
| Mobile app | Native access to maps, the code scanner and ongoing notifications, written in a modern, typed language. | |
| Backend | Handles many open charger connections well, and shares one language across the API and the gateway. | |
| Charger communication | The open standard that chargers from many makers already speak. | |
| Database | PostgreSQL keeps sessions, the ledger and invoices safe. Redis answers live status and nearby search fast. | |
| Maps and location | Maps, place search, clustering and routes that drivers already know how to use. | |
| Payments | Card payment gateway | Cards and digital wallets for top-ups, while card numbers never touch our code or databases. |
| Notifications | Reaches every driver, including those who switch off push alerts. | |
| Cloud | Managed hosting for the API, the gateway and the databases, which scales as the network grows. |
The build plan
This is how we would plan a network app like Tiger Charge today, phase by phase. The charger link comes first, because every screen depends on it.
- DiscoveryWeeks 1 to 2
- List the charger models and their OCPP versions
- Agree time and energy pricing and the wallet rules
- Pick the payment gateway and message providers
- Clickable prototype of the map and start screens
- Charger gatewayWeeks 2 to 8
- OCPP-J gateway in Node.js with ocpp-rpc
- Boot, heartbeat and status handling
- Remote start and stop, meter values
- Security Profile 2 or 3 on every charger
- API and walletWeeks 5 to 12
- Station search with Redis GEOSEARCH
- Ledger-based wallet with holds and settlement
- Top-ups with idempotency keys and verified webhooks
- Automatic invoices for every session
- Android appWeeks 6 to 15
- Map with live pins, filters and clustering
- Station pages, ratings and reviews
- Scan to charge, live status and stop
- Wallet, history and invoices
- Alerts and waitsWeeks 12 to 16
- Push, text message and email alerts
- Ongoing charging notification
- Waiting-time estimates for nearby stations
- Fast-charging details on map and station pages
- Testing and launchWeeks 15 to 20
- Tests against charger simulators and real chargers
- Payment tests in the gateway’s test mode
- Staged rollout on Google Play
- Monitoring and a 3-month fix period after launch
- 01Weeks 1 to 2
Discovery
- List the charger models and their OCPP versions
- Agree time and energy pricing and the wallet rules
- Pick the payment gateway and message providers
- Clickable prototype of the map and start screens
- 02Weeks 2 to 8
Charger gateway
- OCPP-J gateway in Node.js with ocpp-rpc
- Boot, heartbeat and status handling
- Remote start and stop, meter values
- Security Profile 2 or 3 on every charger
- 03Weeks 5 to 12
API and wallet
- Station search with Redis GEOSEARCH
- Ledger-based wallet with holds and settlement
- Top-ups with idempotency keys and verified webhooks
- Automatic invoices for every session
- 04Weeks 6 to 15
Android app
- Map with live pins, filters and clustering
- Station pages, ratings and reviews
- Scan to charge, live status and stop
- Wallet, history and invoices
- 05Weeks 12 to 16
Alerts and waits
- Push, text message and email alerts
- Ongoing charging notification
- Waiting-time estimates for nearby stations
- Fast-charging details on map and station pages
- 06Weeks 15 to 20
Testing and launch
- Tests against charger simulators and real chargers
- Payment tests in the gateway’s test mode
- Staged rollout on Google Play
- Monitoring and a 3-month fix period after launch
Testing and release
Charging apps fail in the field, not on a desk. A charger reboots mid-session, a phone loses signal in an underground car park, or a payment event arrives twice. So we test the paths that cost drivers and money.
Chargers, real and simulated
We run a charger simulator that speaks OCPP-J, so every message and fault can be replayed on demand. Then we test on each real charger model the network uses, because makers read the standard in different ways.
We cut the network mid-session and reboot chargers on purpose. The session must still close with the right meter reading and the right bill.
Money paths
Every payment path runs in the gateway’s test mode: top-up, failed card, refund and duplicate webhook. After each run, the ledger must balance to the penny, and every session must have one invoice.
On the road
We test the app in places with weak signal, because that is where many chargers are. A driver who loses signal must still be able to stop a charge once the phone reconnects.
Staged release
We release through Google Play’s testing tracks first, then roll out to a share of drivers. Start success rate and payment errors decide when the rollout widens.
Results
Tiger Charge now helps drivers find chargers and pay with far less effort, and it gave the operator clean records.
- 10,000+downloads on the Google Play Store
- 4.1 starsaverage rating from drivers
- Over 40%of charging sessions start in the app with no call to the support team
- 70%less manual billing work, thanks to the prepaid balance and digital payments
Drivers plan stops with more confidence, since free chargers and connector types show up before they arrive. Fewer trips end at a busy or unsuitable charger.
Automatic invoices and the transaction history give the operator a clear record of every session, station and payment. That record also supports the business’s tax and audit work.
What the client says
-
“Drivers want three things: find a working charger, start charging without fuss and pay without surprises. AppAgentix built the Android app, the prepaid wallet and the link to our chargers. Live charger status is accurate, starting a session is a scan and a tap, and the wallet settles the right amount even if the connection drops. The app has passed 10,000 downloads with a 4.1 star rating, and our manual billing work has dropped sharply.”
Michael L.Product Manager, Tiger Charge
Since launch
A charging network keeps changing after launch, as new chargers and new drivers arrive. These are the improvements an app like this receives in its first six months.
- 01More charger models connected
New charger models added to the gateway, each tested against the simulator and on site.
- 02OCPP 2.0.1 support
The session engine taught to read TransactionEvent messages from newer chargers.
- 03Offline chargers flagged faster
Missed heartbeats and Faulted status turn a pin grey and alert the operator.
- 04Better waiting-time estimates
Estimates refined using recent session lengths at each station.
- 05Charging progress on the lock screen
An ongoing notification shows energy and time while the car charges.
- 06Payment monitoring
Failed top-ups and webhook errors tracked, with alerts to the team.
- 07New Android versions supported
Each new Android release tested and supported before it reaches drivers.
Want a result like this for your own product? Get a written view of scope, time and price within two working days.
- 95%+ delivered on or before the agreed date
- 60% of clients come back for a second project
- 3 months of fixes after launch in the build price
What this would cost to build today
These are our published prices, in pounds, excluding VAT, as of November 2026. An app at Tiger Charge’s scope, with its own charger gateway and wallet, sits at the top of the first version range.
- Discovery£3,000 to £6,0002 weeks
Charger and OCPP survey, pricing and wallet rules, clickable prototype and a fixed quote. It comes off the build price if you continue.
- First version£15,000 to £40,0008 to 14 weeks
An Android app with map, scan to charge and live status, an OCPP gateway and one way to pay.
- This caseFull app on iPhone and Android£40,000 to £90,0004 to 8 months
Both platforms, prepaid wallet with ledger, alerts by push, text and email, waits, reviews and invoices.
- Support and runningfrom £750 a monthMonthly
New charger models, OS updates, fixes and monitoring. Minimum 3 months, then 30 days’ notice.
- Fixes after launch are included in the build price for 3 months.
- Cloud hosting, map usage, text messages and payment fees are billed by your providers and grow with use.
- Chargers must speak OCPP. We check each model during discovery.
Questions about building an EV charging app
What is OCPP used for?
OCPP, the Open Charge Point Protocol, connects chargers to the system that runs them. Chargers use it to report their status and meter readings. The system uses it to start and stop charges remotely, which is how an app can start a charger.
How does OCPP work?
In its JSON form, OCPP-J, each charger opens a WebSocket connection to the central system and keeps it open. Both sides send short JSON messages, such as StatusNotification, StartTransaction and MeterValues. Secure setups use TLS, with a password or client certificates.
Which EV chargers support OCPP?
Most networked public chargers support OCPP 1.6, and newer models add OCPP 2.0.1. Support varies by model and firmware, so we test each model the network uses before launch. Tiger Charge links to its chargers through OCPP.
Do you have to have an app to charge an EV?
Not always. Some chargers take a card or a payment tap at the unit. An app adds live availability, connector filters, starting from the phone, a prepaid wallet and a record of each past charge.
Is there an app to track EV charging cost?
Yes. A charging app like Tiger Charge records each session with its station, time, energy and cost. Drivers see the cost as they charge and get an invoice when it ends.
How much does it cost to build an EV charging app?
With us, a first version on Android with an OCPP gateway costs £15,000 to £40,000 and takes 8 to 14 weeks. A full app on iPhone and Android with a wallet costs £40,000 to £90,000 over 4 to 8 months. Prices exclude VAT.
Planning an EV charging app?
Tell us about your chargers and your drivers. A developer reads your brief. We reply within 30 minutes.



