Past delivery
Car-owner driver-hailing application
UMobile
A driver-hailing product that lets a car owner invite a driver to operate their vehicle for riders.
The Challenge
A Delivery Shaped Around the Whole System.
Design a driver-hailing service around more than the conventional rider-and-driver relationship: a car owner supplies the vehicle, invites the driver who operates it, and riders request a trip.
What We Delivered
Cuesoft shaped and delivered the driver-hailing product around the car-owner, invited-driver and rider journeys that let the service operate as one connected system.
Product and Interface Design
Experience Design Is Part of the Delivery.
A Three-Party Product Journey
The product is designed around the relationship that makes UMobile distinct. A car owner makes a vehicle available, invites the person authorised to drive it and retains a clear connection to that operating asset, while riders still get a familiar way to request a journey.
Clear Boundaries Between Ownership and Driving
The interface separates the decision to provide a vehicle from the work of driving it. That makes the car owner’s invite meaningful in the product model instead of treating every driver as though they independently supplied the vehicle they operate.
System Architecture
The Technical Foundation.
Vehicle, Driver and Rider as Connected Records
The first-version product has to preserve a traceable relationship between the car, its owner, the invited driver and the trips riders request. That relationship is the foundation for the role-specific actions the application exposes.
A Role-Aware Mobility Service
UMobile is not only a rider marketplace. Its operating model gives owners, drivers and riders different responsibilities, so the product is structured around role-aware journeys rather than one generic account experience.
Engineering Work
Details That Make the Difference.
Owner-Initiated Driver Assignment
The car owner can invite the driver who will operate a particular vehicle. That makes assignment an explicit part of the product, allowing the service to model the real arrangement before a rider is matched to a trip.
Hailing Built on the Operating Relationship
Riders use a driver-hailing service while the product retains the relationship behind the available car and driver. The delivery joins a recognisable ride-request experience with the ownership model that differentiates the business.
Cost and Operating Design
Spend Less on Idle Infrastructure.
A Focused First Product Model
The early product concentrates on the operational relationship that matters to the service: one car owner, an invited driver and the rider journey. Defining those roles clearly avoids building generic fleet-management complexity before the core hailing model is proven.
Technical Capabilities
- 01Mobility product design
- 02Driver hailing
- 03Vehicle and driver operations
- 04Multi-role product journeys
- 05Mobile product delivery