APEX BANK
I built and launched the bank’s iOS app from early prototypes to production banking workflows, onboarding 20K+ clients in three months.
- Role
- iOS Developer
- Scope
- Early product, banking flows, modular architecture
- Stack
- Swift, UIKit, VIPER, MVP, REST APIs, GCD
- Year
- 2023–2024
Current public APEX BANK product screens, shown as product context.
Context
Financial flows make ambiguity costly. Loading, retrying, duplicate actions, authorization, and partial failure needed visible and consistent behavior.
The application also had to remain maintainable as its product surface and backend contracts grew.
Responsibilities
- Built the iOS banking app from prototypes through launch.
- Implemented banking and transaction flows.
- Developed a micro-modular architecture using VIPER and MVP patterns.
- Integrated APIs and treated loading, error, and recovery as first-class states.
- Supported release preparation and the transition to production.
20K+ clients in three months.
Engineering decisions
Separate domains, not screens
Modules followed banking responsibilities so each flow could evolve without coupling unrelated areas.
Failure is part of the flow
Network, authorization, and processing states were designed as expected paths.
Clarity over novelty
Familiar interactions and explicit confirmation suit financial actions.
Release with operational context
Production support required understanding API behavior and user state.
Outcomes
- 20K+clients onboarded
- 3months after launch
- 1native banking application
- 2023–24documented work period
The launch combined rapid delivery with dependable transaction states, an architecture designed to grow, and production support for a banking product.
Metrics describe the documented 2023–2024 work period. Current screens come from the public App Store listing.