Should a UK app be native iOS, or Flutter or React Native? +
iPhone holds only a narrow lead over Android in the UK, so if you need both at launch, Flutter or React Native is usually the better fit. Native Swift makes sense for banking- or health-grade apps, heavy Apple framework use such as Apple Pay, HealthKit or widgets, or an iPhone-first audience. We recommend one after reviewing your feature list.
Can you take over and modernise our Objective-C app? +
Yes. We audit the project, build settings and dependencies first, then move screens to Swift and SwiftUI one at a time, so the app keeps shipping updates under the same App Store listing, with its ratings and reviews intact. Older UIKit screens that work well can stay until there is a reason to change them, and access to any live customer data is agreed with you before we start.
Can the app support strong customer authentication for payments? +
Yes. For account access and online payments covered by the Payment Services Regulations 2017, we implement two-factor journeys such as device possession plus Face ID or a passcode, using the Secure Enclave and Keychain. Your payment provider and compliance team confirm the final flow against the FCA's SCA rules.
How do you test an iPhone app for accessibility? +
We build and test to WCAG 2.2 AA with VoiceOver, Dynamic Type, sufficient contrast and a clear focus order. That is the level public sector apps must meet under the 2018 accessibility regulations, and it supports service providers' duties under the Equality Act 2010. We can also help draft the accessibility statement public bodies must publish.
Can you build an iOS app for the NHS or a health-tech supplier? +
We can build the app and help prepare the technical evidence, such as architecture, data flows and security controls, that DTAC and DSPT assessments ask for. Clinical-safety sign-off under DCB0129 and the assessments themselves remain with your organisation and its clinical safety officer; we are not NHS-approved.
Do you handle App Store submission and review? +
Yes. We set up App Store Connect, signing and provisioning, share TestFlight builds, and prepare screenshots, privacy details and review notes. If Apple rejects a build, we address the cited guideline and resubmit. In April 2026 the CMA also accepted commitments from Apple and Google on fair, transparent app review and no retaliation against developers.
Who owns the Xcode project and the App Store listing? +
You do. The repository, Xcode project and documentation sit in your accounts, and we recommend publishing under your own Apple Developer account so the listing, ratings and certificates stay with your business if you change supplier. Stand-ups and TestFlight demos are held in your morning or lunchtime.