All services

Mobile & product

Mobile apps for UAE businesses

We ship iOS and Android from a single codebase, with the backend built alongside it. You keep both developer accounts and both signing keys, from the first build onwards.

Nadra Clinics, a concept build: the front-desk booking console showing a week of appointments for the Dubai Marina branch, one slot held with a countdown, and a toast confirming a WhatsApp confirmation delivered in 3.2 seconds.

Concept build — Nadra Clinics, engineered in-house

<48h

Brief to fixed proposal

Yours

Both store accounts and keys

2

App stores, one codebase

30 days

Warranty after release

What we build

Eight pieces of the job, quoted separately

Eight pieces of an app, and we build all of them.

How we build it

Three decisions we make early

Three habits that keep a first release from becoming a programme.

Release one is a scope

We cut the app down to the smallest thing worth installing, then quote that. Everything else goes on a list you can buy later, in order, once real users have told you which parts they actually open. An app scoped as a whole product ships late; an app scoped as release one ships and then grows.

The backend ships with it

Most app projects fail on the service behind the screen, not the screen. So the API, the data model and the admin console are built in the same sprints as the app, by the same people, against the same schedule. There is no second vendor to wait for and no integration phase invented at the end.

Store accounts opened first

Apple and Google both have review queues, identity checks and, for new Play accounts, a mandatory closed test before production. Opening the accounts at kickoff turns those into background tasks running quietly beside the build; leaving them until submission turns them into the reason you miss a launch date you already announced.

What you get

What you hold after the first release goes out.

  • One codebase shipping to both app stores
  • Both developer accounts registered to your company
  • Signing keys stored in your own password manager
  • Push notifications and deep links, wired and tested
  • An admin panel for your operations team
  • Crash reporting and release-health dashboards
  • Store listings, screenshots and privacy forms
  • A staged rollout plan for the first release
  • The full repository, history included, handed over
  • Thirty days of warranty after release

Stack

What this work actually runs on

What we reach for when the product lives on a phone.

One codebase, both stores, real release pipelines.

9 tools

  • React Native
  • Expo
  • Flutter
  • Dart
  • Swift
  • Kotlin
  • Firebase
  • Fastlane
  • App Store Connect

A drawing of a phone: a frame, a list of rows and a bottom tab bar, with the two app-store targets beside it.

Names, not logos. Everything listed is something we build with or integrate, not a category page we copied.

Where it lands

Six sectors this work is bought in

The sectors that keep asking us for an app.

  • Logistics

    Dispatch boards, driver apps and proof of delivery.

  • Healthcare

    Clinic systems, patient portals and careful data handling.

  • Retail & e-commerce

    AED storefronts, stock sync and delivery integrations.

  • Hospitality

    Booking engines, guest apps and property dashboards.

  • Energy

    Field reporting, asset registers and offline-first tools.

  • Real estate

    Listing portals, broker CRMs and owner dashboards.

All ten sectors we build for

Process

Five stages, and what you hold at each

Five stages, and a build you can install from the second.

  1. 01

    Scope

    Platform choice, a first release scoped and quoted.

    Release-one scope

  2. 02

    Prototype

    Screens on a real device before production code starts.

    Installable prototype

  3. 03

    Build

    Short increments, each installable on your own phone.

    TestFlight build

  4. 04

    Launch

    Store submission, a staged rollout, then full release.

    Store listing

  5. 05

    Run

    Crash triage, OS updates and two release cycles a year.

    Release-health report

How we quote it

We quote release one, not an open-ended programme — screens, backend and both store submissions, itemised.

  • Quoted per release, not as one open-ended programme
  • Both store accounts stay in your company's name
  • Defects found in the first thirty days are fixed free

Quoted as mobile app: ios and android, backend, store submission. We publish no bands — pick the pieces you need and one itemised quotation comes back within 48 hours, free either way.

Get a quote

Questions

Before you send the brief

Native or cross-platform?

Cross-platform unless something forces otherwise. React Native or Flutter gives you one codebase, one team and near-native performance for the vast majority of business apps. We recommend Swift or Kotlin when the product leans hard on the camera, on Bluetooth, on background location, or on a platform API that changes every year. That decision is made in scoping, in writing, with the trade-off spelled out.

How long until it is live?

That is set by how much release one has to do, so we scope it with you and plan backwards from your date rather than quoting a stock figure. Two things sit outside anyone’s control and both go into the schedule explicitly: Apple reviews most submissions quickly but a rejection adds a cycle, and Google requires new personal developer accounts to run a closed test before production. We open both accounts at kickoff so neither becomes the reason a launch slips.

Whose developer accounts are used?

Yours. Both the Apple Developer and Google Play accounts are registered to your company, paid on your card, and the signing keys live in your password manager with a copy in escrow if you want one. We work as invited members with the access we need and nothing more. If we part ways, you remove us and the apps keep updating — no transfer request, no waiting on us.

What does it cost to run each year?

Budget for the two platform fees, backend hosting, push and SMS or WhatsApp usage, and two maintenance cycles a year. Apple and Google both change requirements annually — target SDK levels, privacy manifests, permission wording — and an app left untouched for eighteen months usually needs remediation before it can ship an update at all. A support retainer covers that; so does a fixed yearly block.

Can you take over an existing app?

Often, yes. We start with a paid audit: we build it from a clean checkout, read the crash history, check which dependencies are still maintained, and confirm who actually controls the store accounts and keys. You get a written risk list and an honest recommendation, which is sometimes a rewrite and sometimes a short repair job. We will say which, before you commit to either.

Related

Where this shows up

Two builds where the phone was the important screen.

  • Clinic booking system

    Nadra Clinics

    A four-branch booking system with held slots, WhatsApp confirmations and a front-desk console.

    Lighthouse accessibility
    100
    LCP on the slot picker
    1.1s
  • Property listing platform

    Atlas Properties

    A bilingual property portal: 1,240 listings, faceted search and an agent-facing CMS.

    LCP on a filtered results page
    0.9s
    Lighthouse performance
    100

Bought alongside

What an app usually needs standing behind it.

  • Custom software

    CRM and internal systems shaped around how you already work.

    Explore
  • Web development

    Marketing sites and web apps in Next.js, ready for Arabic.

    Explore
  • AI implementation

    Retrieval and assistants wired into the data you already hold.

    Explore

Scope your first release.

Tell us what the app has to do at launch. We scope release one, quote exactly that, and leave the rest for later.