The app your crew will actually use is the one that still works when the signal does not.

It depends on scope, and any vendor quoting from a feature list is guessing. What drives the number is the count of user roles, whether the app has to work offline, how many systems it integrates with, whether both platforms launch together, and how much back office sits behind it. We publish indicative ranges on our cost guide and give a fixed price after discovery.

A single-platform app with one or two user roles and a modest back office typically reaches first production use in a few months. Offline sync, multiple roles, hardware integration and a second platform each extend that. We give a dated plan after discovery rather than a number that sounds good in a proposal.

You do. We publish under your Apple Developer and Google Play accounts, not ours, and we hand over signing certificates, repository access and documentation at the end of the project. If you do not have developer accounts yet we help you open them in your company name, which takes a few days and is worth doing before build starts.

Yes, where the work needs it. Records, checklists, photographs and signatures are captured and stored on the device, then reconciled with the server when the connection returns, with rules for what happens when two people changed the same record. We build this whenever the job happens in basements, plant rooms, sites or vehicles.

Both. We recommend cross-platform when it saves money without costing capability, and native when the app depends on hardware, background behaviour or performance that cross-platform handles poorly. The recommendation and the reason for it are written into the proposal, so you are not taking it on trust.

For most operational data, yes, under contractual safeguards including a data transfer agreement we provide and attach to the proposal. If your app touches UAE health data, or banking or telecom data under those regulators' rules, it is built to run in-country. We raise this during scoping rather than after the architecture is fixed.

No, for private-sector work. Nothing in UAE commercial contract law prevents a foreign supplier from contracting directly with a UAE private company, and we invoice you directly under the reverse-charge mechanism. Some government and semi-government procurement does require a UAE-licensed supplier, and we tell you when that applies to your project.

Support under a named agreement, with a response time written into it and a named engineer rather than a shared inbox. That covers operating system updates, store policy changes, defects and small enhancements. Larger changes are quoted separately so you always know which budget a piece of work is coming from.