Reconnect to the current trip
Socket.IO reconnect handling registers the user again and rejoins trip rooms, helping resume communication when the connection changes.
Commerce & Services
CREB.
On-demand transport
Connecting passengers and drivers through live trip updates, scheduled bookings, and fare negotiation in chat, with Stripe supporting purchases of driver credits.
- Implementation scope
- Mobile & real-time integrations
- Platform scope
- Android / iOS
Project image unavailable
The context
A workflow worth connecting.
Passengers and drivers share a journey but need different screens, actions, and updates. Live location and in-trip communication must reconnect to the right user and trip when connectivity changes.
What the project covers
- Immediate and scheduled trips with pickup and destination selection
- Live location, routes, and trip history
- Passenger–driver chat with fare offers
- Driver registration, vehicle details, and credit purchases
The connected workflow
- 01Request or schedule a trip
- 02Connect passenger and driver
- 03Track and negotiate
- 04Complete and review
Inside the implementation
Engineering decisions.
Coordinate location and UI state
Provider, service classes, and data models connect REST responses, route information, and real-time events across passenger and driver flows.
Integrate purchases within a specific flow
Stripe supports driver-credit purchases. Authentication and notifications use Firebase and related mobile integrations.
Scope & validation
The source documents Flutter development and backend integration. It does not establish Node.js/MySQL backend implementation. Stripe is described for driver credits, not as payment processing for every trip fare.
Have something in mind?
Let’s build something
that works together.
Tell me about your product, the people using it,
and the problem you want to solve.