AR mobile app development for iPhone and Android
AR mobile app development is the work of building apps that place digital content in the camera view of the real world, so a buyer sees the sofa in their own room, a technician sees the next step over the real machine, or a visitor sees the route on the floor. We build augmented reality mobile apps with Apple's ARKit and Google's ARCore, as a feature inside a useful app rather than a demo, with the code and the store accounts in your company's name and the backend hosted in an EU region.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
What augmented reality is good for
Augmented reality earns its place when seeing something in place answers a question faster than a photo, a drawing or a manual. The use cases that tend to last are practical:
- Choosing. Furniture, fittings, machines, signage or kitchen layouts shown at real scale in the customer's own space before they buy.
- Measuring. Rooms, walls, openings and distances measured with the phone, with the result saved to a quote or an order.
- Guiding. Step-by-step instructions anchored to equipment for installation, maintenance and inspection, so the field worker does not hold a manual in one hand.
- Training. Procedures practised on a virtual machine or in a virtual room, where the real one is expensive, dangerous or far away.
- Finding. Indoor routes, shelf locations or points of interest shown in the camera view.
Where the answer is a picture, a video or a 3D viewer on screen, we will say so. Augmented reality adds cost and device limits, so it should be there because it does the job better.
ARKit and ARCore: what the platforms require
The two platforms do similar things in different ways, and both set limits on which phones can run the experience. We read the platform documentation for each project; these points come from Apple's and Google's pages as read on 11 November 2026.
| Point | iPhone and iPad (ARKit) | Android (ARCore) |
|---|---|---|
| Minimum | iOS 11 or later and an A9 processor or later; some features need later iOS versions or specific devices (Apple) | A certified device; on Google Play, Android 7.0 or newer unless the model needs a higher version (Google) |
| App that only works with AR | The arkit key in the app's required device capabilities, so only compatible devices can install it | "AR Required": the android.hardware.camera.ar feature and the ARCore meta-data set to required, minimum SDK level 24 (Google) |
| App where AR is one feature | A runtime check of the AR configuration's support before the feature is offered | "AR Optional": the app installs anywhere and asks for Google Play Services for AR only when the user opens the AR feature |
| Face effects | The front TrueDepth camera, checked at runtime; a privacy policy that explains how face data is used | The augmented faces feature on supported devices |
| Camera permission | A clear camera usage text, shown when the system asks | The camera permission in the manifest and at runtime |
For most clients the right choice is AR as an optional feature: the app works on every phone, and the AR part appears on phones that support it. An AR-only app shuts out users on older or uncertified devices, which matters more on Android, where the list of certified devices is long but not complete.
Built to pass App Store and Google Play review
Apple's App Review Guidelines (read 11 November 2026) say in guideline 4.2.1 that apps using ARKit should provide rich and integrated augmented reality experiences, and that merely dropping a model into an AR view or replaying animation is not enough. That rules out the thin AR app that is only a 3D model and a camera. It is one more reason to build AR into an app that has a real job: a catalogue with prices and ordering, a measuring tool that saves results, a service app with tasks and reports.
Two other guidelines matter. Guideline 5.1.2(vi) says data from depth and facial mapping tools, naming ARKit, may not be used for marketing, advertising or use-based data mining, including by third parties. Guideline 2.5.13 says apps that use facial recognition for account sign-in must use Apple's LocalAuthentication, not ARKit, where possible. We design the data flows to those rules from the first sketch, and fill the store privacy declarations from the actual data the app sends, as our app development page describes.
Camera, space and face data under the GDPR
An AR app sees what the camera sees: a customer's home, a factory floor, other people. We keep that data on the device by default. Room scans, anchors and camera frames are processed on the device and sent to a server only when a feature needs it, such as a saved measurement or a shared session, and then only the data that feature needs. Face tracking for an effect or a try-on is not the same as identifying a person, but face data still deserves care. The GDPR treats biometric data used to uniquely identify someone as a special category under Article 9, so we do not build identification into a try-on feature, and face data stays on the device unless there is a written reason and a lawful basis. The backend, where there is one, is hosted in an EU region as standard.
3D content: the part that is easy to underestimate
The quality of an AR experience depends on its 3D models as much as on its code. A product shown at real scale must be modelled at real scale, with materials that look right in a lit room, and light enough to load quickly over a mobile connection. Models usually start from CAD files, existing product renders or a 3D scan, and are converted and reduced for mobile. On iPhone the native format is USDZ; on Android and the web it is glTF. We set up a pipeline so new products become AR-ready models without a manual rebuild for each one, and the models, like the code, belong to you.
For product viewing alone, a full app is not always needed. AR Quick Look on iPhone and Scene Viewer on Android can show a model from a web page, and we can add that to an existing online store. A full app is worth it when the experience needs saved places, accounts, offline use, tracking over time or a link to your systems.
Native, Unity or cross-platform?
| Approach | Fits when | Watch out for |
|---|---|---|
| Native ARKit with RealityKit, and ARCore with Kotlin | The best tracking, newest platform features and tight integration with the rest of a native app | Two codebases for the AR part |
| Unity with AR Foundation | Rich 3D, game-like interaction, or the same scene on both platforms and on headsets | A heavier app, and a game engine inside a business app |
| Cross-platform app with native AR modules | A normal app in Flutter or React Native where AR is one screen | The AR screen is still native code on each platform |
| Web viewer only | Product viewing from a store or catalogue page | No tracking over time, no offline use |
The choice goes into the written scope with the reasons. For the wider framework question, see cross-platform app development and our guide to mobile app development frameworks.
Testing AR in the real world
AR fails in ways a simulator does not show: dark rooms, shiny floors, white walls with no texture, moving people, warm phones that slow down after ten minutes. We test on a spread of real devices, old and new, in the kinds of spaces your users will be in, and we design the app to explain itself when tracking is poor, rather than leave the user waving the phone. Battery use and heat are measured, because an AR session is one of the heaviest things a phone does. Our mobile app testing page covers the wider test plan.
How the project runs
- Use case and devices. The job the AR feature does, who uses it, where, and on which phones, checked against your analytics or customer data.
- Scope and fixed price in writing. AR features, the rest of the app, 3D content, integrations and what the first version leaves out.
- Prototype on real devices. The AR part first, tested in real spaces, because that is where the risk is.
- Build in two-week rounds. You install each version through TestFlight and Google Play testing.
- Store review and launch. Published from your accounts, with privacy declarations that match the code.
- Updates. ARKit and ARCore change with each operating system release, so the app needs regular updates, as our mobile app maintenance page describes.
The source code, 3D models, store accounts and hosting are in your company's name from the start. For technician apps with jobs, checklists and parts, see field service management software. See prices.
Questions we get
What is augmented reality mobile app development?
Building iPhone and Android apps that place digital content in the camera view of the real world: a sofa in your living room, a machine part over the real machine, measurements on a wall or a route on the floor of a warehouse. On iPhone the platform is Apple's ARKit; on Android it is Google's ARCore, delivered through Google Play Services for AR.
Which phones support AR apps?
According to Apple's documentation, ARKit needs iOS 11 or later and a device with an A9 processor or later, and some features need newer devices, such as the TrueDepth camera for face tracking. On Android, Google lists the certified ARCore devices, which on Google Play must run Android 7.0 or newer unless a model needs a higher version. We check your users' actual devices before deciding what the app requires.
Should AR be the whole app or one feature?
Usually one feature. Apple's guideline 4.2.1 asks that apps using ARKit provide rich and integrated augmented reality experiences, and a model dropped into a camera view is not enough. Most successful AR apps solve a job, such as choosing, measuring, guiding or training, and keep a normal screen for users whose phones do not support AR.
Can AR work without an app?
For product viewing, often yes. AR Quick Look on iPhone and Scene Viewer on Android can show a 3D model from a web page. A full app is worth it when the experience needs tracking over time, saved places, accounts, offline use or integration with your systems.
Who owns the 3D models and the code?
You do. The app code, the 3D assets we produce or convert, and the store accounts are in your company's name, and the backend is hosted in an EU region as standard.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.