Best Custom web application development company in Abu Dhabi

Custom web application development is what you commission when the software your organisation runs on does not exist yet. Not a website with a login bolted on, but a working system that holds your data, enforces your process and replaces the spreadsheets, email chains and WhatsApp groups that are currently capping how much work your team can handle.

Tomsher Technologies has built those systems since 2011, with more than fifteen years of delivery experience, a fully in-house team of developers, designers, testers and DevOps engineers, and a rating of 4.9 out of 5 from 201 Google reviews. We work with clients across Abu Dhabi, from ADGM and Masdar City to Mussafah, Khalifa City, Al Ain and the Al Dhafra region. Our office is in Dubai rather than Abu Dhabi, which we state plainly rather than implying a local presence, and the drive is about ninety minutes when a project needs us on site.

This page covers custom builds specifically. If you are still deciding whether you need a web application at all, start with our main web application development services page. If what you need is a corporate website rather than an application, our Abu Dhabi web development page covers that. Come back here for the commercial detail of commissioning a custom system.

One question first, because it decides more about your next five years than the technology does. When the application is finished, who owns the source code, and what exactly is handed over? We read the four agency pages currently ranking for this service in the UAE while preparing this. Not one of them answers it. That silence is how an organisation ends up unable to change its own system without the firm that built it. Our answer: you own the code, you hold the repository, you get the documentation, and you can take all of it elsewhere whenever you choose. The ownership section sets out exactly what that includes, and there is an Abu Dhabi-specific wrinkle to it that nobody else raises.

What counts as a custom web application

The term gets used loosely. A website presents information and collects enquiries. A custom web application does work: it stores records, applies rules, calculates, routes approvals and gives different people different views of the same data depending on who they are.

The practical test is whether the thing has users with accounts, permissions and a state that changes. If people log in, do something that alters the data, and return tomorrow expecting to find it, you are commissioning an application rather than a site, and it needs to be specified, built, tested and maintained accordingly.

Several of these have a page of their own. A consumer storefront is ecommerce development rather than a custom build. A trade portal between businesses is covered in more depth on our B2B and B2C web portal page. Travel businesses should look at travel portal development, and where the requirement is a mobile app rather than a browser-based system, that sits with mobile application development.

This page is one of a pair. The Dubai custom web application page covers the same service for clients there, and both sit beneath our main web application development service. For software beyond browser-based systems, see software development; for websites and corporate platforms, web development.

Who owns the code, and why the answer differs inside ADGM

This is the section the rest of the market leaves out, so it comes first rather than last. In Abu Dhabi there is an extra dimension to it that is worth understanding before you sign anything.

First, the baseline. A proper handover is a defined list of things, not a login to a system somebody else controls:

Now the Abu Dhabi dimension. An intellectual property assignment is only as strong as the law governing the contract that contains it, and Abu Dhabi is one of the few places in the region where that question has two genuinely different answers depending on where your entity sits.

Abu Dhabi Global Market states on its own jurisdiction page that it operates "with direct application of English common law" as an independent jurisdiction, and that the centre extends across Al Maryah and Al Reem Islands, covering 14.38 million square metres, following the expansion of the International Financial District to include both islands on 24 April 2023. For an ADGM-registered entity, that means your development contract, its IP assignment and its dispute resolution can sit within a common law framework with its own courts, which is a materially different position from an onshore Abu Dhabi mainland company contracting under UAE federal law.

We are not going to tell you which is better for you, because that is a question for your counsel rather than your developer. What we will tell you is that it is a question, that it should be settled in the contract rather than discovered in a dispute, and that an agency which has never thought about it is unlikely to have drafted its assignment clause with any care. Ask any firm you shortlist which law governs their development agreement and how IP transfers under it. The quality of the answer is informative.

Two further distinctions, which apply wherever you are registered. An agency may reasonably retain rights in its own pre-existing frameworks and internal tooling while assigning you the custom application built on top; that is normal and it should be stated explicitly rather than left vague. And owning the code is not the same as being able to run it: if the repository is yours but the deployment pipeline, environment variables and server access are undocumented, you own something you cannot use. Ask for both.

Custom build, off-the-shelf product, or low-code

We will talk you out of a custom build where an alternative genuinely fits, which happens more often than an agency page would normally admit.

We also publish ready-made systems covering common requirements, and if one fits your process closely it is a faster and less costly route than commissioning the same thing from scratch. These already exist: clinic management, school management, procurement and tender management, student learning management, employee overtime management and travel booking portals. The honest question in scoping is how far your process differs from the standard one.

Custom web application development across Abu Dhabi

The emirate is geographically vast and commercially segmented, and what a business needs from an application varies more by zone than by sector. This is where we work and what the requirement usually looks like.

Abu Dhabi island and the city centre

Al Markaziyah, Al Danah, Hamdan Street, Electra Street, Al Zahiyah, the Corniche, Al Khalidiyah, Al Bateen, Al Manhal, Al Mushrif, Al Nahyan, Al Wahda, Lulu Island and the Madinat Zayed area. This is head-office territory: government-adjacent entities, professional services, banking back offices, contracting head offices and trading companies. The applications are client portals, document and approval systems, and internal platforms where the constraint is almost always an approval chain with real accountability attached rather than anything technical.

Al Maryah Island and Al Reem Island

Abu Dhabi Global Market covers both, following the 24 April 2023 expansion of the International Financial District, and the character of the work here is distinct. Financial services, funds, family offices, fintech and the professional firms serving them. Requirements skew towards client onboarding workflows, document exchange with controlled access, audit trails that stand up to examination, reporting platforms and integrations with regulated systems. This is also where the governing-law question above matters most, and where clients are most likely to have already thought about it.

Masdar City and Hub71

Masdar City Free Zone and the Hub71 ecosystem bring a different profile again: technology companies, climate and energy ventures, startups and scale-ups. The work is more often a product than an internal system, which changes the engagement: you need something a founder can show investors and change quickly, built so that a future in-house engineering team can take it over without resentment. That makes documentation and code quality commercially important rather than merely good practice.

Mussafah, ICAD and the industrial zones

Mussafah and the Industrial City of Abu Dhabi are where a very large share of the emirate's actual trading, manufacturing, fabrication and workshop businesses sit. The systems here are the least glamorous and the most valuable: stock and inventory tracking, job and work-order management, quote and reorder portals for trade customers, delivery scheduling, and plant maintenance records. The usability constraint is that the people entering the data are on a phone or a shared terminal in a workshop, not at a desk, and an interface designed for a desk gets abandoned.

KEZAD, Khalifa Port and Al Markaz

Khalifa Economic Zones Abu Dhabi, formerly known as KIZAD, together with the Khalifa Port area, covers logistics, warehousing, manufacturing and distribution at scale. Applications here are shipment and consignment tracking, warehouse and yard management, customer-facing track and trace, customs document handling and carrier integrations. Integration is the whole job: these systems are judged on whether they talk correctly to everything else in the chain.

Yas Island, Saadiyat Island and Hudayriyat Island

Hospitality, leisure, culture, events and premium residential. Booking engines, membership and access systems, corporate account portals, event and venue management, and visitor-facing applications where the interface quality is the product. Bilingual delivery is effectively mandatory for anything visitor-facing here.

Khalifa City, Mohammed Bin Zayed City and the mainland suburbs

Khalifa City, Mohammed Bin Zayed City, Shakhbout City, Al Shamkha, Al Falah, Zayed City, Al Raha Beach, Al Raha Gardens, Al Reef, Al Ghadeer, Baniyas, Al Shahama, Al Rahba, Bain Al Jessrain and Al Qurm. Clinics, schools, nurseries, service businesses, property management and home services. The applications are booking systems, parent and patient portals, membership platforms and maintenance request systems, and the common requirement is that a non-technical administrator can run the thing without calling anyone.

Abu Dhabi Airport Free Zone and twofour54

Aviation services, logistics and cargo around the airport zone; media, production and creative businesses in twofour54. Asset and media management, project tracking, rights and usage records, and client review and approval workflows, where version control is usually the real problem being solved.

Al Ain

Al Jimi, Al Muwaiji, Al Towayya, Asharej, Al Jahili, Al Khabisi, Zakher, Al Yahar and the Al Ain Industrial Area. Education, healthcare, agriculture, light industry, retail and government-adjacent services, with a substantial institutional presence. Al Ain is routinely underserved by Dubai-based agencies, and the practical consequence is that organisations there often inherit systems built without anybody ever visiting. We would rather drive out.

Al Dhafra and the Western Region

Madinat Zayed, Ruwais, Ghayathi, Liwa, Mirfa, Sila and Delma Island. Energy, petrochemicals, industrial services, agriculture, fisheries and logistics, often with workforces spread across sites with patchy connectivity. That last point is a genuine engineering requirement rather than a footnote: applications used at remote sites need to tolerate a dropped connection and reconcile afterwards, which is a design decision made at the start or not at all.

Two things worth saying about this list. The zones with the most commercial demand for custom applications in Abu Dhabi are not the prestigious addresses, they are Mussafah, ICAD and the KEZAD corridor, because that is where the process-heavy businesses are. And for most Abu Dhabi clients the question of where our office is turns out to matter far less than whether the specification is written properly, which is the part that actually determines whether the project works.

Our custom web application development services

The full scope, from the conversation before the specification to the maintenance contract after launch.

Discovery and requirements definition

The phase that decides whether the project succeeds, and the one clients are most often persuaded to skip. We work through the process as it actually operates rather than as the org chart says it does, identify the users and what each needs to do, establish the data model, map the integrations, and separate what the system must do at launch from what can wait. The output is a written specification with screens, rules, roles and acceptance criteria, which you approve before anything is built.

Most failed projects we are asked to rescue failed here. The build was competent and it built the wrong thing, because nobody wrote down precisely what was expected.

User interface and experience design

Internal software gets designed badly because nobody is trying to sell it to the people using it. An application your staff find slow or confusing will be worked around, and a worked-around system produces data you cannot trust. We design around the task, phone layouts first where the users are mobile, and we test the flows with real users before development starts.

Architecture and database design

The decisions made in the first fortnight determine what the application can become in year three. We design the data model, the application structure, the API boundaries and the hosting architecture around realistic load and the known direction of the business, and we document why each decision was taken. Our guide to web application architecture sets out how these systems are structured in practice.

Front-end and back-end development

Built in house, in sprints, against the approved specification, with a staging environment you can click through as it progresses. You see working software regularly rather than a status report, which is the only reliable way to catch a misunderstanding early enough to fix at low cost.

Integrations and API development

Almost every custom application has to talk to something else: an accounting system, an ERP, a CRM, a payment gateway, a shipping or carrier platform, a government portal, an SMS or WhatsApp service, a single sign-on directory. We build and document those integrations, including the error handling for when the other system is unavailable, which is the part that gets skipped and then generates the support calls. Our piece on API integration covers how these connections work in more depth.

Quality assurance and testing

Functional testing against the acceptance criteria, cross-browser and device testing, role and permission testing, load testing where volumes warrant it, and security testing. Permission testing deserves naming on its own, because the commonest serious defect we find in inherited applications is a user who can reach data they should not, usually by changing a number in a URL.

Deployment, hosting and DevOps

Environment setup, deployment pipeline, backups, monitoring and alerting, certificate management and a documented rollback path. We will deploy into your own cloud account or host it on cloud hosting, and in Abu Dhabi the question of where the data physically sits deserves its own section, below.

Documentation and handover

Technical and user documentation, repository access, credentials in your name and a walkthrough with whoever will administer the system, as set out in the ownership section above.

Support and maintenance

Custom applications are not finished at launch. Frameworks and libraries underneath them need updating, certificates expire, integrations change at the far end and the business asks for things. An unmaintained application quietly accumulates security exposure and then fails at the worst possible moment. Our maintenance contracts cover updates, patching, backups, monitoring, uptime and a defined response time.

Where your data sits, and why Abu Dhabi is stricter

Hosting location is treated as a technical footnote by most of this market. In Abu Dhabi, for some applications, it is a compliance decision that constrains the architecture, and it has to be settled in the specification rather than at deployment.

The clearest case is health data. Federal Law No. 2 of 2019 on the use of information and communications technology in health fields contains a localisation provision, reported as Article 13 in the analysis published by Latham and Watkins, under which health data related to health services provided in the UAE may not be stored, processed, generated or transferred outside the UAE unless the activity has been approved by a decision of the health authority or the Minister. Al Tamimi's analysis of the same law describes the provision in the same terms and notes that approvals were expected to be limited.

Abu Dhabi then adds a further layer. The Department of Health issues the Abu Dhabi Healthcare Information and Cyber Security Standard, known as ADHICS, which applies to healthcare entities in the emirate. Al Tamimi's analysis notes that this standard restricts cloud use for health information, which narrows the technology options available to an Abu Dhabi healthcare organisation beyond what the federal rule alone does. We should be straightforward about the limits of what we can tell you here: the standard itself is not available to us to read directly, so this page quotes no control references and no version-specific requirements, and anyone building a clinical system in Abu Dhabi should obtain the current standard from the Department of Health and take advice on it. Both of the law firm analyses cited above are secondary and predate the implementing regulations of the federal law.

The practical point stands regardless of the detail. If your application will hold clinical or patient data in Abu Dhabi, the hosting decision comes before the architecture decision, it limits which cloud regions and third-party services you can use, and retrofitting residency into a built application is expensive and sometimes means rebuilding the integrations. Beyond healthcare, the questions worth settling early are which jurisdiction your entity is subject to, whether contractual commitments to your own clients restrict where their data may be processed, which cloud regions your provider offers locally, and whether backups and logs are in scope too, since those travel further than people expect.

Technologies we build on

We choose the stack to fit the application and the people who will maintain it, not to fit what we enjoy writing. A system your in-house IT team can eventually support is worth more than a fashionable one they cannot.

We do not argue stacks on a service page. Our comparison of MERN and Laravel and our review of current frameworks go into it properly.

Security and access control

A custom application holds data a website does not, and it is reached by people you have given accounts to, which changes the risk profile entirely.

What belongs in every build: role-based access control designed from the user list rather than added later, multi-factor authentication for privileged accounts, encryption in transit and at rest, server-side validation of everything regardless of what the interface already checked, protection against the standard injection and cross-site classes of attack, rate limiting on anything enumerable, an audit trail recording who changed what and when, secrets kept out of the repository, and least-privilege database accounts.

Two things deserve special mention because they are where we find real defects in applications built elsewhere. Horizontal access control: can user A reach user B's record by changing an identifier in the address bar? In inherited applications the answer is yes more often than it should be. And the gap between interface and API: a field hidden or disabled on screen but still accepted by the endpoint behind it is not protected at all.

Security is not a launch milestone either. Vulnerabilities are disclosed against frameworks and libraries continuously, so an application running an unpatched dependency is exposed whether or not anything changed on your side. That is the practical argument for a maintenance contract rather than a one-off build.

Migrating off a legacy system

This is how a large share of these projects actually arrive: there is an existing system, it works badly, somebody built it years ago, and it still runs the organisation.

The work differs from a new build. It starts with establishing what the current system actually does, which usually includes undocumented behaviour that people depend on without realising. Then the data: extracting it, assessing its quality, deciding what is migrated, what is archived and what is deliberately left behind, and mapping it into the new model. Then the cutover plan, because for most organisations the old system cannot simply stop. That means either parallel running with reconciliation, or a staged migration by module or user group, and the choice depends on how much duplication your team can absorb.

The honest warnings. Data quality is almost always worse than the client expects, and cleaning it is a workstream rather than a line item. Features that look redundant sometimes turn out to be load-bearing for one department. And a cutover scheduled across a month end, a quarter end or a government reporting deadline is a decision you make once.

Accessibility and bilingual delivery

Both matter more in Abu Dhabi than elsewhere in the country, because so much of the commercial base is government-adjacent or institutional.

Arabic and English, with right-to-left layout designed into the interface rather than retrofitted, is a requirement rather than a preference for anything serving government bodies, institutional users or local retail customers. Building it in from the start costs a fraction of adding it later, because retrofitting right-to-left support touches every screen.

Accessibility is the same calculation. Keyboard navigation, sufficient colour contrast, proper form labels, sensible focus handling, text that scales and structure that works with a screen reader. For an internal system it matters because some of your staff will need it and you do not choose which. For a public-facing or government-facing portal it can be a procurement requirement, and discovering that after the build is an expensive way to learn.

Custom web applications by industry in Abu Dhabi

What the system has to do changes completely by sector. Several of these also have a page covering the website and platform side: logistics, real estate, trading, construction and contracting, clinics and healthcare and education.

How we work, and what the engagement looks like

Our preference for a first project is a fixed-scope discovery phase producing a specification, then whichever build model that specification shows is appropriate. You are not committing a build budget before anybody knows what is being built, and the specification is yours regardless of who builds it.

Projects run in defined stages with a staging environment you can access throughout, a named point of contact, acceptance criteria agreed in advance per stage, and costed variations for changes. For Abu Dhabi clients most of this runs by call and shared screen, with site visits where photography, a technical walkthrough or a stakeholder workshop justifies the drive.

What determines the cost of a custom web application

We do not publish a figure, and a number given before the scope is understood is a hook rather than an estimate.

What drives it: the number of distinct user roles, because each is effectively a separate interface; the number of screens and workflows; how many integrations are required and how well documented the systems at the far end are; whether the data model involves complex pricing, scheduling or calculation rules; whether bilingual delivery is in scope; expected concurrent load, which drives architecture and hosting; compliance and data residency requirements, which in Abu Dhabi healthcare are substantial; whether there is a legacy migration with data cleaning; the depth of testing the application's criticality justifies; and the support level afterwards.

Two costs clients routinely omit from the budget. Ongoing maintenance is a real annual figure, not an optional extra, and an application without it degrades. And your own team's time during discovery and acceptance testing is substantial; projects that run late are usually waiting on client-side decisions rather than on development.

Why choose Tomsher for custom web application development in Abu Dhabi

Five things, each of which you should check against every firm you shortlist, including us.

Code ownership and documentation in writing. You own the custom code, you hold the repository, you receive technical and user documentation, and hosting, domain and third-party accounts are in your name. Ask the others the same question and compare the answers, and ask which law governs their development agreement.

Everything in house, since 2011. Development, design, testing and DevOps are our own employees, not a freelancer network or an offshore production house. On a long-lived system the people who understand why it was built that way should still be reachable in three years.

We will talk you out of it where something simpler fits. Off-the-shelf products, configured platforms and our own ready-made systems all cost less than a custom build, and we would rather say so in week one than take the budget.

We maintain what we build. The maintenance contract covers patching, updates, backups, monitoring and a defined response time, which matters because unpatched dependencies are the commonest route into a business application.

Arabic and English, properly. Including right-to-left interface work designed in rather than retrofitted, which matters disproportionately for Abu Dhabi's institutional client base.

And one thing we are not: a local Abu Dhabi firm. Our office is in Dubai. If having your developer in the same city is a requirement, that is a legitimate basis on which to choose somebody else, and we would rather say it here than discover it at the second meeting.

What we will not promise

We will not quote a price or a delivery date before the scope is defined, because both would be invented. We will not promise that the first version will be the final version; custom software is iterative and anyone claiming otherwise has not built much of it. We will not claim client names, project counts, retention rates, team sizes or award badges we cannot substantiate. We will not tell you a custom build is the right answer when a product you could buy next week would do the job. And we will not advise you on which jurisdiction or governing law suits your contract, because that is a lawyer's work and we are not lawyers.

What we do commit to is a written specification before development, acceptance criteria agreed per stage, access to working software throughout, documentation and code ownership on handover, and telling you early and plainly if the project is heading off course.

Frequently asked questions

Who owns the source code of a custom web application you build for us?

You do. You hold the repository, the intellectual property in the custom code is assigned to you in writing, and hosting, domain and third-party accounts are opened in your name. You also receive the database schema, a list of third-party components and their licences, and technical and user documentation. We may retain rights in our own pre-existing frameworks and internal tooling, which is normal, and we state that explicitly. Ask every firm you shortlist, because none of the four competing pages we reviewed answers it anywhere.

Does it matter that our company is registered in ADGM rather than onshore Abu Dhabi?

For the contract, potentially yes. ADGM states on its own jurisdiction page that it operates with direct application of English common law as an independent jurisdiction, and that it extends across Al Maryah and Al Reem Islands following the expansion of the International Financial District on 24 April 2023. That means an ADGM entity's development agreement, its intellectual property assignment and its dispute resolution can sit within a common law framework, which is a different position from an onshore company contracting under UAE federal law. Which suits you is a question for your counsel, not for us, but it should be settled in the contract rather than discovered in a dispute.

Do you have an office in Abu Dhabi?

No. Our office is at M05, Wafi Residence, Oud Metha Road, Umm Hurair 2, Dubai, and we work with Abu Dhabi clients remotely with site visits where a project warrants it. We say this directly because several agency pages targeting this emirate imply a local presence that does not exist. If having your developer in the same city is a requirement for you, that is a reasonable basis for choosing somebody else.

How much does custom web application development cost in Abu Dhabi?

The range is too wide for a figure to mean anything before the scope is known. The drivers are the number of user roles, the number of screens and workflows, how many integrations are needed and how well documented the far end is, the complexity of the pricing or scheduling rules, bilingual delivery, expected load, compliance and data residency requirements, any legacy migration, the depth of testing and the support level afterwards. Give us the scope and you get a written proposal with deliverables, stages and exclusions.

Where will our data be hosted, and does Abu Dhabi have extra rules?

For health data, yes. Federal Law No. 2 of 2019 contains a localisation provision, reported as Article 13, under which health data relating to health services provided in the UAE may not be stored, processed, generated or transferred outside the UAE without an approving decision from the health authority or the Minister. Abu Dhabi adds the Department of Health's ADHICS standard, which Al Tamimi's analysis notes restricts cloud use for health information. We could not read the standard directly, so we quote no control references and recommend obtaining the current version from the Department of Health. Either way, the hosting decision comes before the architecture decision, because retrofitting residency is expensive.

Do you work in Al Ain and the Al Dhafra region?

Yes. Al Ain covers Al Jimi, Al Muwaiji, Al Towayya, Asharej, Al Jahili, Al Khabisi, Zakher, Al Yahar and the Al Ain Industrial Area, and Al Dhafra covers Madinat Zayed, Ruwais, Ghayathi, Liwa, Mirfa, Sila and Delma Island. Both are routinely underserved by Dubai-based agencies, and for Al Dhafra in particular there is a real engineering consequence: applications used at remote sites with patchy connectivity need to tolerate a dropped connection and reconcile afterwards, which is a design decision made at the start or not at all.

Can you take over an application another developer built?

Usually yes, and we review it before committing. We look at code quality, architecture, dependency versions, hosting setup and whether documentation exists, then tell you honestly whether it is worth maintaining or whether a rebuild costs less over two or three years. The first practical question is whether you actually hold the repository and the accounts, because if you do not, that has to be resolved before anything technical can start.

Should we build custom software or buy an existing product?

Buy, if your process is close to the industry standard and you can adapt to the software. Build, if the process is your competitive advantage, the integrations are specific to you, the scale is real, or nothing on the market does it. Low-code suits internal tools, simple workflows and early validation, and struggles on performance at scale, deep integration and portability. We publish ready-made systems for several common requirements, and if one fits closely we will point you at it rather than quote a custom build.

What happens after launch?

The application goes onto a maintenance contract covering framework and dependency updates, security patching, backups, uptime monitoring, certificate renewal and a defined response time, plus a route for new requirements. This is not an upsell: vulnerabilities are disclosed against libraries continuously, so an unmaintained application becomes exposed over time even if nothing on your side changes. We would rather you held a maintenance contract with somebody than with nobody.

Which technologies do you build on?

React, Next.js, Vue and Angular on the front end, with TypeScript on larger applications; Node.js, Laravel and PHP, Python with Django and .NET on the back end; PostgreSQL, MySQL, MongoDB and Redis for data; REST and GraphQL for APIs; progressive web applications where offline or mobile use matters. We choose the stack to fit the application and whoever will maintain it, and we will host on AWS, Azure, Google Cloud or your own provider, using UAE regions where residency requires it.

Can the application integrate with our existing ERP or accounting system?

Yes, and the integration is a scoped workstream rather than an afterthought. How straightforward it is depends almost entirely on the system at the other end: a documented API is simple, an undocumented or legacy system needs investigation first, and some require a middleware layer or scheduled file exchange. We also build the error handling for when the other system is unavailable, which is the part most often skipped and the part that generates support calls.

Will you build the application in Arabic as well as English?

Yes, including right-to-left layout designed into the interface rather than retrofitted, and Arabic content written rather than machine translated. In Abu Dhabi this matters disproportionately, because so much of the commercial base is government-adjacent or institutional, and for those users Arabic parity is usually a requirement. Building it in from the start costs a fraction of adding it afterwards, since retrofitting right-to-left support touches every screen.

How do you handle changes once development has started?

As costed variations against the agreed specification, which protects both sides. On a fixed-scope engagement that keeps the price honest; on time and materials it is simply a reprioritisation. What we will not do is absorb unlimited change inside a fixed price, because the way agencies survive that is by quietly cutting testing and documentation, and you find out later.

What should we ask when comparing custom web application development companies in Abu Dhabi?

Six questions. Who owns the source code and what exactly is handed over. Which law governs the development agreement and how IP transfers under it. Are the developers employees or subcontractors. What is excluded from the quote. What happens six months after launch, and what the response time is. And who holds the hosting, domain and repository accounts. Our guide to the key factors in choosing a UAE web development company covers the rest of the checks.

Sources

• Abu Dhabi Global Market, jurisdiction page, for the statement that ADGM operates with direct application of English common law as an independent jurisdiction, that it extends across Al Maryah and Al Reem Islands covering 14.38 million square metres, and that the International Financial District expansion to include both islands is dated 24 April 2023. adgm.com
• Latham and Watkins, client alert number 2514, 19 June 2019, on Federal Law No. 2 of 2019 on the use of information and communications technology in health fields, for the Article 13 health data localisation provision. Secondary analysis, published before the law's implementing regulations.
• Al Tamimi and Company, Law Update article on the same federal law, for the localisation provision, the expectation that transfer approvals would be limited, and the reference to the Abu Dhabi Department of Health ADHICS standard restricting cloud use for health information. Secondary analysis.

Three notes on what is not sourced here. The ADHICS standard itself could not be read directly, so this page names it and attributes the cloud restriction to the secondary analysis above without quoting control references or a version; obtain the current standard from the Department of Health before relying on the detail. The health data localisation provision applies to health data specifically and should not be read as a general UAE residency rule for all sectors. And the ADGM position is a matter for your own legal advisers rather than something to act on from this page.