Case Study - Android and iOS apps for a US business bank, shipped in about six weeks.
A US bank for small and mid-size businesses needed phone apps, not another browser tab. Two engineers built Android and iOS together: balances, cards, and the chat assistant that was already running on the server.
- Client
- Business bank
- Year
- Service
- Mobile, assistants
Overview
The client is a US business bank: checking, company cards, and credit lines for smaller firms. Until this engagement, every customer path lived in a responsive web app. Feedback kept returning to the same request. People wanted the account on the phone they already had in their hand.
The phone-app work had three jobs. Show balances and recent activity without a stale cache pretending to be live. Let a cardholder freeze, release, or adjust a limit. Put the bank’s existing chat assistant on the same screen, so a question about cash or spend did not require a second product.
One engineer took Android and one took iOS. They shared the API contract and the visual system so the two apps would not drift. Each used the current native toolkit for that platform, including the platform’s own concurrency and local store. The point was parity, not a clever abstraction that hid both.
The platform those apps call is a separate engagement. See the backend study.
What we did
- Android
- iOS
- Live balances
- Card controls
- Assistant on the phone
- To both stores
- 6 weeks
- Engineers, one per platform
- 2
- Shared with the server
- 1 contract