Financial services · 2024
Consumer mobile application for a fintech startup
Took a payments product from Figma to both app stores, with offline-tolerant transaction history and a release pipeline the in-house team now runs themselves.
- Shipped from one codebase
- iOS + AndroidShipped from one codebase
- Transaction history and sync
- Offline-firstTransaction history and sync
- Release pipeline handed over
- In-houseRelease pipeline handed over
Overview
The situation
A funded startup with a designed product, a payments provider chosen, and no mobile team. They needed to be in both app stores, and they needed to not be dependent on us afterwards — which was stated up front and shaped everything.
What we built
A single React Native codebase for both platforms, with native modules only where the payments SDK required them. The decision that mattered most was treating offline as normal rather than exceptional: transaction history is readable without a connection, and actions taken offline reconcile when it returns.
- One codebase for iOS and Android, with native modules only where the SDK demanded them
- Offline-first transaction history with conflict-aware sync
- Store submission, review cycles and phased rollout set up and documented
- Crash and performance instrumentation wired in before launch, not after
How it was delivered
Release engineering was treated as part of the product from week one. By the time we handed over, the client's own engineers had shipped several releases themselves using the pipeline and the runbook we left behind. The mobile work is described in more detail under mobile applications.
Client named withheld by agreement. Figures we cannot publish are omitted rather than estimated.