Newsletter
Subscribe to our Flutter newsletter!
By submitting your email you agree to receive the content requested and to LeanCode's Privacy Policy

SoftNet: white-label banking app migration to Flutter

animation-background
animation-foreground
animation-logo
SoftNet logo
SoftNet Project Card

Migrating SoftNet's white-label mobile banking app, used by 85+ cooperative banks, to Flutter without a release freeze

SoftNet wanted to move its banking app without stopping releases. We migrated their mobileNet app screen by screen with Inlay, our open-source add-to-app framework, and Converge, our AI-native migration planner, rolling out corporate banking, BLIK, and other features.

Migrating SoftNet's white-label mobile banking app, used by 85+ cooperative banks, to Flutter without a release freeze

SoftNet wanted to move its banking app without stopping releases. We migrated their mobileNet app screen by screen with Inlay, our open-source add-to-app framework, and Converge, our AI-native migration planner, rolling out corporate banking, BLIK, and other features.
9
months to migrate a large banking app to Flutter
9
months to migrate a large banking app to Flutter
30+
years, SoftNet has been serving Poland’s cooperative banks
30+
years, SoftNet has been serving Poland’s cooperative banks
100+
banks across Poland run on SoftNet’s mobile banking systems
100+
banks across Poland run on SoftNet’s mobile banking systems
SoftNet Project Card
SoftNet - Banking software vendor

About the Client

SoftNet is a Kraków-based vendor with 30+ years in cooperative banking, supplying core, internet, and mobile banking systems to 100+ banks. Its portfolio covers the EuroBankNet core banking system, eBankNet internet banking, mobileNet app, eCorpoNet corporate banking, and AMLNet anti-money laundering system. Cooperative banks share its platform instead of building their own, making SoftNet a key technology partner. Its products have won the IT@BANK award several times.
White-label mobile banking app

About the App

mobileNet is SoftNet's white-label mobile banking app for retail and business customers of 85+ cooperative banks, released in a separate variant for every bank. SoftNet came to LeanCode with existing native Android and iOS apps and a need for a new corporate banking module. Their goal was to consolidate the two native codebases into a single Flutter stack that better fits their organizational structure, without slowing down releases.

Challenges

01-white-label-app-for-85-banks

One white-label app serving 85+ cooperative banks

One white-label app serving 85+ cooperative banks

Polish cooperative banks share one vendor platform instead of building their own apps. mobileNet is that platform's mobile channel: one codebase released in 85+ bank-specific variants, each with its own branding and configuration, for retail and corporate customers. Every architectural decision is multiplied across all of them, and every change has to work for every bank, on both platforms and on older phones.
02-two-drifting-app-codebases

Two native codebases that drifted apart over the years

Two native codebases that drifted apart over the years

mobileNet’s native Android and iOS apps had been developed separately for years. With well over a hundred screens on each platform, the two platforms had drifted apart in behavior and scope. Before migrating anything, every screen had to be paired across both platforms, and every difference settled, which at this scale is hard to do by hand.
03-softnet-app-used-everyday

Migrating while 85+ banks keep using the app every day

Migrating while 85+ banks keep using the app every day

The existing app could not stop. SoftNet's banks expect new features and regulatory changes on time, and each bank rolls out updates at its own pace. A full rewrite would have frozen development for many months and ended with one high-risk release for every bank at once.
04-step-by-step-app-migration

Why a step-by-step migration instead of a full rewrite

Why a step-by-step migration instead of a full rewrite

Together with SoftNet, we chose a Flutter add-to-app migration: Flutter screens embedded in the existing native app and released one by one. It keeps mobileNet shipping, lets each bank switch to new screens behind a feature flag, lets SoftNet's native team keep working, and gives a clear finish line: native code removed screen by screen instead of a launch date that keeps moving.
05-softnet-app-accessible

An accessibility gap ahead of the European Accessibility Act

An accessibility gap ahead of the European Accessibility Act

The European Accessibility Act made WCAG compliance a requirement for banking apps in the EU. Closing accessibility gaps separately in two native codebases, for 85+ bank variants, would have meant doing the same work twice.

SoftNet's native banking app moved to Flutter. For 85+ banks. Bank by bank. With no release freeze.

animation-background

Key features

Corporate banking: batch transfers and signatures

Polish transfers and BLIK

Currency exchange

Card management

Accounts, loans, deposits and history

Business users browse transfer batches, check details, and sign them in the app, with push notifications for operations awaiting approval. The module was built from scratch in Flutter and became the first add-to-app entry point into the native app, within the same white-label app for every bank.

Solutions

Flutter add-to-app: a new module first, then the existing app

Inlay: our open-source framework for the native-Flutter boundary

Converge: a migration plan built from the existing code

Bank-by-bank rollout behind feature flags

One design system for 85+ bank brands, accessible by default

A mixed team that leaves Flutter knowledge behind

Flutter add-to-app: a new module first, then the existing app

We started where the risk was lowest. First, we built a brand-new corporate banking module in Flutter and added it to the native apps with add-to-app, with no existing code to migrate. Then a self-contained flow with a single entry point from the native app. Only once Flutter had proven itself did we start migrating the existing retail banking app screen by screen.

SoftNet money transfers

Results

Most of the retail app already runs on Flutter

Seven months after the first line of Flutter code, most of the mobileNet retail banking app is already rebuilt in Flutter, and the full migration is forecast to finish in January 2027.

From one pilot bank to every bank in three weeks

The first migrated flows went live in one pilot bank and reached every bank within three weeks. Every flow since has followed the same path: one pilot bank, a few banks, all banks, then the native code is deleted.

A migration plan that comes from the code, every sprint

Converge made the migration measurable. It flagged behavior differences between the two platforms before work started, so they settled them once as product decisions instead of discovering them mid-sprint. It re-forecasts the end date after every sprint from the team's real pace. Management gets a one-page summary, the delivery lead a wave plan, and developers a screen-by-screen list.

Better accessibility and parity on both platforms

Every migrated screen meets WCAG, so accessibility is fixed once for both platforms. Android and iOS users of all SoftNet banks now get the same features and behavior, built on one design system, one set of business rules and one Flutter codebase for 85+ bank variants.

Review of our work with SoftNet

SoftNet_logo_z polem_ochronnym

LeanCode successfully migrated most of the retail app to Flutter, enabling us to cut tens of thousands of lines of duplicated native code. They brought their own tooling, including Inlay - their open-source framework for connecting native and Flutter code.

Oskar Szewczyk
Oskar SzewczykSoftware EngineerSoftNet
5.0
Reviewed onClutch
SoftNet_logo_z polem_ochronnym

LeanCode successfully migrated most of the retail app to Flutter, enabling us to cut tens of thousands of lines of duplicated native code. They brought their own tooling, including Inlay - their open-source framework for connecting native and Flutter code.

Oskar Szewczyk
Oskar SzewczykSoftware EngineerSoftNet
5.0
Reviewed onClutch

Other applications

Case Study of Credit Agricole Bank Polska App
Credit Agricole Bank Polska logo
Mobile Application

Credit Agricole Bank Polska

Case Study of Kontomierz app
Kontomierz logo
Web Application

Kontomierz

M-Check Case Study by LeanCode
Maspex logo
Mobile & Web Application

M-Check

Meet our expert

Let's schedule a 20-minute talk!

Łukasz Kosman / CEO at LeanCode
Łukasz Kosman, CEO LeanCode
Hi,

This is the initial scoping call with one of our experts. Its purpose is to get a better understanding of what you want to build. After this call, you will have an idea about your project's feasibility and the ballpark estimates.

Łukasz KosmanCEO at LeanCode