Menu

What we tested before launching a taxi service: money logic, commission splits and role boundaries
📰

What we tested before launching a taxi service: money logic, commission splits and role boundaries

DEV Community: reactnative·Dmytro Sadchenko·1 day ago
#SNdJtT10
#devtoreactnative#devto#dev#service#city
Reading 0:00
15s threshold

We built VOLT, a taxi service for a small city in Ukraine, from scratch: a dispatcher panel (15 screens), one mobile app for both passengers and drivers (23 screens), a service site, fares, city zones and a financial loop with driver balances and promo codes. Everything runs on one backend.

Stack: Laravel 13, React Native / Expo, MySQL, maps .

This post is not about screens. It is about the checks that decided whether day one would go well.

1. An overnight run of all the money logic

Before launch we did a separate overnight run of everything that touches money. It found the bug that would have broken day one: production still had the old fares. The first passenger would have paid 80 ₴ instead of the agreed 130 ₴, and the driver would have been short by half.

Lesson: test money logic against the data that is actually on production, not only against fixtures.

2. One source of truth for prices

The prices on the home page were once hard-coded by hand.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.