What makes a good banking app today?
A great banking app should feel easy and intuitive from the very first tap. That means smooth onboarding, quick KYC, biometric login, everything needs to work seamlessly. It should be fast, responsive, and secure, without throwing too many prompts at the user.
But beyond checking balances, users want more: they expect to pay bills, apply for loans, manage cards… all without a hiccup. Security should be there, of course, but quietly in the background.
At the end of the day, the best apps just feel effortless, like a smart, personal finance assistant that users trust from day one.
Do you have a favorite feature in the SBP Digital Banking Suite, as PO & mobile lead?
Definitely onboarding among all of all our SBP Digital Banking suite offerings: onboarding, payments, accounts, cards. First impressions matter, and onboarding is the user’s very first touchpoint with the app. A smooth, intuitive flow directly impacts conversion and retention rates.
It’s also where UX, security, and innovation come together. From eKYC and document scanning to risk scoring, every step must balance ease of use with compliance. Onboarding is a complete journey, from installation to identity verification to the first transaction, and owning that end-to-end experience is both challenging and rewarding. That’s why I truly enjoy working on it.
Mobile moves fast: new devices, new OS updates, new user needs. What’s the hardest part, and what do you enjoy most?
The hardest part? Dealing with platform fragmentation, especially on Android with its endless devices and OS versions. And both iOS and Android love to drop breaking changes in updates!
But we tackle that with modular architecture and config-based UI. It keeps things flexible and easy to adapt for different regions or customers.
What I enjoy most is how fast we can make a difference. With mobile, you push a release and get real feedback almost instantly. It’s super rewarding.
Have you ever had to postpone or drop a feature you really wanted to ship?
Yes, two come to mind. One was the Community SDK, and the other was a screen for showing config-related errors. We had to push them back due to higher-priority needs from clients.
As a product evolves, especially when multiple clients are going live at the same time, you often face tough trade-offs. It’s all about weighing what’s critical now versus what can wait. Prioritization isn’t easy, but it’s essential to stay aligned with real business impact.
You work with different banks, how do you keep the app flexible for each one while staying consistent underneath?
We build the app with modularity in mind. Each feature, accounts, cards, payments, is like a Lego block. Banks can enable or disable what they need.
On top of that, we use JSON-based UI flows. That means banks can configure screens or flows without touching the code. Localization, branding, seasonal campaigns, like a Christmas promo, can be rolled out easily.
And to keep everything solid, we isolate business logic, stick to compliance standards like GDPR, and use feature flags to stay agile.
As a PO & mobile lead, how do you balance product vision and tech limitations in day-to-day work?
It’s a constant balance. I always ask: What problem are we solving, and for whom? That helps align business needs with technical feasibility.
As a Product Owner, I decide which features to build and in what order, considering if they serve one client or add value for all. At the same time, as a Mobile Lead, I work closely with developers to ensure those ideas can actually be built.
I manage two backlogs: one for new features, another for tech tasks like refactoring. So while we roll out things like a new onboarding flow, we also improve modularity or performance behind the scenes.
During grooming sessions, I act as the bridge between design, business, and tech, aiming for balance rather than compromise whenever trade-offs arise.
Is there a customer journey that really challenged or impressed you?
Yes – an onboarding flow we built for a client who needed remote account opening under five minutes, across several countries.
We had to support things like video KYC, document scans, and address checks, each with different regulations. The flow had to be fully configurable.
We used a single codebase, modular components, and config files to make it work. The switch from retail to business banking made it even more complex, but also more rewarding.
After 7 years at SBS, is there a moment that really stayed with you?
One that stands out happened recently. Just before go-live, a client told us many of their users didn’t have biometrics. But our app required it for certain actions.
So we quickly built a configurable solution with fallback of APP PIN, now the customer can configure APP PIN or can use both first biometric if available in device else fallback to APP PIN.
It wasn’t just a fix. It was about adapting fast to real user needs. One of our clients is already live with it, and seeing it work in the real world, it’s moments like that that stick.
Would you like to join the SBS (ex-Sopra Banking Software) adventure? Discover all our job offers on our Careers page by clicking on this link.