22/07/2026
Most founders think a ride-hailing app means building one app.
Ryotei VTC needed three — a passenger experience, a driver experience, and a fleet operator experience — all reading from the same live data, all compliant with European mobility regulations, all working together in real time.
Here is how we helped build it.
━━━
The problem Ryotei VTC came to us with
Urban ride-hailing looks simple from the outside — book a ride, get picked up, pay at the end. Underneath, it requires coordinating passengers, independent drivers, and fleet operators simultaneously, with accurate pricing, live tracking, and payment workflows that all have to agree with each other in real time.
Ryotei VTC needed a platform built for the French market specifically, which meant the engineering had to account for European mobility regulations from day one — not retrofit compliance after launch.
━━━
What we built through the Idea to MVP Programme™
This was not a single product. It was an ecosystem of three connected applications plus a centralised admin layer, all engineered through the Idea to MVP Programme™ to work as one coherent system.
→ A passenger mobile app with real-time ride booking and live driver tracking
→ A driver application covering onboarding, trip management, and earnings tracking
→ A fleet company portal for managing drivers, vehicles, and commission structures
→ An admin dashboard giving full visibility into ride monitoring, analytics, and user management
→ Secure payment workflows with complete digital ride history for every transaction
→ Location-based fare estimation and route calculation, accurate before the ride even starts
→ Scalable backend infrastructure supporting multiple vehicle categories without fragmenting the data model
━━━
The outcome
Passenger
app
Driver
app
Fleet
portal
30K+
Ride requests processed
500+
Drivers onboarded
100+
Fleet vehicles managed
Ryotei VTC is now a live mobility platform processing real rides across France every day — three applications, one underlying system, working in sync.
━━━
What this project taught us about building connected ecosystems
The hardest part of Ryotei VTC was never any single app. It was making sure the passenger app, the driver app, and the fleet portal never disagreed with each other — on price, on availability, on location, on commission.
That kind of consistency is only possible when the backend is designed as the single source of truth from the very beginning, with every application reading from and writing to it correctly. Build the three apps first and the data model second, and you end up with three products quietly drifting out of sync with each other — which in ride-hailing means wrong fares, missed pickups, and drivers who stop trusting the platform.
30,000+ ride requests later, the system holds because the architecture was designed to make disagreement between the apps structurally impossible.
━━━
If you are building a product that needs multiple apps or user types to operate as one coherent system, this is the kind of architecture decision that has to happen before the first screen is designed.
→ We take on a limited number of founders each month. Apply for the Founder Launch Programme™ at noorisys.com