Building Protocol for the UAE market has taught me something different from building for a generic global user.
The global build assumes clean infrastructure, English-first UX, and a fairly predictable path through distribution. In the UAE, each assumption has a specific exception. You usually learn the exception at the wrong moment, right when you are trying to ship.
This is not a comprehensive guide to UAE product development. It is a builder's account of the things that surprised me.
Payment infrastructure
The obvious SaaS payment choice is Stripe: clean, well documented, and easy to build around.
Stripe is available in the UAE. The harder question is whether Stripe alone reflects the local payment context well enough. UAE users are sophisticated digital consumers: they use Apple Pay heavily, use local debit cards, and notice when checkout feels imported rather than native to the market.
For a product like Protocol, that matters less than it would for fintech or ecommerce. The principle still holds. The payment method that converts in London is not automatically the one that converts in Dubai.
Stripe plus a local payment gateway backup, such as HyperPay or Checkout.com, is closer to the real answer than Stripe alone when local card coverage and regional familiarity matter. That is not the kind of lesson a documentation page gives you. You find it when someone cannot complete a payment and the support thread begins.
Bilingual UX is not translation
The Arabic localization problem in most apps is not the translation; translation is the easy part. Functional strings can get you most of the way there.
The hard part is the UX architecture decision that comes before translation.
Arabic is right-to-left, and RTL layout is not mirroring the interface and calling it done. Navigation flows differently, hierarchy reads differently, and the relationship between elements changes when the reading direction changes. An interface designed left-to-right first and mirrored later will often feel exactly like that: mirrored.
UAE users move between Arabic and English fluidly depending on context. That makes the standard even higher. They can tell when Arabic was treated as a layer added at the end.
For Protocol, I decided early to treat RTL as an architectural requirement rather than a localization task. That added design work upfront, but it also created a layout system that can work in both directions without feeling like one direction is the original and the other is the compromise.
This decision is much harder after the product is built. If you are building for the UAE from scratch, Arabic layout belongs in the product architecture, not the release checklist.
What the App Store does not tell you
The UAE App Store has region-specific expectations and review behavior. Certain content categories get more scrutiny. Health and fitness apps need to avoid clinical claims, and that is especially relevant for a product like Protocol.
The answer is straightforward: make no medical claims, recommend professional advice when a topic enters medical territory, and keep the product clearly inside fitness and wellbeing rather than health management.
The part I was less prepared for was timing. UAE review cycles can take longer than the quick 24- to 48-hour path people often expect, and for initial submissions and major updates, planning for up to a week is more realistic.
That matters when you are trying to ship on a cadence. A review delay is not just an app-store detail. It becomes a release-planning constraint.
The real lesson
None of this means the UAE is difficult.
The UAE is one of the better markets in the world for consumer digital products: high smartphone penetration, high digital payment adoption, strong consumer expectations, and an affluent, tech-forward audience. The country reached 79% cashless transactions in 2024, ahead of many markets people casually describe as more digitally mature.
The friction appears when builders treat the UAE as a Western market with an Arabic option. It is not; it has its own infrastructure, expectations, distribution behavior, and product fluency.
Treat it as a first-class market from the start. The rest is engineering.
Protocol is live at useprotocol.app. Built by Moe Hachem - mghachem.com.