Question 1

Does my UK mobile app need to comply with UK GDPR?

Accepted Answer

Yes, if your app processes personal data about UK users in the course of commercial activity. UK GDPR applies regardless of where your company is based. The practical requirements for mobile apps include: processing personal data on a documented lawful basis, collecting only what is necessary for the stated purpose, providing data subject rights mechanisms (access, erasure, portability, objection) within one calendar month, maintaining records of processing activities, and implementing security measures appropriate to the risk of the processing.

Question 2

What is DTAC and does my health app need it?

Accepted Answer

DTAC (Digital Technology Assessment Criteria) is the NHS England standard for assessing digital health technologies before they are used in NHS services or recommended by NHS clinicians. If you want your health mobile app to be used in the NHS — whether deployed to NHS staff, listed in the NHS App Library, or recommended by NHS clinicians to patients — it must pass DTAC assessment across five domains: clinical safety, data protection, technical security, interoperability, and usability/accessibility. We produce DTAC-supporting technical documentation as a project deliverable.

Question 3

Should a UK consumer app be built for iOS, Android, or both?

Accepted Answer

Both, for almost all UK consumer products. With iOS at 49.44% and Android at 50.07% of UK smartphones (StatCounter October 2025), building for one platform means leaving nearly half the addressable market unreached. Cross-platform development using Flutter or React Native produces both iOS and Android applications from a single codebase at 30 to 50% less than parallel native builds, making dual-platform the standard commercial choice for UK consumer products.

Question 4

What does FCA regulation mean for my UK fintech mobile app?

Accepted Answer

If your mobile app conducts regulated financial activities — accepting payments, providing account information services, initiating payments, offering consumer credit, or distributing insurance — it must be authorised by or registered with the FCA, or operate under the permissions of an authorised firm. Building the app without understanding FCA applicability first means you may need to rebuild core authentication and data architecture after authorisation. We scope FCA applicability during discovery for all UK fintech mobile engagements.

Question 5

Do you have operations in the UK?

Accepted Answer

Yes. Noukha has commercial operations in the UK, which means UK clients can engage with a UK-registered entity for contract and invoicing purposes, receive sprint review and technical communication during UK business hours (GMT and BST), and work with a development team that is accountable within the UK commercial and legal framework.

Question 6

How do you handle UK data residency requirements?

Accepted Answer

We deploy UK mobile applications and their backend infrastructure to UK-region cloud infrastructure: AWS eu-west-2 (London), Azure UK South and UK West, or GCP europe-west2 (London) where UK data residency is required by UK GDPR policy, NHS data governance requirements, or government data handling standards. Data residency is designed as a structural architecture constraint during the infrastructure planning phase.

Question 7

How long does a UK mobile app project take?

Accepted Answer

A single-platform UK consumer MVP takes 8 to 12 weeks. A cross-platform UK consumer app takes 12 to 20 weeks. UK fintech apps with FCA compliance architecture take 16 to 28 weeks. NHS digital health apps requiring full DTAC documentation take 20 to 36 weeks. GDS-compliant government digital services typically take 20 to 36 weeks. All timelines are produced from a documented specification and compliance requirements register.

Question 8

Will I own the source code after the project?

Accepted Answer

Unconditionally. When a project closes, 100 percent of the intellectual property transfers to you — all source code, design assets, API documentation, database schemas, and deployment configurations. No licence fees, no retained access, no conditions.