Loading
Answer seven questions and get a cost range in AED for building your app in the UAE, built from the starting prices published on our services page. It is an estimate, not a quote. The real number comes out of a scoping conversation, and this page shows you exactly how it arrives at the band so you can argue with the arithmetic.
Seven answers you already have. Change any of them and the band, the breakdown and the exclusions move with it.
Seven answers you already have. The figures update as you change them.
Built from the published starting figure for Mobile App Development, AED 15,000 on the services page. This is an estimate, not a quote. The real number comes out of a scoping conversation.
You picked a fixed scope project. A full mobile app typically runs 10 to 16 weeks. A written brief and scope sign off come before the build, and payments are tied to milestones.
Each answer is a share of the starting figure, not a separate price. Add them up and you get the multiplier applied to AED 15,000.
The scope published under Mobile App Development on the services page.
One React Native codebase for both stores, submitted under your own developer accounts.
Read the full service lineReal costs that belong to your accounts, not to the build.
Paid by you, not by us. An organization must be a legal entity, hold a D-U-N-S number, enroll through someone with authority to sign, use a work email on the organization domain, and have a public website. developer.apple.com
Also paid by you. An organization account needs a D-U-N-S number, and Google states that obtaining one can take up to 30 days, so start it early. support.google.com
Payment gateway fees, messaging, email delivery, maps, model APIs and anything else with its own meter. These are billed to you by the vendor, and we do not publish figures for prices we do not set.
Copy, photography, product data and the Arabic translation of your content. We build the bilingual interface. The words and images in it are yours or a separately scoped piece of work.
Running costs sit with your cloud provider on your own account. Provider prices change, so read them on the provider page rather than from an estimate.
Every project includes a 30 day warranty period covering bug fixes at no additional cost. Continuing work after that is a monthly retainer, quoted on expected scope.
Anyone can print a single number. The number is only useful if you can see what produced it.
Software estimates go wrong in a predictable way: a single figure is agreed early, the brief turns out to contain three unanswered questions, and the difference is argued about for the rest of the project. A range is more honest than a point, because at the moment you are reading this nobody has seen your data model, your existing systems, or the screen your finance team refuses to give up.
So this tool does two things and refuses a third. It starts from a figure that is already published on the services page, and it shows every factor it adds as a share of that figure, with the reason next to it. What it will not do is invent an hourly rate we do not charge, or repeat a market average we cannot source. If a number is not ours and not published, it is not on this page.
The starting figures are exactly that: a starting point for a straightforward project in that category. Every engagement begins with a written brief that both sides sign off before design starts, and the fixed price is written after that brief exists, not before.
Five things account for most of the distance between the bottom and the top of a band. None of them is about writing more code.
Connecting to an ERP, an accounting package or a booking engine is only as predictable as the system on the other side. A documented API with a sandbox is a few days. An older system with no documentation, no test environment and one person who remembers how it works is the single most common reason a build lands at the top of its band rather than the bottom.
A role is not a checkbox. Each one adds screens, permission rules, an audit of what that role must never see, and another pass through testing for every path. Two roles is the ordinary case. Five roles is a different product, which is why role based access control is written into the custom software scope before anything is built.
Right to left is not a translation task. Layout mirrors, icons that indicate direction flip and others must not, Arabic type needs its own line height, mixed direction strings break in ways English never does, and every screen is tested twice. It is planned from the first sprint rather than added at the end, because retrofitting it costs more than building it in.
The gateway integration itself is the small part. Tax on the invoice, refunds, partial refunds, failed and pending states, reconciliation against what the gateway actually settled, and a sandbox to prove all of it works are the rest. A second gateway repeats most of that work.
Whatever your customers see, your staff need somewhere to fix it: their own screens, their own permissions, and the place where support, corrections, refunds and reporting happen. It is usually the piece a first budget forgets and the piece the team uses every day.
The same arithmetic the calculator runs, written out in full so you can check it.
A booking app for iOS and Android, in Arabic and English, with three kinds of user (customer, branch staff, head office), card payments through a GCC gateway, one integration into the scheduling system the business already runs, and an admin panel for the operations team.
Add the shares and you get the multipliers. AED 15,000 times 1.76 is AED 26,400, rounded down to AED 26,000. AED 15,000 times 2.81 is AED 42,150, rounded up to AED 42,500. A full mobile app typically runs 10 to 16 weeks.
Outside that band sit the Apple and Google fees, the gateway charges, the content, and the hosting bill, all of which are listed under the calculator and none of which is paid to us.
For a shipped build at roughly this shape, read the GSG Academy case study: an iOS and Android app, a public website, a staff admin panel and a NestJS back end for German Standard Group.
Read these before you take the number anywhere. They are the difference between an estimate you can use and a number somebody made up.
Costs the estimate deliberately leaves out: the Apple and Google store fees, third party subscriptions, content and translation, hosting and domains, and support past the 30 day warranty. Each one is listed with its source under the calculator.
What buyers ask once they have a number in front of them.
Send a short description of what you want to build. The reply comes within 24 hours, and the first call is a technical scoping conversation rather than a sales pitch.
Start a scoping conversationSend us the shape of the thing you want built. We will come back within 24 hours with a real next step, and a discovery session that costs nothing and commits you to nothing.