What shapes design work for Bahrain
Design for Bahrain is often design under regulation. The craft lies in meeting the rule while keeping the journey short.
| Topic | What it means for your product | Decide early |
|---|---|---|
| Regulated onboarding | Opening an account, buying a policy or registering as a patient involves identity checks, declarations and consent. Each added step loses some applicants | The steps compliance requires, separated from those added by habit |
| Disclosure that can be read | Fees, terms and risks have to be shown. On a phone, a wall of text is accepted without reading, which serves nobody | What must be disclosed where, and the plain-language version of each |
| Familiar payment and identity patterns | Users know how the national wallet and the national identity app behave. A product that connects to either should match what users expect at that moment | Which external steps appear in the journey, and the provider's interface rules |
| Arabic and English | Both languages are used daily. Arabic needs its own type treatment, and screens with figures need care, since numerals and currency sit differently in each direction | Typefaces, numeral style and who reviews Arabic screens |
| Three-decimal amounts | Dinar amounts carry three decimals. Inputs, summaries and receipts must show them consistently, and a missing digit looks like an error to a local user | A single format for amounts, applied in every component |
| Consent under the data law | The data protection law makes clear notice and consent part of the interface | Each data request, its wording and its refusal path |
| Products that travel | A product designed in Bahrain is often launched elsewhere in the Gulf, where terms, currencies and identity methods differ | Which parts of the design must be replaceable by country |
Design work we do for Bahraini products
Each engagement below ends with something a developer or a compliance reviewer can use directly.
Onboarding redesign
For banks, insurers, payment firms and clinics losing applicants.
- Current journey mapped with drop-off at each step
- Requirements confirmed with compliance
- Steps reordered, merged or deferred
- New journey prototyped in both languages
- Tested with applicants
- Specification handed to developers
Disclosure and consent screens
For products with terms, fees or data sharing to explain.
- Every disclosure and consent listed
- Plain wording drafted with your legal team
- Layered layouts designed, summary first
- Tested for comprehension
- Final text and layout approved by compliance
Product design for a new service
For founders and product teams, including those heading for the sandbox.
- Users and their problem researched
- Core journey defined
- Interface designed in components
- Clickable prototype built
- Feedback gathered from target users
- Design system and files handed over
Design system for a group
For organizations with several apps and portals.
- Existing products audited
- Shared tokens and components defined
- Arabic and English variants built
- Rules for amounts, dates and numbers documented
- Library adopted by product teams
What we design
Journey research
Analysis of where users leave, backed by interviews and tests with people who match your customers.
Onboarding and identity journeys
Sign-up flows that meet the checks required of you in the fewest steps, with progress saved between sessions.
Payment and money screens
Amount entry, confirmation and receipts with correct formats and unmistakable states.
Consent and disclosure
Layered notices and choices that a customer can understand on a phone screen.
Bilingual interface design
Arabic and English screens designed together, described further in our Arabic RTL product design checklist.
Design systems and handover
Component libraries, specifications and documentation that developers and reviewers can rely on.
What we need from you
- The product and the journey that concerns you most
- Figures on where users abandon it, if you have them
- Compliance requirements for onboarding and disclosure
- Brand guidelines and any existing design files
- Access to users or applicants for testing
Ownership and licensing terms are defined in the project agreement.
A readiness checklist for a design project in Bahrain
Before design starts
0 of 8 checkedWhat to do next
Tell us which journey you want to improve, what the rules require of it and what you know about where users leave. We will reply with the engagement we would suggest and the first things we would test. Start a conversation or book a 30-minute call.
Our guide on what a UX audit should deliver describes the output to expect if you start with a review.
Common questions
Can onboarding be shortened without breaking compliance rules?
Often, yes. Journeys grow by accumulation: a field added after an incident, a document requested twice, a declaration that could be combined with another. We map each step to the requirement behind it with your compliance team. Steps with no requirement are removed, and those that remain are ordered so the applicant invests little before seeing value.
How should fees and terms be shown on a phone?
In layers. A short summary in plain words states what matters most, with the full text one tap away and the consent control beside the summary. Key figures are shown as figures, not buried in paragraphs. The wording is agreed with legal and compliance, then tested with users to see whether they can repeat back what they accepted.
Do Arabic screens use Arabic or Western numerals?
Either can be right, and it should be one decision applied everywhere. Many Gulf financial products use Western numerals in both languages for clarity, while some public-facing content uses Arabic-Indic numerals. We set the rule with you, then make sure inputs, receipts, charts and notifications all follow it, including the three decimals of the dinar.
We are building a fintech product. When should design begin?
Before the application or sandbox plan is final, since the journey you design is part of what you will demonstrate. Early prototypes also expose requirements, such as which identity checks happen when. Starting design after development has begun usually means rebuilding the onboarding, which is the most expensive part to change.
Where to go from here
Related serviceUI/UX DesignInterface design that engineers can actually build