Mobile Banking App UX in the Middle East: Onboarding, Trust and KYC Without the Drop-Off

Good mobile banking app UX in the Middle East comes down to three things: onboarding that asks for the minimum at each step, KYC that feels like a formality rather than an interrogation, and trust signals that appear before anyone is asked to photograph their ID. Get those right and most of the drop-off disappears. Below is how we approach banking app design for Saudi Arabia, the UAE, Lebanon and the wider GCC, and where the usual mistakes happen.

Why onboarding is where mobile banking apps lose customers

A banking app has a harder first impression to make than almost any other product. Before a customer sees a single balance, they are asked to prove who they are, agree to terms they will not read, set up security they do not yet understand, and wait for a decision they cannot see. Every one of those steps is a place to leave.

Most drop-off is not caused by the regulation itself. It is caused by the way the regulation is presented: long forms with no sense of progress, document capture that fails silently, error messages written by compliance rather than for people, and a wall of permissions requested on the first screen. The underlying requirements from SAMA, the CBUAE or a central bank elsewhere in the region are broadly similar. The experience of meeting them varies enormously between apps.

When we designed MyBLF, a mobile banking app for a Lebanese bank, the onboarding work started with one question: what does a person need to feel at each step to keep going? The answer shaped the sequence, copy and confirmation moments more than any screen pattern did.

KYC onboarding UX that people actually finish

KYC is where good intentions meet the camera. The flow has to collect identity documents, verify a face against them, confirm an address and sometimes a source of income, all on a phone, often in bright sunlight or a dim living room. A few principles hold across every market we work in.

• Explain before you ask. One short screen that says what will be needed, roughly how long it takes and why it is required removes most of the anxiety. People abandon flows they do not understand far more often than flows that are long.
• Make capture forgiving. Detect document edges automatically, show a live preview, allow a retake without restarting the step, and say exactly what went wrong when it does. “Image unclear” is not feedback; “Move away from the light behind you” is.
• Use national ID sign-in where it exists. Saudi Arabia and the UAE both offer national digital identity schemes that can pre-fill and verify much of what KYC requires. Design the flow around them, with a manual fallback, and most typing errors on the fields that matter disappear.
• Show progress honestly. A stepper that shows where someone is, what is left and what has already been accepted turns a bureaucratic process into a finite one.
• Separate the decision from the data. If verification takes time on the back end, say so, let the person explore a limited version of the app, and notify them when the account is ready. Making someone watch a spinner is a guaranteed exit.

None of this changes the compliance requirement. It changes how the requirement feels, which is the whole point of KYC onboarding UX.

Trust is designed, not declared

Every banking app says it is secure. Very few show it in ways a nervous first-time user can read. Trust in a mobile banking app is built through dozens of small, consistent signals: a clear confirmation before any irreversible action, a receipt that looks like a receipt, biometrics that are offered rather than forced, and session timeouts that explain themselves instead of silently logging people out mid-transfer.

Confirmation moments carry particular weight in Lebanon, where confidence in banking has been severely tested and people want to see immediately, in plain language, that a transfer has gone through. The principle travels. In Saudi Arabia and the UAE, where customers hold accounts across several banks and switch freely, the app that confirms, explains and never surprises is the one that keeps the salary account.

Trust also means restraint. Asking for contacts, location and notification permissions on first launch, before any value has been shown, reads as grasping. Ask for each when it is needed, with a sentence that says why.

Banking app design in Saudi Arabia and the UAE: what is different

The fundamentals of mobile banking app UX travel well, but the context in the Gulf shifts the priorities.

Open banking frameworks in Saudi Arabia and the UAE mean customers increasingly expect to see accounts from other institutions inside your app and to grant and revoke consent for data sharing. Consent screens are now part of onboarding UX, and they have to be legible in Arabic and English.

Saudi Arabia’s PDPL and its UAE counterpart set explicit expectations for what you tell people when you collect data. Treating the privacy notice as legal boilerplate misses an opportunity: a short, plain explanation of what is collected and why is itself a trust signal.

Vision 2030 has pushed Saudi Arabia towards a cashless, digitally served economy, so the people onboarding to your app include first-time digital banking customers, not only early adopters switching banks. The flow has to work for someone who has never photographed a document with a phone.

Finally, digital-only banks and fintech wallets have reset expectations for how quickly an account can be opened, and a traditional bank’s app is judged against that standard whether it likes it or not. Our fintech practice spends much of its time on exactly this gap.

Arabic, English and the bilingual banking app

Most banking apps in the GCC ship in Arabic and English, and many Lebanese apps add French. Bilingual banking app design is not translation. It is a second interaction model.

Right-to-left layouts mirror navigation, progress indicators and back gestures, but not everything flips. Numerals, card numbers, IBANs and phone numbers stay left-to-right inside a right-to-left line, and getting that wrong on a transfer screen is a trust failure, not a cosmetic one. Arabic labels usually run longer than English ones, so buttons, tabs and error messages need testing in both languages on real devices. Date formats, calendars and name fields all carry regional conventions that a default component library will not know about.

Design the KYC and onboarding flows in both languages from the first wireframe, and test them with Arabic-first and English-first users separately. The problems each group finds are rarely the same.

Research before screens

Teams that struggle with onboarding drop-off almost always share one trait: they designed the flow from the regulation outwards rather than from the customer inwards. Our UX research work on banking products typically begins with moderated sessions watching real people attempt to open an account on a competitor’s app, followed by interviews with the bank’s branch and call-centre staff, who see exactly where customers get stuck.

That research produces a map of hesitation points, which becomes the design brief. It is cheaper than a redesign and more reliable than copying whichever neobank is fashionable this year.

Frequently asked questions

What causes the most drop-off in mobile banking app onboarding?

Document capture and verification waiting time are the largest culprits in our experience, followed by permission requests made too early. Most of these are design problems rather than regulatory ones, and they can be fixed without changing what is collected.

How should KYC onboarding UX differ for Saudi Arabia and the UAE?

Both markets offer national ID sign-in that can pre-fill and verify much of the KYC data, and both have open banking consent requirements that belong inside the onboarding flow. The flow should also be designed and tested in Arabic and English as equals rather than treating one as a translation of the other.

Does better banking app UX conflict with compliance?

No. Compliance defines what must be collected and verified; UX defines how that is asked for, explained and confirmed. The strongest banking apps in the region meet every requirement from SAMA or the CBUAE while feeling faster and calmer than their competitors.

If you are planning or rebuilding a banking app for Saudi Arabia, the UAE, Lebanon or the wider GCC, talk to us about where your onboarding is losing people and how to fix it.