Loading
An app is the easiest thing to start and the hardest thing to finish, because the work people forget is at the end: certificates, store listings, review responses, push notifications that reach the right device, and an update path that does not break the version already installed. Novamind builds in React Native so iOS and Android share one codebase, and handles the submission work as part of the engagement rather than as an afterthought.
Businesses whose customers or field staff need something on a phone that a website cannot do: offline work, push notifications, the camera, or a place on the home screen.
The honest first question is whether you need an app at all. If the job is reading and filling in forms on a good connection, a responsive website or a progressive web app will cost less, ship sooner and never need store approval. We will say so.
An app earns its cost when it needs to work without a connection and sync later, when push notifications are part of the product rather than marketing, when the camera or biometrics are central, or when being on the home screen is itself the point, which is usually true for staff tools used many times a day.
Field and warehouse use is the clearest case in the Gulf: a driver with patchy coverage, a technician logging work on site, a salesperson taking an order in a shop. Those are offline-first problems, and offline-first is an architecture rather than a feature you add later.
One codebase, both stores, and the parts of app delivery that usually get left out of a quote.
React Native with TypeScript and a shared business logic layer, so a rule lives once rather than twice. Platform conventions are respected where they matter: navigation, system fonts, safe areas and the share sheet behave the way each platform expects rather than the way the other one does.
Offline-first data, a local store that is the source of truth while the connection is gone, and sync that resolves conflicts on a rule agreed with you rather than by last-write-wins. This is the part that decides whether a field app survives real use, so it is designed before anything is drawn.
Push wired to the right device and the right user across reinstalls, biometric authentication where a password is the wrong gate, and deep links so a notification or a web page opens the exact screen rather than the home screen. Deep linking is also what lets your website and your app reinforce each other.
Certificate and provisioning management, store listings, screenshots at the sizes each store demands, privacy declarations, and responses to review feedback. We handle the submission and the follow-up. What we cannot do is guarantee an approval, because that is Apple’s and Google’s decision.
Published starting price is AED 15,000. These are the four things that take a quote above it, in roughly the order they matter.
Integrations with systems you already run. An app that reads and writes to an existing ERP or accounting package carries the cost of that integration, and the cost depends on what the system exposes rather than on the app.
How many kinds of user. Each distinct role is its own set of screens, its own permissions and its own test path, so three roles is considerably more than three times one screen.
Offline behaviour. An app that must work with no connection and reconcile afterwards is a different architecture from one that shows an error, and it is worth paying for only when the field reality demands it.
Whether the backend exists. If there is an API to build against, the app is the whole job. If not, the backend is part of the project and should be quoted as such.
One codebase is the right default for business apps. It is not the right answer for everything, and we would rather tell you that now.
For the apps businesses actually commission, which are forms, lists, media, notifications and a camera, React Native produces something that feels native on both platforms from one codebase. That halves the build and, more importantly, halves every change you make for the next three years.
It is the wrong answer when the app is the product and the product is performance: heavy real-time graphics, games, sustained video processing on device, or anything leaning on a platform API the moment it ships. In those cases native Swift or Kotlin is correct, and that is not what this service offers.
We will tell you which of those two you have in discovery. Recommending the thing we build regardless of fit is how a client ends up with the wrong app and a reason never to come back.
The limits are real, so they are written down.
A guarantee that Apple or Google will approve the app. We prepare the submission properly and respond to review feedback; the decision is theirs.
Any promise about how long review takes. That timeline moves and is not ours to quote.
Native Swift or Kotlin builds, and Flutter. This service is React Native. If your app genuinely needs native, we will say so rather than take the work.
Games, and apps built around sustained on-device video or 3D processing.
App store optimisation or paid install campaigns as part of the build price.
On-site work. Everything runs remotely, including the build you can install on your own device from the first week.
The GSG Academy app is published as a case study and is in both stores, which is the most useful evidence we can give you.
GSG Academy is an iOS and Android app carrying live lectures, an on-demand course library, certificates and a community feed, with an indexable web platform at gsgacademy.co where every course and event has its own page that deep-links into the app, and an admin console the academy team runs enrolment, payments, email campaigns and push notifications from.
The content is KHDA-approved and co-delivered with Improve International across GSG branches in the UAE, Saudi Arabia, Qatar and Egypt, so the app is in real use rather than in a portfolio.
If you want to judge the quality of our mobile work, install it.
The questions we hear before a mobile app development project starts.