A booking app, and a payment gateway swapped under live traffic
Two jobs in one window. A home-services business needed booking across iOS, Android and web, and it needed to come off its existing payment gateway. The second job had to happen on a running system with customer money moving through it.
Two jobs, one window
A growing home-services business needed cross-platform booking, and separately needed to switch payment provider. Doing them in sequence would have meant two disruptions. Doing them together meant the riskier of the two happened while the newer of the two was still settling.
The migration
The gateway switch ran with no service interruption. Payments are the one part of a booking system where a maintenance window is not a minor inconvenience, because a customer who cannot pay does not come back later to try again, they book someone else. So the cutover was designed to be reversible at every step rather than fast.
One codebase, three surfaces
React Native with Expo, shipping to iOS, Android and web from one codebase. Native sign-in. An OCR-driven visa flow that reads the document rather than asking somebody to type it in, which removes the most common source of bad data at intake. Driver routes are optimised through maps, which is most of what decides whether a day of jobs actually fits into a day.
Stack
React Native (Expo) on the front. Node and Express with PostgreSQL behind it. Tap Payments for the gateway and OneSignal for notifications.
Want the same thing looked at in your business?
We map the process, find the part worth automating first, and give you a written scope with the phases separated. No obligation, and you keep the plan.