In today’s world, launching a mobile banking app isn’t the end goal – it’s the starting point. The real challenge is building one that actually works for the people who use it, every day, under real business conditions.

At GET, we partnered with Banca Intesa Belgrade, a member of the Intesa Sanpaolo Group, to deliver BizMobi, a mobile banking solution built specifically for corporate clients in Serbia. From the ground up, our team handled the entire lifecycle – from product discovery, UX design, and system architecture to development, deployment, and long-term support. In this article, we’re sharing what we learned – not as a how-to guide, but as a practical look behind the scenes of a project shaped by actual business needs.

When Real Business Users Set the Bar

BizMobi isn’t aimed at casual users checking balances over coffee. It serves over 15,000 active users daily – corporate users managing high transaction volumes, authorizing payments, monitoring liquidity, and handling critical operations on the move. For them, reliability is non-negotiable. They don’t want bells and whistles; they want an app that works fast, keeps them informed, and doesn’t get in the way.

We designed BizMobi with three core expectations in mind:

  • Simplicity: Clear navigation, minimal steps, and immediate access to core features. Productivity matters, especially in high-pressure business environments.
  • Security: The app uses token-based authentication, digital signatures, and secure protocols (HTTPS, encryption) to protect data at every touchpoint.
  • Speed: With up to 100,000 transactions processed daily, performance optimization isn’t optional – it’s foundational. Backend services and mobile UI are engineered to respond quickly and consistently.

Compliance and Usability Aren’t Mutually Exclusive

Financial services are among the most regulated industries, and compliance can often feel like the enemy of usability. In this case, it wasn’t.

We worked closely with Banca Intesa’s legal, compliance, and security teams to make sure every feature – every screen – respected both regulation and real-life workflows. For instance, user-based access rights ensure that only authorized personnel can see or do certain things within the app. Secure in-app signing lets users review and approve transactions directly from their phones, with audit trails that hold up to scrutiny.

We didn’t hide these features in complexity – we made them a seamless part of the experience.

Choosing the Right Tech: Xamarin, and What Comes After

When we started developing BizMobi, Xamarin was a solid choice for delivering high-performance apps across iOS and Android with a shared codebase. It offered us the speed of cross-platform development without sacrificing native feel or access to device features.

BizMobi’s backend, built on .NET and RESTful APIs, connects to core banking systems and other enterprise platforms via REST, SOAP, and queuing protocols. The result? Stability, speed, and the ability to evolve.

Today, with Xamarin’s support officially ending, we’ve already begun the migration to .NET MAUI – ensuring that BizMobi stays modern, maintainable, and high-performing across platforms in the years ahead.

Good UX Isn’t Just Design—It’s a Business Enabler

In corporate banking, users aren’t exploring apps for fun. They’re focused, often pressed for time, and need things to “just work.” That’s why we emphasized:

  • Consistency across devices: Users shouldn’t have to “relearn” the app depending on where they’re accessing it.
  • Minimal effort per task: Whether they’re authorizing payments or checking account activity, every step is streamlined.
  • Immediate feedback: Submitting a payment? You’ll see confirmation right away. Getting a loan update? It’s reflected in your notifications. The interface responds the way users expect it to.

We designed for high-frequency use, assuming our users aren’t here to browse—they’re here to act.

The Invisible Engine: Backend Architecture

No matter how sleek the front end is, if the backend can’t keep up, the user will feel it. For BizMobi, we built a resilient backend hosted on a private cloud with load balancing and high availability features. This ensures continuity even under peak load.

Key components include:

  • REST APIs in .NET for efficient communication between frontend and backend.
  • MS SQL database for secure transaction storage.
  • Firebase notifications to keep users updated on payment statuses, loan progress, or account activity.

The result? A backend that scales, adapts, and never lets the user down.

From Idea to Execution: Product Management That Listens

What sets BizMobi apart isn’t just how it was built – but how it’s continuously improved. From the product side, we took a few principles seriously:

  • Start with real needs, not assumptions. We didn’t build “cool features.” We built what users asked for – faster payment approval flows, clearer notifications, reliable access to account statements.
  • Align stakeholders early. Everyone – from developers and UX designers to banking experts and compliance officers – shared a single vision from day one. That minimized backtracking and made room for faster delivery.
  • Agile in spirit, not just in name. Our sprints didn’t just produce code. They delivered tangible improvements based on real feedback. We launched, measured, learned, and adjusted.

And we’re still doing that.

Final Thoughts

BizMobi didn’t happen by chasing trends. It happened by asking the right questions, staying close to the users, and translating complex banking logic into simple mobile interactions.

The next time you open a mobile banking app, consider this: behind that screen is a whole world of architecture decisions, stakeholder negotiations, security protocols, product iterations – and a team that cares about getting it right.

We’re proud of what we’ve built with Banca Intesa, not because it ticks all the boxes, but because it works in the real world, for real business users. And that’s the standard we hold ourselves to.

If you’re working on something similar, let’s talk – schedule a discovery call! There’s always value in comparing notes – and asking better questions.

Let’s keep asking.