The ENBD mobile app and its siblings

Walk into the App Store from a UAE IP and you will see four ENBD-branded apps stacked beside each other: ENBD X, Liv X, Emirates Islamic, and businessONLINE X. They share a parent, a payments stack, a fraud system, and a regulator. They do not share a tone of voice, an information architecture, or, in many places, a feature roadmap. Each one was built for a different kind of customer doing a different kind of thing.

ENBD X is the conventional retail app. It replaced the older "Mobile Banking" app as part of a multi-year platform rebuild, and it now carries most of the bank's daily transactional volume. Its design language leans editorial: serif moments at the top of journeys, generous whitespace, and a deliberate pace that signals stability over flash.

Liv X is the youth-and-lifestyle app. It owns its own brand, its own colour palette, and a tone that reads closer to a fintech than to a bank. Liv prioritises in-app investments, savings goals, lifestyle offers, and a faster onboarding that suits a customer who arrived via a friend's referral rather than a branch visit.

Emirates Islamic ships its own retail app, anchored in Sharia-compliant products. The naming, the iconography, the calendar (which sometimes references Hijri dates), and the financing flows are all distinct. A customer cannot quietly drift between conventional and Islamic products through a single login: by design, the boundary is explicit.

businessONLINE X is the SME and corporate banking app. It is the one most often missed in a designer's tour, but it carries some of the most consequential decisions: payroll runs, multi-signatory approvals, bulk payments, and trade-finance touchpoints. Its primary user is not a consumer making impulse decisions; it is a finance manager with a spreadsheet open in another window.

The journeys that matter

If you imagine the retail app as a city map, eight neighbourhoods carry the most traffic. Onboarding is the gateway, where a customer becomes a customer through Emirates ID, biometrics, and central-bank-driven KYC. Domestic and international transfer is the daily street, the place an app proves itself to a new resident sending money home. Bill payment is the utility road, the long tail of DEWA, du, Etisalat, Salik, and dozens of merchants. Cards is its own quarter, with controls, statements, instalment plans, and rewards. Lending stretches across personal finance, auto, and home, and it is where compliance and conversion fight hardest. Buy-now-pay-later is a newer block, regulated under recent CBUAE guidance and shared with non-bank players. Wealth is the quiet boulevard for funds, deposits, and structured products. Foreign exchange runs underneath all of it, the rail and the margin both.

The chapters ahead will return to several of these in detail. For now, hold the map: most of what you design at ENBD will live in one of these neighbourhoods, and the patterns from one rarely transplant cleanly into another.

The shared infrastructure underneath

The four apps draw from a common core. Authentication runs through smartPASS, the bank's transaction-signing layer. Push and OTP flow through the same fraud and notifications stack. Transfers ride the same payment rails. Customer data and statements live in the same warehouses. That sharing is a gift and a constraint. A change to a shared component lands in four products at once, which means the review process is correspondingly heavier and the risk of unintended impact higher. As a designer, the right instinct is to find the shared layer first and ask "is this the right place to change it?" before touching a single screen.

Where journeys diverge

Two designers can sit beside each other and ship very different work because their app demands different idioms. ENBD X writes in full sentences. Liv X writes in fragments. Emirates Islamic frames moments around intention and Sharia compliance, where ENBD X frames them around outcome and speed. businessONLINE X often abandons the consumer-friendly metaphors entirely, because a finance manager wants the value first and the wrapper second.