Mobile App Development in Oman: Arabic Design, Payments, Data Law, Store Accounts and Cost
By Dr. Hani Elimam Manager & CEO, SmartTech Studio
An app is a bigger commitment than a website. It lives on the customer’s phone, it has to pass Apple’s and Google’s reviews, it handles payments and personal data, and every update goes through the stores again. In Oman it also has to work properly in Arabic, take the cards Omani customers actually carry, and respect a data protection law that is now fully in force.
This guide covers what is specific to building a mobile app for a business in Oman: language and design, the technology choice, payments, the Personal Data Protection Law, hosting, login and notifications, the store accounts, the tax and e-invoicing rules that affect apps that sell, and the timeline and cost. General pricing logic is covered in our article on what a mobile app costs, and the common reasons apps are abandoned after launch are in why mobile apps fail; we do not repeat them here.
SmartTech Studio builds from Abu Dhabi and works with clients across Oman remotely; we have no office in the Sultanate. Our Oman page explains what we build there and on what terms. The legal and store points below were checked against published sources in November 2026. They are a planning map, not legal advice, so confirm the details with the relevant authority or your adviser before launch.
Design in Arabic first, not as a translation
Most Omani users will choose Arabic if the app offers it properly, and many will judge the whole business by how the Arabic screens look. An app designed in English and “flipped” at the end usually shows it: icons that point the wrong way, numbers and phone fields that break inside right-to-left text, truncated labels because Arabic words run longer or shorter than their English counterparts, and a font that was never meant for Arabic.
The fix is cheap if it is done at the start and expensive if it is done later. Design both languages side by side from the first wireframe; mirror the layout, navigation and gestures for right-to-left; keep phone numbers, prices and order references left-to-right inside Arabic text; and pick a typeface with a real Arabic cut. Our guide to bilingual right-to-left design covers the detail, and almost all of it applies to apps.
Write the Arabic copy natively. Button labels, error messages and push notifications are short, and a literal translation of a short English phrase often reads as odd or even rude in Arabic. Store listings matter too: the Arabic name, description and screenshots on the App Store and Google Play are what an Omani customer sees before deciding to install.
One codebase for iOS and Android
Omani customers use both iPhones and Android phones, so a business app nearly always needs both. Building two separate native apps doubles the work for every feature and every fix. For most business apps (bookings, ordering, loyalty, field service, customer portals), a cross-platform framework gives the same result for far less.
We build with Flutter: one codebase produces the iOS and Android apps, both talking to one backend and one admin dashboard. Flutter handles right-to-left layouts and Arabic text well, which matters more in Oman than in many markets. Native code is still used where a device feature needs it, such as some payment SDKs or Bluetooth hardware, but that is the exception rather than the plan.
The app is only the visible part. Behind it sit the API, the database, the admin panel your team uses to manage orders, content and users, and the integrations with your payment gateway, SMS provider, courier or accounting system. When you compare quotes, check that all of those are included, because a low price for “the app” often leaves out the dashboard.
Payments: OmanNet, gateways, cash on delivery and the store rules
If the app takes card payments, it does so through a payment gateway: the one your bank offers, a local provider such as Thawani, or a regional gateway that supports Oman. Whichever you choose, check that it accepts OmanNet, the national debit-card network, alongside Visa and Mastercard, and that it offers a mobile SDK or a hosted payment page that works cleanly inside an app. Apply early: gateways ask for your commercial registration and business documents, and approval can take weeks.
Cash on delivery still matters for ordering and delivery apps. Design for it rather than bolting it on: confirm cash orders before dispatch, let the driver mark payment collected in the driver app, and reconcile cash against orders in the dashboard every day.
The part many businesses miss is Apple’s and Google’s own rules. Apple’s App Review Guidelines require in-app purchase for digital goods and content used inside the app, such as premium features, subscriptions to app content or digital credits, while physical goods and services consumed outside the app must use other payment methods. Google Play’s payments policy follows the same broad split. Get this wrong and the app is rejected at review, so decide early which category each thing you sell falls into.
| What the app sells | Typical payment route | What to check |
|---|---|---|
| Physical products (retail, food, groceries) | Payment gateway with OmanNet, Visa and Mastercard, plus cash on delivery | Refunds, prices in rials to three decimals, delivery fees by area |
| Services used in the real world (bookings, clinics, repairs) | Payment gateway, deposit or pay on arrival | Cancellation and no-show rules written into the booking flow |
| Digital content or features used inside the app | Apple in-app purchase and Google Play Billing | Store commission in the price, subscription management, restore purchases |
Whatever the route, prices in the app must carry the Omani rial’s three decimal places (2.500 OMR, not 2.5) through the cart, discounts, receipts and reports. The same applies to an online store; our guide to building an e-commerce website in Oman covers payments and delivery in more depth.
Personal data: what Oman’s data protection law means for an app
Oman’s Personal Data Protection Law was issued by Royal Decree 6/2022, and its executive regulations followed in 2024 from the Ministry of Transport, Communications and Information Technology, which supervises it. Royal Decree 68/2026 amended the law in September 2026; our guide to Oman’s data protection law for websites and apps covers the amended text. An app collects exactly the kind of data the law covers: names, phone numbers, locations, order histories, device identifiers and sometimes health or identity information.
In practice, build the app around a few rules. Ask for consent clearly and separately for each purpose (an account, marketing messages, location tracking) rather than one pre-ticked box. Collect only what the feature needs: a delivery app needs an address, it rarely needs a date of birth. Tell users in plain Arabic and English what you collect, why and for how long, and let them withdraw consent and correct their data.
Some categories need more care. The law treats health, genetic and biometric data, and data about children, more strictly. Processing health, genetic or biometric data generally needs a permit from the Ministry; a child’s data is not a permit category, but it needs a guardian’s consent. A clinic booking app or a school app falls into this zone, so plan the permit and the consent flow before development, not after.
Plan for incidents as well. The law requires a controller to notify the Ministry of a data breach and, where it is likely to harm them, the people affected. That means the app and backend need logging, access control and someone responsible for responding, not just a privacy page.
The stores add their own layer. Apple requires apps that let users create an account to let them delete it from inside the app, and Google Play requires a data safety declaration and an account deletion route as well. Both reject apps whose privacy disclosures do not match what the app actually does.
Hosting and where the data lives
The data protection law does not ban every transfer of personal data outside Oman, but it attaches conditions to it, and some clients (government bodies, banks, healthcare providers) have their own rules that require data to stay in the country. Ask the question at the start: where must the database, the backups and the file storage sit?
If the data can sit in the region, a major cloud provider’s Middle East region is usually the simplest option. If it must stay in Oman, the backend can be deployed with a provider inside the Sultanate. Either way, the app itself does not change much; what changes is where the backend runs and how backups and logs are handled. We decide this with the client before the architecture is fixed rather than after launch.
Whoever hosts it, the account should be in your company’s name, with your team holding the admin access. The same rule applies to the domain, the payment gateway, the SMS account and the store accounts. If a supplier owns those, you do not fully own your app.
Login, OTP and notifications
Most Omani users expect to sign in with a mobile number and a one-time code by SMS rather than with an email and password. That needs an SMS provider that delivers reliably to the Omani networks (Omantel, Ooredoo and Vodafone) with a registered sender name, so the message arrives from your brand rather than an unknown number. Budget for it: every OTP is a paid message, and a login screen without rate limits can be abused to send thousands of them.
WhatsApp is the other channel Omani customers live in. Order confirmations, booking reminders and delivery updates through the WhatsApp Business Platform often get read where an email would not. It has its own approval process for message templates, so plan the wording early.
Push notifications are free to send but easy to overuse. Ask for permission at the moment it makes sense (after the first order, not on the first screen) and send them in the language the user chose. A user who turns notifications off rarely turns them back on.
Publishing: put the store accounts in your company’s name
Publish the app under your own developer accounts, not your supplier’s. If the app sits in an agency’s account, moving it later is slow and sometimes impossible without losing reviews and users. Setting up your own accounts takes some lead time, so start them in the first weeks of the project.
Apple’s Developer Program costs USD 99 a year. To enrol as an organisation, so that your company name appears as the seller, Apple requires the business to be a legal entity and to have a D-U-N-S Number, a free business identifier issued by Dun & Bradstreet. Request it early: Apple’s own guidance says obtaining it can take time.
Google Play charges a one-time USD 25 registration fee. Organisation accounts also need a D-U-N-S Number and go through identity verification. Note one trap: a new personal Google Play account must run a closed test with at least 12 testers for 14 days before it can publish to the public, which adds about two weeks to the first launch. An organisation account avoids that requirement, which is another reason to register as a company.
Then allow time for review. Apple and Google both review every new app and most updates; a first submission that needs changes can add days. Prepare the Arabic and English store listings, screenshots, privacy disclosures and a test account for the reviewers before you submit.
If the app sells: VAT and Fawtara e-invoicing
Oman charges VAT at 5%. If your business is registered, receipts and invoices issued from the app must show it correctly, and the backend should give your accountant the tax figures without manual rework.
E-invoicing is coming. Under Decision 189/2026, Oman’s Fawtara system becomes mandatory on 1 April 2027 for businesses with annual supplies above OMR 5 million and on 1 October 2027 for the rest. An app that sells should therefore keep clean customer, product and tax data from day one, and issue invoices from one place in the backend, so that connecting to an e-invoicing provider later is an integration rather than a rebuild.
Our Fawtara deadline checker shows which date applies to you, and the Oman e-invoicing guide covers the preparation step by step.
Timeline and cost
A focused first version (one main user journey, an admin dashboard, payments and Arabic and English) typically takes about two to four months from signed scope to the stores. Apps with several user types, such as a customer app, a driver app and a vendor dashboard, or with heavy integrations, take longer. Store account setup, gateway approval and Apple and Google review all sit on the critical path, which is why we start them in week one.
Our published prices are in UAE dirhams and apply to Omani clients as well. A cross-platform iOS and Android app starts from AED 10,000; a full product with an admin dashboard, API and AI features starts from AED 20,000, both excluding VAT. Every project gets a written quote with a dated plan, and the details are on our app development service page.
Budget beyond the build too: the store fees above, hosting, SMS and WhatsApp messages, the payment gateway’s transaction fees, and maintenance. Apple and Google update their operating systems every year, and an app that is not maintained eventually breaks or falls out of the stores’ requirements.
Choosing a team, local or remote
Many Omani businesses work with app developers outside the Sultanate, and it works well when the arrangement is explicit. What matters is not where the team sits but whether they can show apps they have actually shipped in Arabic, whether you will own the code and every account, and whether the quote names the dashboard, the integrations, the store submission and the support period.
Ask each candidate the same questions: Who owns the source code and the store accounts? What happens after launch, and what does maintenance cost? Which payment gateway have they integrated in Oman or the Gulf? How do they handle the data protection law and hosting location? Who writes the Arabic? A supplier who answers vaguely before the contract will be vaguer after it.
We work with Omani clients remotely from Abu Dhabi, in Arabic or English, with video calls at each milestone and a staging build you can install and test throughout. If you are also planning a website or store, the same team can build both on one backend; see our Oman page for what we offer there.
FAQ
How much does it cost to build a mobile app for a business in Oman?
Our published prices are in UAE dirhams: a cross-platform iOS and Android app starts from AED 10,000 and a full product with an admin dashboard, API and AI features starts from AED 20,000, both excluding VAT. Store fees, hosting, messages, gateway fees and maintenance come on top.
How long does app development take?
A focused first version typically takes about two to four months from signed scope to the stores. Several user types or heavy integrations take longer, and store account setup, gateway approval and app review should be started in the first week.
Can my app accept OmanNet cards?
Yes, through a payment gateway that supports OmanNet, such as your bank’s gateway or a local provider like Thawani. Check OmanNet support and a mobile SDK before you sign with a gateway. Digital content used inside the app must instead go through Apple and Google in-app purchase.
Does Oman’s data protection law apply to my app?
If the app collects personal data such as names, phone numbers, locations or orders, yes. The Personal Data Protection Law (Royal Decree 6/2022) and its 2024 executive regulations require clear consent, limited collection and breach notification. Health and biometric data usually need a Ministry permit, and a child’s data needs the guardian’s consent. Royal Decree 68/2026 amended the law in September 2026.
Whose name should the app be published under?
Your company’s. Open your own Apple and Google Play organisation accounts (both ask for a D-U-N-S Number) and keep admin access in your team. An app published in a supplier’s account is hard to move later without losing reviews and users.
Can you build our app if you are not based in Oman?
Yes. We work with Omani clients remotely from Abu Dhabi, in Arabic or English, with milestone calls and a test build you can install throughout. We have no office in Oman, and we can host the backend inside the Sultanate if your data must stay there.