- Expats Often Know the Goal, Not the Process
- Clear Language Is More Important Than Formal Language
- Forms Should Prevent Predictable Mistakes
- The Whole Journey Matters More Than One Good Screen
- Status Messages Should Explain What Happens Next
- Mobile UX Needs to Reflect Real Situations
- Switching Language Should Not Mean Starting Again
- Payment Screens Need to Remove Doubt
- When Self-Service Fails, Support Should Keep the Context
- What Expats Keep Asking Can Reveal UX Problems
- A Practical Checklist for Expat-Facing Digital Services
- Better UX Means Fewer Unanswered Questions
Moving to Saudi Arabia comes with a long list of practical tasks.
A new resident may need to understand their Iqama, open a bank account, activate a SIM card, manage insurance, check visa information, book appointments, make payments, or submit documents to an employer or government service.
Many of these tasks can now be handled digitally, which saves residents considerable time.
But being online does not automatically make a process easy to understand.
For an expat, even a straightforward form can become confusing when it contains unfamiliar terminology, identification numbers they have never used before, unclear date formats, or instructions written for someone who already understands how the system works.
For expats, better digital UX is therefore not mainly about adding features. It is about making important tasks clearer and reducing unnecessary uncertainty.
Expats Often Know the Goal, Not the Process
Imagine someone who has recently moved to Riyadh.
They need to check something related to their residency, but the digital service asks for a border number.
Is that the same as an Iqama number? Where can it be found? Can a passport number be used instead? What if the Iqama has not been issued yet?
These are not signs that the user lacks digital skills. They simply may not understand the administrative system yet.
Someone who has lived in Saudi Arabia for years might immediately recognise terms such as Iqama, border number, exit/re-entry visa, sponsor information, or residency status. A newcomer may be seeing them for the first time.
Good digital services account for that difference.
If a field requires a border number, for example, a short explanation can show users where to find it. Fursah GCC’s guide on checking a border number in Saudi Arabia is a useful example of the kind of information expats often need when navigating these services.
The interface itself should ideally answer four basic questions:
What am I doing? What information do I need? Where can I find it? What happens next?
When those answers are clear, users are less likely to leave the service just to understand how to continue.
Clear Language Is More Important Than Formal Language
Language creates another challenge, but it is not simply a question of Arabic versus English.
For many expatriates, English is also a second language.
That makes clear instructions particularly valuable.
Consider this error message:
Identification data does not match.
It sounds official, but it does not tell the user enough.
Was the passport number incorrect? Was the date of birth entered in the wrong format? Does the Iqama information not match the government record?
A better error message should help the user recover.
For example:
Check that your passport number and date of birth match the information registered with your residency record.
Now there is a clear action to take.
Official terminology will sometimes be necessary, particularly in government, banking, immigration, insurance, and employment services. The goal is not to remove those terms but to explain them when their meaning affects the user’s next step.
Translation tells people what the interface says. Good UX also helps them understand what they are expected to do.
Forms Should Prevent Predictable Mistakes
Forms are one of the places where expats are most likely to experience digital friction.
A single process might request:
- Iqama number
- passport number
- border number
- nationality
- mobile number
- date of birth
- visa details
- employer information
- uploaded documents
That is a lot of information to enter correctly, particularly for someone still learning which document contains which number.
A well-designed form should provide help before something goes wrong.
If a field requires ten digits, say so. If a date needs a specific format, show an example. If an uploaded document must be a PDF or JPG below a particular file size, explain that before the user attempts the upload.
Small improvements like these can prevent repeated submissions and unnecessary support requests.
The form should also preserve information whenever possible. Completing a long application and losing several fields because of one validation error creates frustration that could easily have been avoided.
Good forms are not memorable because of how attractive they look. They work well because users can complete them without repeatedly stopping to figure out what the system expects.
The Whole Journey Matters More Than One Good Screen
Many expat services involve more than one organisation.
A resident might begin with a government platform, wait for an employer to complete another step, provide information to an insurer, make a payment through a bank, and then return to a different service.
Each platform can work correctly on its own while the overall process still feels confusing.
The problem often appears between the individual steps.
Who needs to act next? Does the resident need another document? Should they wait for a notification? Do they need to open another platform?
Organisations naturally design around their own responsibilities. Users experience the process as one continuous task.
This is where user-centered design becomes valuable. It encourages teams to look beyond individual screens or departments and organise the experience around what the resident is actually trying to accomplish from beginning to end.
Improving that journey does not always require a new feature.
A sentence explaining that an employer must complete the next step can remove significant confusion. A direct link to the next service may save several searches. A short document checklist can help users prepare before beginning another stage.
The quality of a digital journey often depends on these transitions just as much as the screens themselves.
Status Messages Should Explain What Happens Next
After submitting an application or request, users often enter another difficult stage: waiting.
A platform may display:
Pending
or:
Under review
Those labels describe the current status, but users may still wonder whether their request was received correctly, whether a document is missing, whether someone else needs to take action, or whether they should simply wait.
This matters more when the process affects residency, employment, travel, insurance, or money.
A clearer status message might say:
Your request has been received. No action is required from you at this stage. You will be notified when the review is complete.
The system has not promised an exact completion time, but the user understands the situation.
That clarity can also reduce unnecessary repeat logins and support enquiries.
Mobile UX Needs to Reflect Real Situations
Expats do not always use digital services while sitting at a desk with every document prepared.
Someone may need to find an electronic document while standing at an office counter. They might upload a photo from their phone, verify information at a bank, or check a residency detail while travelling.
A service can be technically responsive and still be frustrating on mobile.
Long forms become tiring. Tables may require horizontal scrolling. Upload controls can be difficult to understand. Important instructions may appear far away from the fields they explain.
Session timeouts can create even bigger problems.
A user might leave the browser briefly to locate a document and return to find that the session has expired and part of the form needs to be completed again.
Mobile testing should therefore go beyond checking whether the page fits different screen sizes.
Teams should test whether a person can comfortably complete the full task from a phone under realistic conditions.
Switching Language Should Not Mean Starting Again
Expats may switch between Arabic and English for many reasons.
A colleague might be helping them. An official document may use Arabic terminology. They may want to compare the meaning of a particular label between languages.
The language selector should support that behaviour rather than interrupt it.
Where technically possible, switching languages should preserve:
- entered information
- uploaded documents
- selected options
- the current step
- application context
A person who has already completed half a form should not lose that progress simply because they changed the interface language.
The principle is straightforward: changing the language should not change the user’s progress.
Payment Screens Need to Remove Doubt
Payment is one of the worst places for ambiguity.
A user presses the payment button, waits several seconds, and receives an unclear message.
Now they do not know whether they were charged.
Trying again could create a duplicate payment. Doing nothing could leave an application unfinished.
A good payment experience should make the outcome obvious.
Users should be able to see whether the payment succeeded, how much was charged, what the payment covered, and what happens next. When relevant, receipts and reference numbers should also be easy to save.
If something fails, the interface should clearly explain whether money was taken and whether it is safe to try again.
Financial transactions are not a place where users should be forced to guess.
When Self-Service Fails, Support Should Keep the Context
No digital interface can handle every possible situation.
Records can contain incorrect information. Verification may fail. Accounts may become inaccessible. Payments may encounter technical problems.
Sometimes human support is necessary.
The frustrating part is having to start the explanation from the beginning.
A resident may already have logged in, entered information, attempted the process, received an error, and obtained a reference number. If support then asks them to reconstruct every step, the digital and human experiences feel disconnected.
Where privacy and system capabilities allow it, support teams should receive enough context to understand which service was being used and where the problem occurred.
The goal of good self-service is not to eliminate support entirely. Routine tasks should be easy to complete independently, while unusual situations should be straightforward to escalate.
What Expats Keep Asking Can Reveal UX Problems
One useful source of UX research already exists: the questions people repeatedly ask.
How do I check my Iqama expiry?
Where can I find my border number?
Why is my information not showing?
Which number should I enter?
What does this status mean?
What should I do after this step?
When users repeatedly leave a service to find answers to these questions, that behaviour can reveal gaps in the original experience.
Support tickets, help-centre searches, repeated validation errors, abandoned forms, call-centre questions, and practical expat guides can all show where people need additional clarity.
Instead of only asking how a page should look, service teams should ask:
What information are users repeatedly leaving this service to find elsewhere?
Sometimes the answer reveals a simple improvement that can remove friction for thousands of people.
A Practical Checklist for Expat-Facing Digital Services
Before launching or improving a service used by expats, teams can ask:
- Can a newcomer understand the terminology?
- Is it clear which identification number or document is required?
- Do forms provide examples before users make mistakes?
- Do error messages explain how to fix the problem?
- Can important tasks be completed comfortably on mobile?
- Can users switch languages without losing progress?
- Do status messages explain whether any action is required?
- Is payment confirmation completely clear?
- Does each stage explain what happens next?
- Can support continue from where self-service stopped?
- Is the service understandable for people with different levels of digital confidence?
- Have actual expats tested the important journeys?
Not every problem requires a large redesign.
Sometimes clearer wording is enough. In other cases, better validation, more useful status information, or a clearer connection between two stages can have a significant impact.
The important thing is identifying the moments where users are forced to stop because they no longer know what to do.
Read Also: Friendi Mobile Codes Saudi Arabia 2026: Full USSD Guide
Better UX Means Fewer Unanswered Questions
Saudi Arabia has already made many important services available digitally, giving residents convenient ways to handle tasks related to work, residency, banking, travel, communication, and everyday life.
For expats, the next opportunity is making unfamiliar processes easier to understand from beginning to end.
Residents should not need to understand how a government department, employer, insurer, bank, or telecom provider is structured internally simply to complete an ordinary task.
They need to know what information is required, what to do if something goes wrong, whether an action succeeded, and what happens next.
Often, that does not require more features.
It requires fewer unanswered questions.
For expats, the most useful digital experiences are the ones that make important tasks feel clear, manageable, and predictable.


