Mobile App Development in the UAE — UAE PASS Sign-In and Local Payment Rails
The UAE market puts a question to an app developer that many markets never raise: which identity does the user sign in with? Since 2018 residents here have opened government and banking services with the UAE PASS app instead of yet another password, and they now measure every app by that yardstick. Payment comes next, after the Central Bank of the UAE added two domestic rails alongside international cards: the Jaywan card scheme and the Aani instant account-to-account platform. On top of that sits a federal personal data protection law that reaches processing inside and outside the country. Snaabble is an Egyptian team based in Talkha, Dakahlia, with no office in the UAE, working with its Gulf clients remotely from day one.
Get a quoteWhat is different in the UAE?
UAE PASS is the sign-in button people expect
UAE PASS is the country's first national digital identity solution, launched at GITEX 2018 by Digital Dubai, the Telecommunications and Digital Government Regulatory Authority and the Department of Government Enablement. It gives a user one identity across government, semi-government and private-sector entities, and is already used by banking, exchange and telecom services. The official developer documentation lists three capabilities open to private organisations: authentication, digital signature and eSeal, and data and document sharing, the last available to private organisations only. In practice your app can drop long registration forms, provided the account model is planned to accept an external identity.
The two domestic payment rails: Jaywan and Aani
On 27 February 2025 Al Etihad Payments, a subsidiary of the Central Bank of the UAE, announced that the infrastructure for Jaywan, the country's first domestic card scheme, was ready. Its cards are issued as debit, prepaid and credit, accepted across all payment channels including e-commerce, either mono-badged for use in the UAE and the GCC or co-badged with an international network. Before it, Aani launched on 16 October 2023 for instant account-to-account transfers around the clock using a phone number, with request money, split bills and QR payments at merchants.
The federal data law follows the processing wherever it happens
Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data came into force on 2 January 2022, and applies to the processing of personal data in whole or in part through electronic systems, inside or outside the country. It bars processing without the data owner's consent except in specified cases, gives them the right to correct inaccurate data and to restrict or stop its processing, and sets requirements for cross-border transfer. The UAE Data Office acts as the federal regulator. Free zones run their own regimes as well, such as DIFC Data Protection Law No. 5 of 2020.
E-invoicing reaches your app if it sells to companies or government
The Ministry of Finance is building the electronic invoicing system on the OpenPeppol standard with a decentralised model. It applies to every person conducting business in the country for business-to-business and business-to-government transactions, subject to specified exclusions. The Ministry states plainly that PDF, Word, images, scanned copies and emails are not e-invoices. Issuer and recipient each appoint an Accredited Service Provider. The pilot starts on 1 July 2026; businesses with annual revenue above AED 50 million appoint a provider by 30 October 2026 and implement from 1 January 2027, while those below appoint by 31 March 2027 and implement from 1 July 2027.
What we build for you
A services app that signs in with a digital identity
An account model built to accept an external identity alongside email and phone number, linking an existing account to that identity after verification instead of creating a second account for the same person. The design covers the edge cases: a rejected request, an expired one, and a registered name that differs from the name the identity returns, plus a document-signing path inside the app where the service needs one.
A store app with more than one way to pay
A cart and payment screen that take a card, a phone wallet and an instant transfer, not one card field. We keep order logic separate from the payment provider, so adding a method later becomes a configuration and a contained integration rather than a rewrite of the whole purchase flow. Declines, expired sessions and returns from a banking app are designed as real screens, because they happen often.
A booking and logistics tracking app
Booking a service or a shipment with map tracking and a notification on every status change, and a driver interface kept entirely separate from the customer one, with different permissions and different data. Schedules and reports on local time, and a language that switches between Arabic and English without restarting the app and without the layout breaking as direction flips.
An enterprise app for business-to-business selling
Company accounts, multi-level permissions, credit limits and orders that pass through approval before execution. We build invoice data as structured fields from the start, with a tax number, line items, per-line tax and a purchase-order reference, so handing it to an accredited service provider later becomes a single integration rather than a restructuring of the whole database.
A bilingual app priced in dirhams
An interface that flips direction completely between Arabic and English, rather than translated strings sitting on an English layout that never moved. Amounts in dirhams and fils under one rounding rule shared by screen and receipt, dates and numbers formatted the way people in the country read them, and a font carrying the dirham symbol with a fallback for devices that were never updated.
Upgrading or migrating an existing app
Reviewing a running app to add a local payment method, an identity path or an invoicing layer, or to move it onto a single codebase serving Android and iOS from one source. We start with a written report separating what is worth changing from what is worth leaving alone, because a full rewrite costs more than it returns in most cases.
Frequently asked questions
Do you have an office or a licence in the UAE?
No. Snaabble is an Egyptian company based in Talkha, Dakahlia, with no branch and no trade licence in the country. We contract with you directly from Egypt and work fully remotely. That means the licence and licensing entity shown to your users are yours and not ours, and any local regulatory obligation sits with you as the business owner. We sign an NDA before starting, and ownership of the code, designs and documentation transfers to you on delivery.
Can sign-in be connected to UAE PASS?
The official UAE PASS documentation lists authentication and digital signature as available to private organisations, along with data and document sharing which is offered to private organisations specifically. The technical side we handle is the account model, the integration path and the edge cases, such as a user rejecting the request or letting it time out. Registering as a service provider and obtaining the approvals happens in your company's name, and we prepare the technical requirements asked for at that stage.
Which payment methods should the app support in the UAE?
Start with cards and wallets, then look at the two domestic rails. Jaywan cards are accepted across all payment channels including e-commerce according to the Al Etihad Payments announcement, and Aani allows instant transfers by phone number and QR payments at merchants. The practical decision is not to lock the purchase flow inside one provider, so a new method can be added later without a rebuild. We help you compare what the gateways available to you actually support before you sign.
Does the electronic invoicing system cover our app?
The system covers business-to-business and business-to-government transactions, with specified exclusions, not sales to individual consumers. So if your app sells only to individuals it sits outside the current scope, and if it sells to companies or government entities then issuer and recipient each appoint an accredited service provider. The dates are published: a pilot from 1 July 2026, mandatory implementation from 1 January 2027 for revenue above AED 50 million, and from 1 July 2027 for those below.
Your team is in Egypt — does that conflict with UAE data protection law?
No, but it calls for a clear arrangement. Federal Decree-Law No. 45 of 2021 applies to processing inside or outside the country and sets requirements for cross-border transfer. In practice we state in the contract which real data we can reach and which test data we work on, keep the development environment separate from production, and tie our team's access to the project's duration. And if your business sits in a free zone such as DIFC, its own data protection regime may apply alongside the federal one.