The problem
A banking channel needs to make complex services understandable on a small screen. Accounts, cards, loans and payment journeys each bring their own integration and state-management concerns.
The same bank can also reach people through conversational channels. That requires a different interaction model while keeping the connection to banking services coherent.
My role
I was the lead mobile engineer on AFC Mobile. My work spans Flutter application engineering and its connection to banking APIs, across account information, card management, loans, billers, wallets and multicurrency journeys.
I also worked on AFC WhatsApp banking, including backend integrations and conversational loan, account-balance and statement flows. These products share a banking domain and serve different customer interactions. My lead mobile role applies to AFC Mobile.
The engineering approach
Mobile journeys need clear boundaries between presentation, application state and service responses. The user should be able to understand what is happening even when a service takes time or a request cannot complete.
On WhatsApp, a conversation needs explicit steps, response handling and hooks into services. Template-driven journeys and webhook processing make the flow model important alongside the API integration.
Why these belong together
The mobile application and the conversational channel show different strengths: a richer interface for mobile banking, and guided interaction in chat. The connecting skill is understanding the service journey beyond its first screen.
What it demonstrates
This work brings together mobile engineering leadership, integration work and banking-domain experience across two customer channels.