NKBM Mobile Bank
A bank's mobile application with massive view controllers, one full-time iOS developer, and a long future ahead of it. The job was not to rewrite it for them — it was to leave behind an architecture the person who stays can actually keep using.
What I did
- Introduced Clean Architecture to break up massive view controllers, separate responsibilities and make the app maintainable and testable.
- Implemented the initial architecture hands-on, so the team had a working reference rather than a document.
- Taught and supported the application's one full-time iOS developer in applying it consistently over time.
- Returned during later periods of high delivery demand, when the team needed additional senior capacity.
- Contributed to the redesign required after OTP acquired NKBM.
- Helped integrate the design system into the mobile application.
Why "enablement" is the right word
The measure of this engagement is not what I shipped while I was there. It is that the architecture survived after I left, through a bank acquisition and a redesign, and that one developer was able to carry it. A pattern nobody on the permanent team can apply is a pattern that gets abandoned the first time a deadline gets tight.
Scope, stated accurately
The 2020–2024 range describes recurring engagements, not continuous full-time work. The core iOS implementation had one full-time developer; I provided targeted senior architecture support and mentoring rather than managing a large mobile team.