[ MOBILITY ]

Carpooling & Ride Management Platform

2026Marketplaces & Consumer AppsIn-depth

What it is

A ride-sharing app with the safety and dispute machinery a real operator needs.

Client work is shown without identifying imagery

[ THE_PROBLEM ]

Why this existed

A ride platform without identity verification, an emergency path and a dispute queue is not an early version — it is a liability. Those are the parts regulators and users judge first.

[ WHAT_WE_BUILT ]

What we built

Rider and driver flows — publish a ride, find a ride, ride detail, active ride tracking and history — with Google Maps location search, route preview and permission handling. Around them: OTP phone auth, KYC document upload, an SOS button that transmits location, a dispute system with a support chat thread, rewards, notifications and profile management, all with real-time updates. Delivered first as a cross-platform build packaged for native app stores, then rebuilt on a modern native stack with a reactive backend, internationalisation and push notifications.

Publish a ride, find a ride, ride detail, active tracking and history
Maps location search, route preview and permission handling
OTP phone authentication and KYC document upload
SOS button transmitting location
Dispute system with a support chat thread
Rewards, notifications and profile management
Real-time updates across rider and driver views
Cross-platform build packaged for native app stores
Rebuilt on a native stack with a reactive backend, i18n and push notifications

[ HOW_IT_IS_USED ]

How a company uses it

A mobility operator, corporate commute programme or campus transport service launches with identity verification, an emergency path and a dispute queue on day one — the parts that get an operator shut down if they are missing.

Built with

ExpoIonicConvexSupabaseGoogle MapsCapacitor

[ COMMON_QUESTIONS ]

Questions clients ask

Why build safety features into the first version?

Because they are not features, they are preconditions. A mobility platform that launches without KYC, an SOS path and a dispute process will be shut down or sued before the growth features matter. Sequencing them first is not caution, it is the correct order.

Why was it rebuilt on a different stack?

The first build proved the product; the second was about real-time behaviour, push notifications and internationalisation, which the original stack made harder than it needed to be. Rebuilding a validated product on better foundations is a different and much lower-risk decision than rewriting a speculative one.

Does this work for corporate or campus transport?

Well, actually — closed-community deployments avoid the hardest part of consumer ride-sharing, which is trust between strangers. The identity, tracking and dispute machinery all still apply.

[ RELATED_WORK ]