labs@atheron:~/industries/automotive/apps$ build app --web --mobile

Dealer and EV apps

Service drive apps with video, and EV charging apps.

Dealer and charging software is often bought as a bundle, with an app nobody enjoys using. We build the parts customers and technicians touch, a service app they actually use and a charging app that tells the truth about the charger, on top of the DMS or the charging hardware you already have.

Start a project See the example projects

// what matters here

What is different in this industry.

Customers see the work

Photos and short videos of worn parts reach the customer by text, so a recommendation is something they can see, not a line item.

Connected to the DMS

Repair orders, parts and customer records sync with your dealer management system, so advisors are not keying anything twice.

Chargers spoken to directly

The back office talks OCPP to the stations, so the app shows the real state of each connector and operations can reset a charger remotely.

Payments that work at the curb

Payment for service or charging runs through your payment provider, with receipts in the app and no card data stored on the phone.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appMobile app

Service app with video inspections

Hypothetical. Not a client, not a result.

// The problem

A dealer group's service departments write up inspections on paper, and customers decline recommended work they cannot see while advisors chase approvals by phone.

// What we would build

A technician app for multipoint inspections with photos and short videos, a customer link to see and approve work and pay online, and an advisor board showing every repair order's status, connected to the dealer management system.

// What is in it

Multipoint inspections on a tablet, with photos and video per item
Customer link by text to watch, approve or decline each item
Online payment and digital signature at pick-up
Advisor board with every repair order's status and wait time
Sync with the dealer management system for repair orders and parts
Reporting on approved and declined work by advisor and store

// Stack

React Native
Next.js
PostgreSQL
CDK or Reynolds DMS integration
Stripe
AWS

// estimate

Build: ≈ US$137,000 to US$210,000, delivered within 29 weeksCAD 195,200 to 298,600
Hosting: ≈ US$492 a monthCAD 700 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 6.9 to 12.4 weeks
Core features: 1.9 to 2.9 weeks
Full build: 1.4 to 1.9 weeks
First build on devices: 3.9 to 6.4 weeks
Testing and fixes: 0.4 to 0.9 weeks
Store submission: 0.9 to 1.9 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 to 2 weeks
API access approved by your DMS vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 39,040 to 59,720
Discovery 9.2%: CAD 17,958.40 to 27,471.20
Design approved 9.2%: CAD 17,958.40 to 27,471.20
Core features 7.6%: CAD 14,835.20 to 22,693.60
Full build 5%: CAD 9,760 to 14,930
First build on devices 20.1%: CAD 39,235.20 to 60,018.60
Testing and fixes 2.5%: CAD 4,880 to 7,465
Store submission 6.7%: CAD 13,078.40 to 20,006.20
Launch 9.7%: CAD 18,934.40 to 28,964.20
Holdback, 30 days after launch (10%): CAD 19,520 to 29,860

Start from this example

Example projectWeb appMobile app

EV charging app, OCPP back office

Hypothetical. Not a client, not a result.

// The problem

A regional charging network runs its stations from a vendor portal drivers never see, so they cannot tell which chargers are free, and payment fails at the worst moment.

// What we would build

An iOS and Android driver app to find, start and pay for a charge with live charger status, and a web back office that talks to the stations over OCPP for status, pricing, remote starts and fault alerts.

// What is in it

Map of stations with live status per connector
Start, stop and pay from the app, with receipts
Back office speaking OCPP to the chargers for status, pricing and remote resets
Fault alerts to the operations team before drivers call
Roaming with other networks through OCPI
English and French throughout

// Stack

React Native
Next.js
OCPP 1.6 and 2.0.1
OCPI
PostgreSQL
Stripe

// estimate

Build: ≈ US$132,000 to US$202,000, delivered within 28 weeksCAD 188,300 to 288,000
Hosting: ≈ US$492 a monthCAD 700 a month
Support: ≈ US$5,010 a monthCAD 7,135 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 6.9 to 11.9 weeks
Core features: 1.9 to 2.9 weeks
Full build: 1.4 to 1.9 weeks
First build on devices: 3.4 to 6.4 weeks
Testing and fixes: 0.4 to 0.9 weeks
Store submission: 0.9 to 1.9 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 to 2 weeks

How it is paid

Deposit 20%: CAD 37,660 to 57,600
Discovery 9.2%: CAD 17,323.60 to 26,496.00
Design approved 9.2%: CAD 17,323.60 to 26,496.00
Core features 7.6%: CAD 14,310.80 to 21,888.00
Full build 5%: CAD 9,415 to 14,400
First build on devices 20.1%: CAD 37,848.30 to 57,888.00
Testing and fixes 2.5%: CAD 4,707.50 to 7,200.00
Store submission 6.7%: CAD 12,616.10 to 19,296.00
Launch 9.7%: CAD 18,265.10 to 27,936.00
Holdback, 30 days after launch (10%): CAD 18,830 to 28,800

Start from this example

// questions

Questions we get about this.

Which dealer management systems can you connect to?

CDK, Reynolds and Reynolds, Dealertrack and others through their partner APIs, which usually need the DMS vendor's approval. We plan that approval into the work.

Which chargers can the back office manage?

Any charger that speaks OCPP 1.6 or 2.0.1, which covers most current hardware. We test with your models before launch.

Can drivers charge on other networks from our app?

Yes, through OCPI roaming agreements with those networks. The agreements are yours to sign; we build the connection.

Back to the industry: Automotive and mobility About the service: Web and mobile apps

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call