Field-service scheduling and payments mobile app

Problem

The client had finished designs after a stalled earlier developer engagement and needed a working product that lets farriers manage barns, horses and recurring services and get paid quickly, often from locations with poor connectivity.

Solution

The team built a React Native app on a Dockerised self-hosted Supabase backend with RPC and edge functions, server-side search and pagination, Twilio OTP sign-in and Spanish-ready localisation. Farriers send invoice links by SMS or email; clients pay by card or bank transfer on a responsive web app with tips, saved payment methods and auto-charge through Stripe Connect. Later work added offline-first queued sync, team accounts with roles, OneSignal push notifications triggered on payment, in-app purchases, CSV exports for accounting, and two fee-model reworks migrated safely on live data.

Key features

• Barns, horses and recurring service scheduling
• Phone one-time-passcode sign-in
• Invoice links by SMS and email
• Card and bank payments with tips, saved methods and auto-charge
• Companion web payment app
• Offline-first mode with queued sync
• Team and organisation accounts with invites
• Push notifications on payment
• In-app purchases on both stores
• CSV exports for accounting and tax
• English and Spanish localisation structure

Tech stack

• App Store Connect
• Apple In-App Purchase
• AsyncStorage
• Docker
• Figma
• GitHub
• Google Play Billing
• Google Play Console
• NetInfo
• OneSignal
• PostgreSQL
• React Native
• Redux
• SendGrid
• Stripe Connect
• Stripe Elements
• Supabase
• Supabase Edge Functions
• TestFlight
• Twilio
• Twilio OTP
• Vercel