Tap
Targets of at least 44 points, spaced so a thumb never hits two. Each tap answers within a frame, with a ripple or highlight, so users never tap twice and order twice.
05 · Mobile development · UAE, GCC, Syria and MENA
Mobile app development for iOS, Android and the web, designed for the thumb
Nexlla's mobile app development services take a product from first sketch to signed builds in the App Store and Google Play, or to a progressive web app when that serves users better. We pick native, cross-platform or PWA per product and explain why in writing, then design, build, test and launch it in Arabic and English for users across the Gulf, Syria and the wider Middle East.
What an app costs in the UAE and GCC Hiring in Dubai? See our Dubai app service
- Tap: draft a reply
- Edge swipe: back
- Long-press: menu
iOS: iOS users expect a swipe from the left edge to go back, sheets that pull down to dismiss and a home bar at the bottom. Long-press opens context menus.
- Tap: add to cart
- Swipe: next photo
- Long-press: options
Android: Android has a system back gesture from both edges, so in-app swipes must stay clear of the screen sides. Material ripples confirm every tap.
- Tap: get the app
- Scroll: the page
- Long-press: link preview
Web / PWA: In the browser, pull-to-refresh and scrolling belong to the browser itself. A PWA added to the Home Screen gets its own icon, full screen and offline pages.
What the service covers
An app is five products wearing one icon
From the outside, a mobile app looks like a few screens. Underneath, every serious app is a bundle of parts that each need an owner. When a quote feels too good to be true, one of these is usually missing.
- 1
The interface people touch
Screens sized for one-handed use, tap targets a thumb can hit, motion that confirms each action, and an Arabic layout that mirrors properly rather than flipping a few icons.
- 2
The app binary
The installable build for each platform: native Swift or Kotlin, a shared React Native or Flutter codebase, or a web app with a service worker. This is the part most people mean by "the app".
- 3
The backend
Sign-in, the database, APIs, payments, push notifications and file storage. Without this the app is a brochure. We build it with the app, so both sides agree on every field.
- 4
The tools your staff use
An admin panel or dashboard for orders, users, content and support. It often decides whether the app is run well after launch.
- 5
The release machinery
Signing keys, store listings, privacy forms, crash reporting, analytics and a repeatable way to ship version 1.1. Skipped here, it turns every update into a small crisis.
The decision matrix
Native, cross-platform or PWA?
There is no best technology, only the best fit for a budget, a timeline and the features your users need. Here is how the three routes compare on the questions that decide most projects, with the advice we give clients for each row.
| Question | Native Swift · Kotlin | Cross-platform React Native · Flutter | PWA installable web app | Our honest advice |
|---|---|---|---|---|
| Build cost | Highest: two codebases and two skill sets | Medium: one codebase, with small native modules where needed | Lowest: one web codebase, often shared with your website | Cross-platform for most business apps. A PWA if the budget covers only one surface. |
| Time to first release | Slowest, because each platform is built separately | Fast: both apps come from the same code | Fastest, with no store review between you and users | A PWA to test demand in weeks; cross-platform to launch properly in both stores. |
| Device features | Everything: camera pipelines, Bluetooth, background location, widgets | Most features through plugins; unusual hardware needs native code | Limited, and iOS exposes fewer browser features than Android | If the product lives on the hardware, go native or budget for native modules. |
| Store presence | App Store and Google Play | App Store and Google Play | Installed from the browser; not in the stores by default | If customers will search a store for your name, you need a store app. |
| Offline use | Full control of on-device data | Strong, with a local database and a sync layer | Possible with a service worker, but storage is tighter on iOS | For field teams and patchy coverage, choose native or cross-platform with sync. |
| Push notifications | Full support | Full support | Supported on Android; on iPhone only after the user adds it to the Home Screen | If push drives your business, a store app is the safer route. |
| Shipping updates | Every change goes through store review | Store review for app changes; some setups allow small fixes without a new build | Instant: deploy and every user has it | Weekly releases favour a PWA or cross-platform; plan review time into native roadmaps. |
| Long-term upkeep | Two codebases to keep current with each OS release | One codebase, plus framework and OS upgrades each year | Lowest, but tied to what browsers support | Budget for upkeep whichever you pick; an app is never "done". |
The short version. Most business apps in the region (booking, ordering, loyalty, customer accounts) are best built cross-platform: one team, one codebase, both stores. Native earns its extra cost when the app is built around the camera, Bluetooth, background tracking or heavy graphics. A PWA is the smart first step when you need to prove demand or reach users that stores serve poorly.
There is also a fourth route: a web front end inside a thin native shell. We use it for the Android app of our own Customer Portal, because that app mirrors a web product our clients already use.
Designing for hands
Every gesture is a promise the app has to keep
Phones are used on the move, in sunlight and one-handed. We design the touch layer first, because a beautiful screen that fights the thumb gets deleted.
Swipe
Reserved for actions that are easy to undo, such as archiving or moving to the next photo. Swipes stay away from the screen edges, where the system back gesture lives.
Long-press
A shortcut, never the only way. Anything hidden behind a long-press must also be reachable from a visible button, or most users will never find it.
Mirrored for Arabic
In right-to-left layouts, "next" moves left, and on iOS the back swipe starts from the right edge (Android's system back works from either edge). Carousels, sliders and progress bars all flip, while numbers and media controls keep their direction.
Before you press publish
The launch checklist we run on every app
Store rejections rarely come from code. They come from paperwork nobody owned. Tick off what you already have; whatever is left is what we handle during the build.
0 of 9 ready
Apps we built and run
Proof on real devices
Two of these are Nexlla's own products, which means we live with their store reviews, crash reports and update cycles ourselves. The rest are client work you can read about in full.
Nexlla product · file transfer
Dragy
Drag-and-drop file transfer between all of a person's devices, end-to-end encrypted and with no account needed. One product, many targets: it runs on Android, iPhone, Windows, Mac, Linux and in any browser, so the same transfer has to feel native on a phone and on a desktop.
- Android
- iPhone
- Windows
- Mac
- Linux
- Browser
Dubai, UAE · Web3
Golex
Wallet connection, token swaps and transaction review designed mobile-first, so a trade feels native on the phone and every irreversible step is shown before it is confirmed.
Read the Golex case study
Oman · conservation
Arabian Oryx Hema
A mobile layer for rangers across roughly 50 kilometres of remote terrain, mirroring the command dashboard, with alerts and field reporting built for patchy connectivity and bright sun.
Read the Oryx case study
Muscat, Oman · services
Superlaundry app
A customer app for households to pin their door on a map, book a pickup, follow the order live and earn rewards points, sitting alongside the portal and website we built.
Read the Superlaundry case studyNexlla product · Android
Customer Portal app
The Android companion to our Customer Portal, with push notifications, so clients can follow projects, approvals and invoices from their phone. It is the web-in-a-native-shell route from the matrix above, in use.
Building for this region
What changes between Riyadh, Doha and Damascus
An app that works in one Gulf market can stumble in the next. Card schemes and local wallets differ from country to country, delivery addresses are often a pin on a map rather than a street number, and many users switch between Arabic and English in the same session.
Syria needs extra care. Several store, payment, push and mapping services are restricted for Syrian users or developer accounts, so we confirm how the app will reach people before we design it. Sometimes the right answer is an installable web app with a direct Android download beside it, rather than waiting on a store.
Cost, timing and how you pay
We quote each app per project after a scoping call, in a written plan with milestones. Price follows complexity: user roles, integrations, offline needs and the size of the backend matter more than how many screens there are.
For market ranges and the running costs nobody mentions, such as hosting, store fees and push services, read our guide to app development costs in the UAE and GCC.
You can pay Nexlla by Visa, Mastercard, bank transfer, PayPal and other methods. The payment gateways inside your app are scoped separately for each market.
Questions
Mobile development, answered
What do mobile app development services include?
A complete engagement covers product scoping, interface design for phones, the app itself, the backend and admin tools it talks to, testing on real devices, store submission and the first weeks after launch. You can also hire us for one part, such as a design sprint or a store-readiness review.
Should we build a native app, a cross-platform app or a PWA?
Choose native when the app depends on device hardware or demanding graphics, cross-platform when you need both stores on a sensible budget, and a PWA when speed and reach matter more than store presence. The comparison table on this page goes row by row, and we put our recommendation in writing before any build starts.
How much does mobile app development cost?
Nexlla quotes every app per project once the scope is clear, because the number of user roles, integrations and backend work moves the price far more than screen count. Our app cost guide for the UAE and GCC explains typical market ranges and the running costs after launch.
Can one team ship iOS and Android at the same time?
Yes. With React Native or Flutter, one codebase produces both apps and they go to review in the same week. With fully native builds, Swift and Kotlin run as two parallel tracks that share the design, the API and the test plan.
Will the app work with weak or no signal?
It can, if offline use is designed in from the start. We store the data a user needs on the device, queue their actions, and sync when the connection returns. Intermittent connectivity was a core design constraint for the field app in the Arabian Oryx Hema monitoring system.
How do you handle Arabic, right-to-left layouts and gestures?
Arabic screens are designed alongside the English ones. Navigation, icons with direction, carousels and swipe actions all mirror for right-to-left reading, and we test the mirrored gestures on real devices because a back swipe that feels right in English can feel wrong in Arabic.
Can you publish an app for users in Syria?
Usually, yes, but distribution needs checking first. Some store, payment, push and map services are limited for Syrian users or developer accounts, so we confirm the route, whether a store listing, a direct download or a PWA, before design starts.
Describe the one thing your app must do well
That is enough for a first call. You will leave it with a platform recommendation, the risks we see, and the next step to a written quote.
End of issue · 2026.05
Time to feel the Nexlla Gen.
Got a big idea? Say hi to unlock creativity and innovation for your seamless project — from the first sketch to the production deploy.