Collect three quotes for the same app and they will land twice as far apart as you expected. In most cases that gap is not a negotiating position; it is a sign that the three teams priced three different products and left out three different sets of line items. So the question worth asking is not "what does an app cost?" but "what is actually on the invoice?"
This guide breaks the cost of building a mobile app in Saudi Arabia into the lines a business owner here really pays: the development fee, charges owed to parties who never write a line of your code, a percentage skimmed from every sale, and Saudi regulatory work that lands in the budget before your first user ever opens the app.
Every figure below comes from the page of the organisation that sets it, with the date it was checked. Where no figure is published, that is stated plainly rather than filled with an estimate that looks precise and isn't.
Why a price from another market doesn't transfer to Riyadh
Start with the currency. The Saudi Central Bank states in its Sixtieth Annual Report that it has held the riyal fixed at SAR 3.75 to the US dollar since 1986. The practical effect on your budget is real: dollar-denominated lines such as developer accounts and cloud hosting hold roughly the same riyal value year over year, so you do not need the currency buffer a buyer in some neighbouring markets has to build in. If you are comparing against quotes from Egypt, the line items there follow a different logic, and we broke them down in our guide to mobile app development cost in Egypt.
Next, the payment rails. mada is the domestic card network most of your customers will reach for, and its fees are structured in a way that differs fundamentally from international cards. We will come back to it, because for some businesses it moves the margin more than anything else on this page.
Finally, there is what Saudi regulation itself requires: VAT on the invoice, the Personal Data Protection Law, and e-invoicing if your app issues tax invoices. These are budget lines with engineering hours attached, not legal footnotes to be handled after launch.
Where the development fee comes from
A development fee is hours multiplied by an hourly rate. Both numbers explain why two quotes for one idea diverge: one team scoped 600 hours and the other 1,400, because they never agreed on what the app includes.
Hours are driven by scope, and the biggest multiplier is the number of apps and roles, not the number of screens. An app where a customer browses and orders is far simpler than a system with a customer app, a driver app and an admin dashboard, because each role brings its own permissions, tests and failure paths. Technology choice comes next: one codebase serving both iOS and Android costs fewer hours than writing each platform natively, and we compared the options in Flutter vs React Native.
Rather than accepting a single lump sum, ask each company for estimated hours per item. The table below is the worksheet you fill in from the quotes themselves:
| Work item | What to ask | Quote A hours | Quote B hours |
|---|---|---|---|
| Discovery and scoping | Is there an approved requirements document before any code? | ||
| UX and interface design | Do I approve a clickable prototype before development starts? | ||
| Customer app | How many screens, and which error paths are covered? | ||
| Apps for other roles | Driver, merchant, supervisor: which are in the price? | ||
| Backend and database | Who owns the server and the source code after handover? | ||
| Admin dashboard | Which permissions and reports are included? | ||
| Integrations | Payments, maps, OTP messages, accounting or inventory links | ||
| Arabic and RTL support | Who tests Arabic text and alignment, and on which devices? | ||
| Testing and fixes | How many review rounds before launch? | ||
| Store submission | Who handles Apple review and a possible rejection? |
As for the hourly rate, there is no official published benchmark for the Saudi market, and we will not invent one. The practical method is to collect three itemised quotes: the gap in scope shows up in the hours long before it shows up in the price.
Fixed charges your developer has nothing to do with
These are owed to third parties, and they are cleanest when paid from your own company card rather than through your developer. The figures below are those published on official pages as of September 2026, with riyal equivalents at the pegged rate of 3.75.
| Item | Published charge | Approx. in riyals | Note |
|---|---|---|---|
| Apple Developer account | 99 USD per membership year | about SAR 371 per year | Apple notes prices may vary by region and are shown in local currency at enrollment |
| Google Play developer account | a 25 USD registration fee, paid once | about SAR 94 | Does not recur, unlike the Apple account |
| Cloud hosting | Usage-based | Grows with adoption | See the data residency section before choosing a provider |
The difference between those two accounts matters when you build the budget: Google's fee is one-off, while Apple's is a recurring annual line that belongs in operating costs, not project costs.
The percentage taken from every transaction
This is where feasibility studies go wrong most often, because the cut taken from each sale accumulates quietly and appears nowhere in a quote.
First answer this: what does your app sell? If it sells physical goods or services consumed outside the app — a meal, a clinic appointment, a delivery — payment runs through an ordinary payment gateway and the stores take no commission on those orders. If it sells digital content or in-app subscriptions, purchases run through the store's billing system and its commission applies.
In that second case, Apple's Small Business Program offers a reduced 15% commission to developers whose proceeds did not exceed 1 million USD in the prior calendar year, equivalent to SAR 3,750,000. On Google Play, Saudi Arabia falls among the remaining markets where service fees are 15% on a developer's first million dollars of annual revenue and 30% above that, with 15% on subscription auto-renewals regardless of revenue. The revised structure Google announced from 30 June 2026 applies to transactions in the EEA, the UK and the United States, not to the Saudi market.
Payment fees themselves carry a Saudi quirk worth calculating separately. Tap Payments publishes online mada fees of 1% capped at SAR 200 per transaction since 1 September 2023, including Apple Pay made with a mada card. The cap is the important part. On a SAR 300 order you pay about SAR 3. At SAR 20,000 the fee reaches its ceiling, and above that it stays at SAR 200 while its effective percentage falls — 0.4% on a SAR 50,000 order. If your app sells high-value items such as furniture, annual contracts or contracting equipment, steering customers toward mada instead of credit cards changes your margin noticeably.
Snaabble provides a tailored technical assessment to define the right stack & exact budget.
One thing deserves to be said bluntly: most Saudi payment gateways do not publish their rates. Moyasar's FAQ states that its sales team sets pricing according to business volume and requirements. Any comparison you find on an aggregator site is usually unsourced, and some of it contradicts itself. Get written quotes from at least two gateways and compare three things specifically: the mada rate and its cap, the international card rate, and any setup or monthly subscription charges.
Saudi line items that land on the invoice
Value added tax. The standard rate in the Kingdom is 15%, per the Zakat, Tax and Customs Authority. A SAR 150,000 agreement therefore reaches SAR 172,500 on a compliant invoice from a registered Saudi supplier. Ask whether a price is quoted inclusive or exclusive of VAT before you compare two offers; a great deal of confusion in these comparisons comes from that single line.
The Personal Data Protection Law. If your app collects customer names, mobile numbers or locations, you are a data controller. The Saudi Data and AI Authority (SDAIA) publishes the relevant laws and regulations, including the law and its implementing regulation, the regulation on transferring personal data outside the Kingdom, the rules for appointing a data protection officer, and a risk assessment guideline for transfers abroad. Translated into budget lines: a genuine privacy notice, an in-app path to withdraw consent and delete an account, a record of what you collect and why, and a risk assessment if your data will be processed outside the Kingdom. These are scoped hours, and they cost far less at design time than after launch.
E-invoicing. If your app issues tax invoices, it falls inside the FATOORAH programme. ZATCA explains that Phase One has applied since 4 December 2021 and that Phase Two began on 1 January 2023 in waves, requiring the electronic solution to integrate with the Authority's systems. Integration is engineering work with its own specifications, cryptographic signing and acceptance testing, so ask directly whether it sits inside the scope or outside it.
Data residency and cloud choice. This is an architectural decision made before any code is written and painful to reverse. Google states that its Dammam region (me-central2) is available to KSA-based customers only through CNTXT, its exclusive reseller in the region, meaning contracting, billing and technical support all run through a third party rather than Google directly. AWS lists the Kingdom among the regions it has announced but not yet brought into service. If your contract or your sector requires hosting inside the Kingdom, these constraints shape your options and their cost before they shape your app.
A Saudi company or a regional one?
The question usually gets framed around price alone, while the practical differences sit elsewhere. Here is what actually differs:
| Item | Supplier registered in Saudi Arabia | Supplier outside the Kingdom |
|---|---|---|
| VAT | The standard rate appears on the invoice, with a compliant tax invoice | Treated differently; check with your accountant before contracting |
| E-invoicing | Issues an invoice compliant with FATOORAH | May not, which matters if you deduct input VAT |
| Personal data transfers | Processing inside the Kingdom simplifies compliance | Triggers a transfer risk assessment under SDAIA's regulation |
| Currency | Contract in riyals, no conversion exposure | Contract in dollars, stable thanks to the peg, or in a third and volatile currency |
| Contract and disputes | Local jurisdiction | Needs an explicit governing law clause |
| Day-to-day contact | Same working hours | Depends on overlapping hours, not on distance |
There is no single right answer. The real difference shows up when you ask who carries the compliance burden. If your app handles sensitive data or issues tax invoices, a supplier who works inside these systems daily saves you hours that never appear as a price in any quote.
What recurs every year after launch
Project budget ends at handover; operating budget starts there. The recurring lines that belong in your figures from day one:
- Annual renewal of the Apple Developer account.
- Hosting and backups, which grow with your user count rather than with time.
- Payment gateway fees on every transaction.
- Usage-based external services: maps, OTP messages, push notifications.
- Keeping the app compatible with new iOS and Android releases, which recurs whether or not you add features.
Ask the quote to define the warranty period and its scope, and to separate clearly between fixing a defect under warranty and a new development request. That single line prevents the most common dispute after launch.
Before you sign
Three things make a quote comparable: hours itemised per work item, a price stated explicitly as inclusive or exclusive of VAT, and a list of the accounts that will be registered in your company's name rather than your developer's — the Apple account, the Google Play account, the code repository, the hosting account and the merchant account at your payment gateway. Make each payment conditional on a milestone you receive and test yourself on your own device before approving, and require the contract to hand over the corresponding code, design sources and access credentials alongside it.
If you want to see these line items applied to your own idea, describe it to the Snaabble team from our mobile app development page. Within one working day you will get an initial view of the scope and an estimate of time and cost, at no cost and with no commitment afterwards.
Sources
- Apple Developer Program: Become a member · accessed 19 September 2026
- App Store Small Business Program · 19 September 2026
- Google Play Console: registration fee · 19 September 2026
- Google Play service fees · 19 September 2026
- Tap Payments: mada fees · 19 September 2026
- Moyasar: Frequently Asked Questions · 19 September 2026
- Saudi Central Bank: Sixtieth Annual Report · 19 September 2026
- ZATCA: Value Added Tax · 19 September 2026
- ZATCA: What is E-invoicing (FATOORAH)? · 19 September 2026
- SDAIA: Policies and Regulations · 19 September 2026
- Google Cloud: Dammam region access · 19 September 2026
- AWS Global Infrastructure · 19 September 2026
Frequently asked questions
Can I launch an app in Saudi Arabia on a small budget?
Yes, if you genuinely shrink the scope rather than simply pick the cheapest quote. Start with the single path where a customer orders or pays, one user role, and one codebase serving both iOS and Android, then defer the rest until you see real usage. The cost difference comes from how many hours you buy, not from the hourly rate alone.
Do I have to host the app's data inside the Kingdom?
It depends on your sector and on what your own customer contracts require. If data will be processed outside the Kingdom, SDAIA's regulation on transferring personal data abroad calls for a risk assessment before the transfer. And if you do need hosting inside the Kingdom, note that Google Cloud's Dammam region is sold to KSA customers through its exclusive reseller CNTXT, and that the AWS Saudi region is still among the announced regions that have not entered service. Decide this before you design the architecture, not after.
When does a store commission apply to my app's sales?
It turns on what you are selling. Physical goods and services consumed outside the app, such as a meal, an appointment or a delivery, are collected through an ordinary payment gateway and no store commission touches them. Only digital content and subscriptions activated inside the app run through store billing and give up a share: 15% with Apple for those who qualify for the Small Business Program, and 15% on Google Play for a developer's first million dollars of annual revenue in the Saudi market.
What is the difference between the project budget and the operating budget?
The project budget is paid once to build and hand over the app. The operating budget starts on launch day and does not stop: the annual Apple account renewal, hosting that grows with your user count, payment gateway fees on every transaction, usage-based services such as maps and OTP messages, and keeping the app compatible with new releases of both platforms. Ask the quote to state both figures separately.
