Digital BankingDigital Channels
A next-generation mobile platform for a participation bank
A participation bank built its digital channels on an orchestration layer and a reusable component pool (Core SDK + UI SDK) that are entirely the bank’s own asset. The bank was left with a lasting technology asset that can also serve its subsidiaries.
- 1/4The screen’s skeleton is produced from the 133 components of the design system — a definition, not code.
- 2/4The core SDK applies the business rules: session, authority, limits. No business rule lives on the client.
- 3/4The middleware connects to core banking; data reaches the screen through one contract.
- 4/4The screen is ready: one of 2,581. Changes ship without a store review.
- 2,581 screens
- Total screens generated from 133 unique designs
- 8× faster
- New screen development: from ~1 week to ~1 day
- 7× faster
- New app: from 5–6 months to 3–4 weeks
Problem
- Business rules on the client side
- The smallest rule change meant days of app store processes and high operational risk.
- High development cost
- With no ready components, every screen was coded from scratch.
- Replicability
- There was no shared infrastructure for the bank’s and its subsidiaries’ apps.
Solution
- Core SDK
- Central management of integration and workflows; repeated code disappeared.
- UI SDK
- With 144 reusable components generated from 15 modules, screens are assembled by configuration in minutes.
- Orchestration middleware
- Business rules in one place; even if the core system changes, the mobile app is unaffected.
Technical notes
- Native iOS/Android
- 15 modules, 144 components
- Server-defined screens
- Channel-independent rule layer
- Core banking adapters
- Component versioning
Related services
What comes next
Content and campaign updates in minutes instead of weeks; a core banking migration costs the mobile channel ~zero. The same architecture is strong enough to carry subsidiary apps and web channels too.
Let’s assess your project.
If you are planning a transformation of high scale and architectural demand, we draw up the risk map together in the first meeting.