
Mobile apps · 14 min read
أهلاًAhlan, Arabic for welcome
I'm Maniruzzaman Jubayer, a senior designer whose team handles mobile app design and development in Riyadh for founders whose users read Arabic first, sign in with Nafath and pay with mada or Apple Pay. I design and build your iOS and Android app, from the first flow to the store listing, on a clock three hours ahead of yours, and my weekend also falls on Friday and Saturday.
Free 30 min intro call in Riyadh time · iOS and Android · One fixed quote
7 hours of your day shared
Trusted by teams at
In StatCounter's September 2026 figures, iPhones carried 51.6% of Saudi mobile web traffic and Android 48.4%. A Riyadh app has to feel at home on both, and these are the problems that show first.
Apps drawn in English and translated late get clipped Arabic tab labels, wrapping buttons and digits in the wrong style. Apple suggests Arabic about 2 points larger beside capital Latin letters. I size Arabic first, test it at the largest text settings and pick Eastern or Western digits per screen.
Your users move between your app and national ones like Tawakkalna, which serves more than 36 million citizens, residents and visitors. A web view whose back arrow points left feels foreign beside them. I design native navigation for iOS and Android, with back pointing right and gestures and layouts mirrored.
The 2022 census counted 13.4 million non-Saudis, 41.6% of everyone in the Kingdom. One app often serves a Saudi reading Arabic and a resident reading English, signing in with a national ID or an Iqama. I design both paths together, with the language, ID fields and help each person needs.
The PDPL's implementing regulation asks for separate consent for each purpose, explicit consent for sensitive and credit data, and withdrawal as easy as giving it. On a phone that sits beside the system permission prompts. I design both as one calm sequence, asked only when a feature needs it.
Three phone-first projects of mine: a wallet app for moving and tracking money, a mental wellbeing platform with web and app screens, and app screens for a farming company. Payments, health and food security each have their own Vision 2030 programme in the Kingdom.

Product design · Fintech
A Shariah-compliant web app where investors in Saudi Arabia own property shares, collect rent, trade units and track Zakat.
Read the case study →
Product design · Fintech
A fintech app for payments, expense tracking and budgets, with its research, user flow and UI design.
Read the case study →
Website design · Health
Website and app screens for a digital health platform that makes recovery feel human.
Read the case study →Does your app still point left in Arabic? Let's mirror it properly.
Tafaddal, book a callSix pieces of work, each listed in the scope up front, so Nafath, payments, consent and Hijri dates arrive as designed states instead of last-sprint patches.
Each screen laid out right to left before its English twin exists, following Apple's guidelines and Material Design, with Arabic type sized on real phones and digits chosen for each context.
The ID or Iqama field, the number to match, the jump to the Nafath app and back, plus waiting, expired and declined states and a fallback for anyone without Nafath.
Payment sheets and card forms for mada and both wallets, with 3D Secure, failure and refund states, and the full price shown before anyone confirms, as Apple asks of Apple Pay apps.
Date fields built on the Umm al-Qura calendar that iOS and Android both support, with Hijri and Gregorian labelled side by side wherever a booking, payment or document needs both.
Consent for each purpose, explicit consent for sensitive data, permission prompts asked in context, and a privacy screen where people withdraw consent as easily as they gave it.
One codebase for iPhone and Android, written by me in React Native or Flutter depending on the product, the admin panel in React and Next.js, and Arabic and English store screenshots. Mobile engineers of your own receive the tested design system and specs instead.
Four steps on your Sunday to Thursday week, built on my mobile app design process and tuned for Arabic, Nafath and two app stores.
A video call on Google Meet, any Sunday to Thursday, at an hour that suits Riyadh. Show me the app or prototype, the users it is for and the release you are aiming at, and you leave knowing honestly whether I am the right fit.
I list every flow on iOS and Android in Arabic and English, each Nafath, payment and consent state, and the target store date, then quote the whole app as a single fixed sum. No retainer, no hourly meter.
Weekly Figma sprints with Arabic screens first, and prototypes your team and early users try on their own iPhones and Android phones. You get a written note in Slack every two days, and your native speakers approve the words.
I build the app in React Native or Flutter, with a fresh test build on your phones each week and the admin panel growing beside it. Arabic and English listings and reviewer notes go to Apple and Google on a date we set around Ramadan and Eid.
Remote, but inside your week, your users' language and your market's rules.
We can talk now
Your day My day Shared
I draw your screens and build your app, and I share one Slack channel and the same calls with you. Nobody relays messages, and I lead every review myself.
We both rest on Friday and Saturday, so your Sunday to Thursday is our working week. I am three hours ahead, 7 hours of your day is shared, and every invite goes out in Riyadh time.
Figma from day one, decisions written down, a short Slack report every 48 hours and one review call each week. Prototype links, and later each test build, open on your own phone, so your team can try them between reviews.
Nafath, mada, Apple Pay and Google Pay, STC Bank and other wallets, the PDPL and SDAIA, TGA driver checks, the CST's platform rules and Hijri dates are on my checklist from the first call.
Facts come from the Vision 2030 Annual Report 2025, SAMA and each sector's regulator. Each picture is a screen from my own work in that field, never from a Saudi client.

SAMA's sandbox lets fintechs test with real customers for six to 12 months, and they must tell those customers the test's duration, limits and risks. Wallet apps need that disclosure, Nafath onboarding and transfers people can trust.
My fintech work →
Vision 2030's 2025 report counts 241 hospitals linked to the SEHA Virtual Hospital. Health and wellbeing apps need Arabic-first booking, explicit consent for health data and notifications that never show a diagnosis on the lock screen.
My healthcare work →
Apple Pay has carried mada cards since 2019, and SAMA made Google Pay available in September 2025. Shopping apps need both wallets, Arabic product pages and order tracking that holds from checkout to the doorstep.

Transport General Authority rules make delivery apps verify each driver's face through a system linked to the authority. Driver and fleet apps need that check to be quick, plus Arabic maps, large controls and dispatch views on tablets.
My logistics work →
Saudi family homeownership reached 66.24% in 2025, and the Sakani app, launched in 2017, lets families check eligibility and reserve homes. Property apps need Arabic listings, floor plans and financing steps that work on a phone.
My real estate work →
The Reef Saudi Arabia programme gave small farmers more than $770 million of direct support between 2020 and 2025. Farm apps need Arabic-first screens, large controls, offline saving and water and resource tracking that reads in bright sun.
Most Riyadh app teams who reach me fall into one of these four groups. A 30 minute call settles whether we fit.
That sounds like you?
If you are testing under SAMA's sandbox or preparing for a licence, I design and build onboarding, wallet and disclosure screens to the standard regulated apps need, with a written record your compliance team can follow.
Talk it through on a free callThat sounds like you?
Citizen and staff apps that sit beside national platforms such as Tawakkalna need bilingual flows, Nafath sign-in and careful data handling. I fit into your approval chain and write down every decision, so sign-off never stalls on a missing reason.
Talk it through on a free callThat sounds like you?
Vision 2030's 2025 report counts 123 million tourists and more than 17 million Riyadh Season visitors. Ticketing, venue and travel apps open on dates that cannot move, so I plan design and store review backwards from opening day.
Talk it through on a free callThat sounds like you?
If your app began in Dubai, Cairo or Europe, Saudi users will expect Nafath, mada and Arabic that reads natively. I adapt the flows for them and keep one design system across every market you serve.
Talk it through on a free callNone of the three is wrong for every team. This is how they stack up for an Arabic-first app on iOS and Android.
| What you get | With me | In-house hire | Freelancer |
|---|---|---|---|
| Starts without a recruitment round or a visa | Yes | No | Yes |
| Arabic-first iOS and Android screens, mirrored natively | Yes | Sometimes | Sometimes |
| Nafath, mada and Apple Pay states written into the scope | Yes | Sometimes | Sometimes |
| PDPL consent and permission prompts designed together | Yes | Sometimes | No |
| Store review readiness for a regulated fintech or health app | Yes | Sometimes | Sometimes |
| iOS and Android app built by the person who designed it | Yes | No | Sometimes |
| At a desk in your Riyadh office each weekday | No | Yes | Sometimes |
Apps rarely ship alone. Most Saudi teams also need the website, the product dashboard or the web build.
Guides on Nafath login screens, design budgets in riyals and Arabic interfaces.

Mobile apps · 14 min read

Mobile apps · 15 min read
Straight answers for teams building an app for Saudi users, before we talk.
أهلاً
Pick a time that suits your day in Riyadh. Thirty minutes on your product and your deadline, and you leave knowing whether I am the right fit.
City photos from Unsplash.