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

Transit and parking apps

Rider apps, paratransit booking and parking permits.

Transit and parking software is used by everyone, including riders with a screen reader, a caregiver booking for someone else and an officer in the rain. We build rider apps, booking systems and permit portals on your open data and your own systems, and test them with the people who use them.

Start a project See the example projects

// what matters here

What is different in this industry.

On your open data

Built on your GTFS, GTFS Realtime and GBFS feeds, so the app shows what your systems already know.

For every rider

Screen readers, large text, plain language and several languages, tested with riders who use them.

Bookings without a queue

Paratransit and shuttle trips booked, changed and cancelled from a phone, with freed seats offered to the waitlist.

Permits without a counter

Residents apply and pay online, and officers check plates from an app.

// 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

Rider app and trip planner

Hypothetical. Not a client, not a result.

// The problem

A regional transit authority's riders check a PDF timetable and a third-party app that lags behind detours, and riders who use screen readers or speak another language struggle with both.

// What we would build

An iOS, Android and web app designed with riders, built on the agency's GTFS schedules and GTFS Realtime feeds: next departures, trip planning through OpenTripPlanner, service alerts pushed to the routes a rider follows, and nearby bike share docks from the operator's GBFS feed. Designed and tested for screen readers, large text and five languages.

// What is in it

Next departures and live vehicle positions from your GTFS Realtime feed
Trip planning across bus, rail and bike share
Alerts pushed only for the routes and stops a rider follows
Design research and testing with riders, screen readers and large text
Five languages, with your alerts translated by your staff or a vendor you choose
An admin screen to publish detours and notices

// Stack

React Native
Next.js
OpenTripPlanner
GTFS and GTFS Realtime
PostgreSQL
AWS Canada

// estimate

Build: ≈ US$124,000 to US$189,000, delivered within 29 weeksCAD 176,000 to 269,100
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: 8.9 to 14.9 weeks
Core features: 1.9 to 2.9 weeks
Full build: 0.9 to 1.9 weeks
First build on devices: 2.9 to 5.4 weeks
Testing and fixes: 0.4 to 0.9 weeks
Store submission: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 week
Access to your GTFS Realtime feeds: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 35,200 to 53,820
Discovery 9.2%: CAD 16,192.00 to 24,757.20
Design approved 9.2%: CAD 16,192.00 to 24,757.20
Core features 7.6%: CAD 13,376.00 to 20,451.60
Full build 5%: CAD 8,800 to 13,455
First build on devices 20.1%: CAD 35,376.00 to 54,089.10
Testing and fixes 2.5%: CAD 4,400.00 to 6,727.50
Store submission 6.7%: CAD 11,792.00 to 18,029.70
Launch 9.7%: CAD 17,072.00 to 26,102.70
Holdback, 30 days after launch (10%): CAD 17,600 to 26,910

Start from this example

Example projectWeb appMobile app

Paratransit and shuttle booking

Hypothetical. Not a client, not a result.

// The problem

A paratransit service books every trip by phone during office hours, sends reminders by hand, and cannot offer a freed seat to another rider in time.

// What we would build

A booking app and web portal for eligible riders and their caregivers, with trip requests, reminders by text or voice call, cancellations that offer the seat to the waitlist, and trips passed to and from your scheduling software through its API. Eligibility and booking rules are the ones your agency sets, and staff sign in with your organisation's accounts.

// What is in it

Trip requests, changes and cancellations from a phone, the web or a caregiver's account
Reminders by text or voice call, in the rider's language
Freed seats offered to the waitlist
Trips sent to and from your scheduling software
Call-centre screens that see the same booking the rider sees
Riders moved in from the current spreadsheets

// Stack

React Native
Next.js
PostgreSQL
Scheduling software API
SMS and voice API
AWS Canada

// estimate

Build: ≈ US$131,000 to US$200,000, delivered within 27 weeksCAD 186,200 to 284,700
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 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 5.9 weeks
Testing and fixes: 0.4 to 0.9 weeks
Store submission: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 week
Scheduling software API access: 1 to 4 weeks
Your IT security review and sign-on setup: 4 to 8 weeks

How it is paid

Deposit 20%: CAD 37,240 to 56,940
Discovery 9.2%: CAD 17,130.40 to 26,192.40
Design approved 9.2%: CAD 17,130.40 to 26,192.40
Core features 7.6%: CAD 14,151.20 to 21,637.20
Full build 5%: CAD 9,310 to 14,235
First build on devices 20.1%: CAD 37,426.20 to 57,224.70
Testing and fixes 2.5%: CAD 4,655.00 to 7,117.50
Store submission 6.7%: CAD 12,475.40 to 19,074.90
Launch 9.7%: CAD 18,061.40 to 27,615.90
Holdback, 30 days after launch (10%): CAD 18,620 to 28,470

Start from this example

Example projectWeb appMobile app

Parking permits and enforcement

Hypothetical. Not a client, not a result.

// The problem

A parking operator runs residential permits, citations and appeals on a FoxPro system, takes payments at a counter, and officers write plates on paper before typing them in.

// What we would build

A permit portal where residents apply, upload proof and pay through a hosted checkout, an Android app for officers that checks plates against valid permits and issues citations with photos, and an online appeal flow. It replaces the FoxPro system, with records moved across and checked, after a review of what the old system does.

// What is in it

Permit applications, proof uploads and payment online
An enforcement app that checks plates against permits and records citations with photos
Online appeals, with the officer's notes and photos attached
Payments through a hosted checkout, so card details never touch the system
Records moved from the old system, after a written review of how it works

// Stack

Next.js
Kotlin for Android
PostgreSQL
Payment provider hosted checkout
AWS Canada

// estimate

Build: ≈ US$138,000 to US$211,000, delivered within 29 weeksCAD 196,200 to 300,100
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
Written review of the old system: 0.4 weeks
Design approved: 6.9 to 11.9 weeks
Core features: 2.4 to 3.4 weeks
Full build: 1.4 to 2.4 weeks
First build on devices: 3.4 to 5.9 weeks
Testing and fixes: 0.9 weeks
Store submission: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 week
Payment provider account and hosted checkout: 2 to 6 weeks
Your IT security review and sign-on setup: 4 to 8 weeks

How it is paid

Deposit 20%: CAD 39,240 to 60,020
Discovery 7.9%: CAD 15,499.80 to 23,707.90
Written review of the old system 8.7%: CAD 17,069.40 to 26,108.70
Design approved 7.9%: CAD 15,499.80 to 23,707.90
Core features 8.1%: CAD 15,892.20 to 24,308.10
Full build 5.4%: CAD 10,594.80 to 16,205.40
First build on devices 15.8%: CAD 30,999.60 to 47,415.80
Testing and fixes 2.7%: CAD 5,297.40 to 8,102.70
Store submission 5.2%: CAD 10,202.40 to 15,605.20
Launch 8.3%: CAD 16,284.60 to 24,908.30
Holdback, 30 days after launch (10%): CAD 19,620 to 30,010

Start from this example

// questions

Questions we get about this.

Do you build on our GTFS feeds or replace them?

We build on them. Your scheduling team keeps publishing GTFS as it does today, and the app reads it.

Can the paratransit app work with our scheduling software?

If it has a published API or a file exchange, yes. We check yours before we quote.

Who sets parking enforcement and appeal rules?

Your organisation does. We build the permit, citation and appeal steps to the rules you set.

Back to the industry: Transit 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