Tremoloo 2026: What 186+ Projects Taught Us About GCC Users
Recap
Summary
After 186+ projects across 10 countries since 2016, the most durable lesson about GCC users is this:
They do not behave like the Western personas in design playbooks, and designing as if they do is expensive. Four patterns hold up across nearly every project.
Trust is visual before it is functional: users judge a Saudi app by polish and language quality within seconds, and a half-translated Arabic screen destroys credibility faster than a missing feature.
WhatsApp is the real interface: users expect to share, ask, and get support through it, and products that fight this lose.
Payment trust must be earned at every step, even at 85% electronic payment adoption, because one unclear fee screen can end the relationship.
And family and group decisions shape individual accounts, from shared carts to family subscriptions. Each section below unpacks one pattern with project evidence and what to design differently.
This is our year-in-review piece, but we are skipping the highlight reel. What follows is what actually repeated across the work, including the parts that surprised us.
What did we learn in 2026 specifically?
Five lessons from this year's projects:
Evidence beats seniority in client meetings now. The phrase that changed our year was a client asking "show me the sessions, not the deck." Teams that watch users together stop arguing.
Arabic-first is a revenue decision. Products that launched Arabic-first this year onboarded measurably better than translated ones. We stopped framing this as a localization question.
AI features failed quietly, not loudly. The AI features that struggled did not break; users just never trusted them with real tasks. Permission design turned out to matter more than model quality.
The audit-first engagement won. Clients who audited before redesigning spent less overall and shipped sooner. We now actively talk clients out of bigger scopes when the evidence says so.
Speed is a feature users mention unprompted. In testing sessions, "fast" came up more than any visual quality. Users forgive plain; they do not forgive slow.
How are GCC users different from Western personas?
Beyond the four patterns above, the meta-lesson is that imported personas smuggle in assumptions: individual decision-making, card-first payment habits, English-dominant literacy, and support expectations built around email. None of these hold reliably in the Gulf. Personas are useful only when built from local research. We keep a living library of GCC user patterns from our own session archives, and it contradicts the imported templates more often than it confirms them.
Why does Arabic quality make or break trust?
Because language quality is a proxy for respect. A Saudi user who hits an Arabic screen with broken phrasing learns something about your company: the Arabic-speaking customer was not in the room when this was built. In financial and government products, that inference is fatal. The fix is process, not budget: Arabic-native designers and writers in the team from day one, and Arabic screens reviewed with the same rigor as English ones.
What role does WhatsApp play in product experience?
In this market, WhatsApp is infrastructure. Users screenshot products into family groups to get purchase approval. They expect support there, not in a ticket portal. Products that accept this and design for it (shareable product cards, order updates over WhatsApp, human support in-thread) ride the behavior. Products that resist it get worked around, which is worse.
How do payment habits shape UX in Saudi Arabia?
Payment screens carry more anxiety here than the adoption numbers suggest. Yes, 85% of retail payments are electronic now (Saudi Central Bank, April 2026), but trust is conditional and re-earned at every transaction. The products that convert show fees before the PIN pad, state clearly what happens after the user taps confirm, and write error messages that say "you were not charged" in plain Arabic and English. One ambiguous failure at payment can end a customer relationship permanently.
What should product teams do differently in 2027?
Build from local evidence. Run your next usability round in Arabic. Add WhatsApp to your support and sharing map. Put fee transparency on the design checklist, not the compliance checklist.
The year in numbers
186+ projects delivered since 2016 across 10 countries.
Start 2027 with clarity
If you are building for GCC users next year, start with a Product Clarity Audit: evidence about your product, from your actual users, before you commit the year's budget. It is the cheapest insurance in product development, and after 186 projects we can say that without crossing our fingers.
