Skip to main content Scroll Top

Augmented Reality App Development Company: AR Apps for iPhone, Android, the Web and Headsets

Updated September 2026 · Written and maintained by the Progression Agency strategy team

An augmented reality app development company plans, designs and engineers software that pins 3D objects, instructions or live data to the physical world through a phone camera, a web browser or a headset. The work spans native ARKit and ARCore apps, web AR that opens without an install, spatial apps for Apple Vision Pro, Meta Quest and Android XR, and the 3D asset pipeline that feeds all of them, for uses that run from retail try-on to technician guidance. Progression Agency is based in New York City and works with clients across the United States and worldwide.

On this page · 17 sections
  1. What does an augmented reality app development company actually deliver?
  2. AR, VR or mixed reality: which one does the job?
  3. Which platform should an AR app target first?
  4. Native, Unity or web: choosing how to build the AR layer
  5. The 3D asset pipeline: USDZ, glTF and budgets that keep scenes fast
  6. Use cases where augmented reality earns its budget
  7. What makes an AR experience feel solid rather than gimmicky?
  8. Camera data, face tracking and privacy rules for AR apps
  9. Virtual reality app development: when a headset beats a phone
  10. How much does augmented reality app development cost?
  11. How long does an AR build take?
  12. Measuring an AR feature: the numbers worth tracking
  13. How founders and product leaders ask AI assistants for an AR developer
  14. How to choose an AR app development company
  15. The skills an AR and VR team needs
  16. AR VR app development services we provide
  17. Related services and guides

The short answerAugmented reality app development is four jobs done together: choosing the platform (ARKit on iPhone and iPad, ARCore on Android, WebXR or AR Quick Look in the browser, visionOS or Meta Horizon OS on headsets), preparing 3D assets in USDZ and glTF, engineering tracking, placement and rendering, and shipping through the app stores or the web. Success is judged by the decision the AR moment supports: an item added to cart after it was placed in a room, a procedure completed without a trainer, a repair closed on the first visit. By our published planning ranges, AR added to an existing app runs $30,000-$80,000 over 6-12 weeks and a standalone product visualization app $60,000-$150,000 over 3-6 months, with a written quote after scoping. A one-scene prototype on your own devices comes first, so feasibility is settled before the full budget is committed.

Search volumes and costs per click are Ubersuggest data for the United States, September 2026. Platform capabilities, limits and review rules are quoted from Apple, Google, W3C, Khronos, Unity, Meta and OpenUSD documentation, linked where they appear; the Illinois statute is linked to the Illinois General Assembly. Price ranges are the planning ranges published on our app development pages; a written quote follows scoping.

What does an augmented reality app development company actually deliver?

A working AR experience and everything that keeps it working: the app or web viewer, the 3D content, the service that delivers that content, and device testing that proves placement holds in real rooms. The code is often the smaller share of the effort.

Apple’s ARKit documentation offers a precise yardstick. It describes augmented reality as user experiences that add 2D or 3D elements to the live view from a device’s sensors “in a way that makes those elements appear to inhabit the real world,” and says ARKit combines device motion tracking, world tracking and scene understanding to make that possible. Every line of an AR budget serves that illusion: tracking that does not drift, lighting that matches the room, models light enough for a mid-range phone, and prompts that tell people where to point the camera.

  • A decision brief: the question AR answers and the metric that proves it.
  • A device matrix covering the phones, browsers and headsets to support.
  • A one-scene prototype running on those devices before the full budget is spent.
  • Master 3D models with USDZ and glTF exports held to a performance budget.
  • The AR app, feature or web viewer, with fallbacks for unsupported devices.
  • A content service so models and variants change without a store release.
  • Analytics events and a launch report tied to the decision metric.

Discovery that starts from a decision

Useful AR answers a question a photo cannot: will this sofa fit under the window, which valve comes first, how does the kitchen look with the island moved. We write that question down, name the metric that shows it was answered, and check whether a 3D viewer or a short video would answer it more cheaply. If nothing changes when the object is in the room, the AR is decoration.

3D content production and optimization

Much of the schedule risk sits in the models rather than the app. Product files arrive as CAD, as meshes built for rendering or as nothing at all, and each needs clean-up, texture baking, material setup and export to two formats before it loads quickly on a phone.

Engineering: tracking, placement, occlusion and rendering

The app detects surfaces, anchors content, matches lighting and hides virtual objects behind real ones where the device can measure depth. It also recovers gracefully when tracking is lost, which happens in dim rooms, on blank walls and when someone walks through the scene.

Release, analytics and content updates

AR ships through the App Store, Google Play, the web or a headset store, and models should update without a new app release. Analytics record whether people open AR, whether placement succeeds and what they do next.

ARKit — iPhone and iPad. iOS and iPadOS 11 and later.
ARCore — Android phones. Certified devices only.
WebXR — Web browsers. W3C draft, June 2026.
visionOS — Apple Vision Pro. Windows, volumes, spaces.
Quest — Meta Horizon OS. Unity, Unreal, OpenXR.
Android XR — Headsets and glasses. Jetpack XR, OpenXR.

AR, VR or mixed reality: which one does the job?

Choose AR when people must stay in their real surroundings, VR when the surroundings are the problem, and mixed reality when a headset should blend both. The device plan follows from that choice.

Augmented, virtual and mixed reality compared for business apps
Augmented reality (AR)Virtual reality (VR)Mixed reality on headsets
What the user seesThe real world through a camera, with digital content anchored in itA fully rendered environment that replaces the real oneThe real room, shown through passthrough, with digital objects placed in it
Typical devicesiPhone, iPad, Android phones, web browsersMeta Quest and other headsets; Apple Vision Pro in a Full SpaceApple Vision Pro, Meta Quest, Android XR headsets
Strongest business usesProduct placement, try-on, wayfinding, work instructionsProcedural and safety training, simulation, design reviewSpatial product demos, collaborative review, guided assembly
Main build toolsARKit, RealityKit, ARCore, WebXR, Unity AR FoundationUnity, Unreal Engine, OpenXRvisionOS SDK, Unity, OpenXR, Meta Spatial SDK
How people get itApp stores or a web linkHeadset stores or company-managed devicesHeadset stores or company-managed devices
Main constraintPhone performance and room lightingComfort, motion and headset accessHeadset cost and availability

The disciplines overlap more than the labels suggest. Virtual reality app development uses the same engines, 3D pipeline and interaction thinking as AR, so the same team can plan both. Where a client needs virtual reality software development for training or simulation, we scope it on the same terms as AR work, with headset access and comfort testing written into the plan.

Grouped bar chart of US monthly searches, AR wording against VR wording: ar and vr app development 210 and 110; ar and vr app development company 210 and 70; augmented and virtual reality app development 170 and 110; augmented and virtual reality app development company 210 and 50. Ubersuggest, September 2026.Grouped bar chart of US monthly searches, AR wording against VR wording: ar and vr app development 210 and 110; ar and vr app development company 210 and 70; augmented and virtual reality app development 170 and 110; augmented and virtual reality app development company 210 and 50. Ubersuggest, September 2026.
US monthly searches, Ubersuggest, September 2026. The AR wording leads in all four pairs, with 800 searches a month across the AR phrasings against 340 for the VR phrasings.

Which platform should an AR app target first?

Target the devices your users already carry. For consumer AR that usually means iPhone and Android phones, often starting on the web; for training and field work it can mean a fleet of company-managed headsets.

AR platforms at a glance, from each platform’s developer documentation
PlatformNative toolsWhat the documentation says about reachGood first choice for
iPhone and iPadARKit with RealityKitARKit is documented for iOS and iPadOS 11 and later; apps built around AR can declare it so they install only on ARKit-compatible devicesConsumer apps, LiDAR room capture, try-on
Android phonesARCoreRuns on devices Google has certified; AR Required apps are offered on Google Play only to supported devicesBroad consumer reach alongside iOS
Web browsersWebXR, Scene Viewer, AR Quick LookNo install; the model-viewer component hands off to whichever AR viewer the device supportsProduct pages, campaigns, first pilots
Apple Vision ProvisionOS with SwiftUI, RealityKit and ARKitApps run in windows, 3D volumes or a dedicated Full SpaceSpatial demos, design review, premium retail
Meta QuestUnity, Unreal, OpenXR, Meta Spatial SDK, WebXRMeta Horizon OS supports mixed reality apps and existing Android appsTraining fleets and mixed reality
Android XR headsets and glassesJetpack XR SDK, Unity, OpenXR, WebXRMost existing Android apps appear as 2D panels in 3D space without changesEarly spatial versions of Android apps

iPhone and iPad: ARKit and RealityKit

ARKit handles sensing, and RealityKit, which Apple calls “an AR-first 3D framework,” handles rendering and simulation (RealityKit documentation). Apple’s guidance on device support and camera permission gives two paths: an app whose core function is AR adds the arkit key to its required device capabilities so it installs only on compatible devices, while an app with AR as a secondary feature checks support at run time. Either way, the app must explain in its Info.plist why it needs the camera.

Android phones: ARCore and Google Play Services for AR

ARCore uses simultaneous localization and mapping to track the phone, detects horizontal and vertical planes, estimates lighting and, on supported devices, builds depth maps from the main camera (ARCore fundamentals). It runs only on certified devices. Google’s ARCore setup guide separates AR Required apps, which Google Play offers only to supported devices and which install Google Play Services for AR automatically, from AR Optional apps, which install anywhere but need Android 7.0 or later to run AR features.

The browser: WebXR, Scene Viewer and AR Quick Look

Web AR reaches people from a product page or a QR code with nothing to install. The WebXR Device API is a W3C Candidate Recommendation Draft, dated 9 June 2026, that gives the web access to VR and AR devices, and its augmented reality module adds the immersive-ar session mode. On Android, Google’s Scene Viewer opens glTF models in AR; on iPhone and iPad, AR Quick Look opens USDZ files from Safari, Messages, Mail, News and Notes. Google’s model-viewer web component tries WebXR, then Scene Viewer, then Quick Look by default, and can generate the USDZ file on the fly.

Headsets: Vision Pro, Meta Quest and Android XR

Apple’s visionOS developer pages describe apps built from windows, volumes and a Full Space using SwiftUI, RealityKit and ARKit, with Reality Composer Pro for preparing 3D content and Unity as an alternative. Meta’s developer platform for Quest supports Unity, Unreal, OpenXR, the Meta Spatial SDK, WebXR and existing Android apps. Google’s Android XR documentation covers headsets and glasses and says existing 2D Android apps work by default, shown as a panel inside 3D space.

Planning an AR feature or app?Tell us the product, the decision AR should help people make and the devices your users carry; we reply with a platform recommendation and a prototype plan.

Get an AR proposal

Native, Unity or web: choosing how to build the AR layer

Native SDKs give the tightest tracking and store integration on one platform, Unity with AR Foundation shares one codebase across several, and web AR trades depth for reach. Plenty of products combine two of the three.

Build approaches for AR software development
ApproachStrengthsTrade-offsChoose it when
Native: Swift with ARKit and RealityKit, Kotlin with ARCoreNewest platform features first, best performance, natural fit with an existing native appTwo codebases for iOS and AndroidAR lives inside a native app or depends on platform-only features such as RoomPlan
Unity with AR FoundationOne codebase for ARKit, ARCore, visionOS, Meta Quest and HoloLens 2 through provider plug-insEngine runtime adds size; features vary by platformThe product is 3D-first or game-like, or must reach headsets as well as phones
OpenXR-based engines (Unity, Unreal)One royalty-free standard API across many headsetsMainly relevant to headsets rather than phonesVR or mixed reality training across more than one headset brand
Web AR: WebXR, model-viewer, Quick Look, Scene ViewerNo install, a shareable link, fastest to pilotFewer features; depends on browser supportProduct pages, campaigns and first tests of demand

Unity’s documentation says AR Foundation “enables you to create multi-platform augmented reality (AR) apps with Unity” through plug-ins for Google ARCore, Apple ARKit, Apple visionOS, OpenXR on HoloLens 2 and Meta Quest, and warns that feature availability varies by platform. That is why unity ar app development still needs a device matrix. For headsets, the Khronos Group describes OpenXR as “a royalty-free, open standard” for XR applications; version 1.1 is current, and Meta, Microsoft, Valve, Google for Android XR, HTC, Pico and others ship conformant runtimes.

Where each AR delivery path is strong (1-5, editorial)Where each AR delivery path is strong (1-5, editorial)
Editorial scores. Web AR leads on reach and speed, native on tracking and store features, Unity where headsets matter.

The 3D asset pipeline: USDZ, glTF and budgets that keep scenes fast

An AR product that reaches both iPhone and Android needs each model in two formats: USDZ for Apple’s viewers and glTF, usually packed as a single .glb file, for Android, the web and most engines. The pipeline that converts, optimizes and versions those files decides load time and visual quality more than any app code.

glTF is the Khronos Group’s “royalty-free specification for the efficient transmission and loading of 3D scenes and models,” nicknamed “the JPEG of 3D,” and glTF 2.0 was published as the international standard ISO/IEC 12113:2022 (Khronos glTF overview). USDZ comes from the OpenUSD world: the USDZ specification defines it as an uncompressed, read-only zip package whose files each begin on a 64-byte boundary so they can be read in place. The Alliance for OpenUSD, founded by Pixar, Adobe, Apple, Autodesk and NVIDIA, works on standardizing OpenUSD.

Mobile AR model budget, from Google’s Scene Viewer guidance
ConstraintGoogle’s figureHow we apply it
TrianglesRecommended limit of 100,000; 30,000 to 50,000 is the ideal rangeHero products near the top of the ideal range, catalog items well below it
MaterialsRecommended limit of 10Merge materials during texture baking
Texture resolutionMaximum 2048 x 2048Bake detail into normal maps instead of raising resolution
Mesh per material1Split or merge meshes before export
Model size10 MB; bigger models may result in a poor user experienceCompress textures and strip hidden geometry
FormatglTF 2.0 or .glbExport USDZ from the same master file for Apple devices

The figures come from Google’s Scene Viewer file requirements. We hold USDZ exports to the same targets and test them on the oldest iPhone the client supports.

Where models come from

CAD files from engineering are accurate but heavy. Rendering meshes from a marketing studio look right but can carry far more geometry than a phone should draw. When nothing exists, Apple’s Object Capture builds a 3D model from a series of well-lit photographs taken from many different angles, on iOS 17 and macOS 12 or later.

Optimization and levels of detail

Every model gets a triangle budget, baked textures, merged materials and compressed images. Complex products keep a lighter version for list views and a detailed version for close inspection.

Materials and lighting that survive conversion

Materials convert between glTF and USDZ with small differences, so each export is checked side by side on real devices under warm and cool light. Shadows are left to the viewer: Scene Viewer renders hard shadows when an object is placed, and Google recommends against baking them into the model.

A content service instead of app releases

Models, variants and prices live on a server or CDN, so a new colorway ships without an App Store update. Apple’s guideline 4.2.3 asks apps that must download extra resources at first launch to disclose the download size and prompt users first, so large libraries load on demand.

The 3D asset pipeline for ARThe 3D asset pipeline for AR
Every model passes the same gates, so a new product can go live without an app release.
USDZ — Apple's package. Read-only, 64-byte aligned.
glTF — Khronos standard. ISO/IEC 12113:2022.
100K — Triangle limit. Scene Viewer guidance.
2048 px — Largest texture. Per side, Scene Viewer.
10 MB — Model size. Scene Viewer guidance.
10 — Materials. Recommended limit.

Use cases where augmented reality earns its budget

AR pays when it removes a doubt that would otherwise cost a return, a site visit, a trainer’s hour or a second truck roll. These are the patterns with the clearest line from AR use to a business number.

Retail try-on and product placement

Placement shows furniture, appliances, fixtures and decor at true scale in the shopper’s room; try-on overlays eyewear, makeup, watches or shoes using face or body tracking. On iPhone, AR Quick Look supports Apple Pay and custom action banners, so a shopper can buy from inside the AR view. For stores built on a web platform, AR usually starts on the product page; our ecommerce web development services and 3D website design teams handle that side.

Training and simulation

Headset training suits procedures that are dangerous, expensive or rare to rehearse on real equipment. Mixed reality overlays steps on a real machine; full VR rebuilds a site that does not exist yet. Progress, errors and completion times flow to the learning system the client already runs, which our education and training software work covers.

Field service and work instructions

Technicians point a phone or tablet at equipment, the app recognizes it through image or object tracking, and anchored steps appear on the right component. Instructions and models are cached for sites without signal, and completed steps sync back to the work order.

Real estate, architecture and interiors

Apple’s RoomPlan uses the camera and LiDAR Scanner on iPhone and iPad to create a 3D floor plan of a room, including dimensions and types of furniture, exported as USD or USDZ. That makes measured rooms, virtual staging and renovation previews practical inside a property app; our real estate software development page covers listings, portals and agent tools.

Outdoor and location-based AR

Google’s Geospatial API lets content be attached remotely to any area covered by Google Street View, combining GPS, device sensors and Google’s Visual Positioning System. It offers anchors by latitude, longitude and altitude, on terrain or on rooftops, for Android, iOS, Unity and Unreal, which suits wayfinding, site previews and tourism.

Marketing activations and packaging

A QR code on a box, poster or display opens a web AR scene with no install, so the experience is one scan away for anyone holding the product. Campaign scenes are built on the web, and the 3D assets are reused on product pages afterward.

Try-on — Retail. Faces, wrists, feet.
Placement — Furniture and fixtures. True scale in the room.
Training — Headsets. Repeatable procedures.
Field service — Work instructions. Steps on the machine.
Property — Real estate. Rooms scanned with LiDAR.
Outdoor — Geospatial. Street View coverage.

What makes an AR experience feel solid rather than gimmicky?

Stable tracking, clear guidance and restraint. Apple’s review rules reject AR that only drops a model into the camera view, and its design guidelines spell out the patterns that keep people oriented.

App Store guideline 4.2.1 is blunt: “Apps using ARKit should provide rich and integrated augmented reality experiences; merely dropping a model into an AR view or replaying animation is not enough” (App Store Review Guidelines). The practices below are how an AR feature clears that bar.

Coach the scan

Apple’s Human Interface Guidelines for augmented reality note that people need to move their device so ARKit can evaluate the surroundings and detect surfaces, and recommend the built-in coaching view. Google’s documentation adds that flat surfaces without texture, “such as a white wall,” may not be detected properly, so the prompts tell people what to aim at.

Show where placement is possible

A visible indicator appears only once a surface is detected, objects snap to it at true scale, and a reset control recovers from a bad placement. When tracking is lost, the app says so and helps people return the device to where it was.

Design for arms, eyes and surroundings

Apple warns that holding a device at a set distance or angle for a long time is tiring, and that rapid, sweeping or expansive motions can be dangerous when people are absorbed in a scene. We keep sessions short, place objects at a comfortable distance and avoid interactions that make people move quickly through a room.

Offer AR only where it works

Apple’s guidance is to offer AR features only on capable devices. On unsupported phones the same screen shows a 3D viewer or photos instead of an error, and on Android an AR Optional app keeps the rest of the product available to everyone.

Not sure your 3D files are AR-ready?Send a sample model or CAD export and we will check it against the budgets on this page and tell you what conversion it needs.

Check my 3D assets

Camera data, face tracking and privacy rules for AR apps

Treat the camera feed and any face or room geometry as sensitive by default. Apple restricts what apps may do with facial mapping data, Illinois treats face geometry as a biometric identifier, and both shape how try-on features are built.

Rules that shape AR privacy design
SourceWhat it saysHow the build responds
App Store guideline 5.1.2(vi)Data gathered from depth or facial mapping tools such as ARKit, Camera APIs or Photo APIs may not be used for marketing, advertising or use-based data mining, including by third partiesFace and depth data stays on the device and never reaches analytics or ad SDKs
Apple camera permissionThe app’s Info.plist must include NSCameraUsageDescription explaining why it needs camera accessPlain-language purpose text, requested when AR is first opened
Illinois BIPA, 740 ILCS 14Lists a scan of face geometry as a biometric identifier and requires written notice of the purpose and term and a written release before collectionDesigns that avoid collecting or storing face geometry, or consent flows your counsel approves
BIPA retention and damagesA public retention schedule; destruction when the purpose is met or within 3 years of the last interaction; liquidated damages of $1,000 per negligent and $5,000 per intentional or reckless violationNo retention by default and a documented deletion path

Sources: Apple’s App Store Review Guidelines and camera permission guidance, and the Illinois Biometric Information Privacy Act. We build inside these rules and document how each feature handles camera data; whether a particular try-on design falls under a statute is a question for your counsel, not something this page decides.

Virtual reality app development: when a headset beats a phone

Choose VR when the environment itself is what people must learn or experience: a hazardous procedure, an unbuilt building, a machine too costly to take offline. A good VR app development company will also tell you when a phone or a video would do.

Training that has to be repeatable

The value of VR training is that every trainee faces the same scenario, errors are safe, and results are recorded. Scenarios are built in Unity or Unreal, and OpenXR keeps them portable across headset brands.

Design review and pre-visualization

Architects, retailers and manufacturers can walk through a space or product before it exists. The same master models feed the AR app, the website viewer and the headset scene, which is why the asset pipeline comes first.

Headsets as managed devices

When training runs on company-owned headsets, the plan covers device setup, app distribution, updates and data collection alongside the app itself. Meta’s platform also accepts WebXR content, which is useful for pilots before a native build.

Comfort and motion

Apple’s advice to introduce motion gradually applies with more force inside a headset. Locomotion, turning and text size are tested with first-time users, not only with the development team.

Buyers comparing virtual reality software development companies should ask how comfort testing is done and on which headsets. As a virtual reality app development company, we take on headset projects where the headset is justified and say so when it is not; our AR and VR services overview summarizes the offer on one page.

How much does augmented reality app development cost?

By our published planning ranges, AR added to an app you already run costs $30,000-$80,000, a standalone product visualization app $60,000-$150,000, and a VR training application $80,000-$300,000 or more. The number of 3D assets and the number of device targets move the estimate most.

AR and VR planning ranges (US market)
ScopePlanning rangeTypical timelineWhat drives it
AR feature added to an iOS or Android app you already run$30,000-$80,0006-12 weeksNumber of products, placement or try-on, platforms
Standalone product visualization app$60,000-$150,0003-6 monthsCatalog size, content service, analytics, both stores
VR training application$80,000-$300,000+4-9 monthsScenarios, interactions, headsets, learning-system integration
3D product viewer with AR on an existing website$8,000-$40,0003-8 weeksModels, viewer customization, page integration
Model preparation from CAD$2,000-$20,000 per product family2-6 weeksComplexity, variants, material accuracy
Hosting, CDN and maintenance for 3D content$300-$3,000 per monthOngoingTraffic, library size, update frequency

The ranges are published on our AR and VR app development and 3D website design pages and in our app development cost guide. They are planning figures for budgeting, not quotes; your quote follows a written scope.

What moves an AR app development cost estimate

Five things do most of the work: how many products need models and whether CAD exists, whether try-on needs face or body tracking, how many platforms and headsets must be supported, whether content updates need a management tool, and what the AR moment must connect to, such as a cart, a work-order system or a learning platform.

3D models — How many products. And whether CAD files exist.
Try-on — Face or body tracking. Tracking work plus privacy design.
Devices — Platforms and headsets. Each one joins the test matrix.
Updates — A content tool. New models without app releases.
Integrations — What AR connects to. Cart, work orders, learning platform.
Hosting — CDN and maintenance. $300-$3,000 a month, planning range.

How long does an AR build take?

Plan on 6-12 weeks to add AR to an app you already run and 3-6 months for a standalone product visualization app, per our published ranges; VR training runs 4-9 months. The first milestone is a prototype running on your own devices.

A typical AR feature timelineA typical AR feature timeline
Phases overlap; the prototype gates the budget for everything after it.
A typical AR feature project, phase by phase
PhaseWhenWhat you receiveCheck before moving on
Discovery and device planWeeks 1-2The decision to support, a success metric, a device matrix and an asset auditEveryone agrees what AR should change
One-scene prototypeWeeks 2-4One product or step running on target phones or headsetsPlacement holds in real rooms and lighting
Asset pipelineWeeks 3-8Master models, USDZ and glTF exports, a content serviceLoad time and file size inside budget
BuildWeeks 4-10The full AR flow, fallbacks for unsupported devices, analyticsEvery device in the matrix passes
ReleaseWeeks 8-12Store submissions or web launch, monitoringReview approval and stable sessions
ImproveMonthlyNew content and experiments on prompts and placementThe success metric moves

Measuring an AR feature: the numbers worth tracking

Measure the decision the feature supports, then the health of the experience underneath it. A high open rate with poor placement success means AR is being tried and abandoned.

AR metrics and what each one tells you
MetricWhat it tells youHow it is captured
AR entry rateWhether people find and trust the AR buttonEvents on the product page or screen
Placement successWhether tracking and surface detection work in real homes and sitesSession events from the AR view
Time to first placementHow clear the coaching isTimestamps from AR open to first anchor
Action after ARWhether AR changes behavior: add to cart, booking, task completedFunnel comparison with sessions that skipped AR
Returns or repeat visitsWhether expectations matched reality, where the client tracks itOrder or CRM data joined to sessions
Asset load timeWhether the pipeline is doing its jobClient-side performance logging

How founders and product leaders ask AI assistants for an AR developer

Buyers can ask ChatGPT, Claude, Perplexity, Gemini, Microsoft Copilot or Google’s AI Overviews for a shortlist of AR developers. The answers lean on pages that state platforms, deliverables and prices in plain text.

US searches for AR and VR development servicesUS searches for AR and VR development services
US monthly searches, Ubersuggest, September 2026. Company and service phrasings draw as much volume as the bare technology terms.

How the questions are phrased

Buyers describe the job rather than the technology: “recommend an augmented reality app development company that can build eyewear try-on for iOS and Android,” “who can put our furniture catalog into web AR without an app,” “which studios build Unity AR apps for field technicians,” or “best VR developer for safety training on Meta Quest.” Search data has the same shape: in Ubersuggest’s September 2026 figures, “ar app development company” and “augmented reality app development company” each draw 210 US searches a month, as many as “ar app development” itself.

What the assistants tend to cite

Assistants that search the web build answers from pages they can retrieve and quote. For this market that means agency service pages with specific platform detail, directory profiles and reviews, “top AR companies” roundups and, for technical claims, Apple, Google and W3C documentation. Ubersuggest’s September 2026 SERP analysis for “ar app development company” showed a Google AI Overview in the top position, and half of the first ten organic results were directories or “top companies” roundups rather than agency pages.

Using an AI shortlist well

Treat the answer as a starting list. Ask each named firm for a device matrix, a prototype plan and the 3D budgets it works to, ask the assistant follow-up questions that force specifics, such as which firms have shipped visionOS apps or WebXR viewers, and check every claim on the firms’ own pages.

What to publish so your AR product gets named

Once the feature ships, give assistants something to quote: a crawlable page explaining what the AR does and which devices support it, a model-viewer demo that works in a browser, store listings that name the use case, and help articles that answer setup questions. Our answer engine optimization team builds that side.

Need a number for the budget?Share the scope and we will map it to our published planning ranges and send a written estimate.

Request an estimate

How to choose an AR app development company

Pick the team that proves feasibility on your devices before asking for the full budget and treats 3D content as part of the job, not an extra.

What to require from an AR app development company
RequirementHow to check it
A device-first planAsk which phones and headsets they will test on and how that list was chosen
A paid prototype before the full buildAsk for a fixed-price, one-scene prototype on your own hardware
An owned 3D pipelineAsk who optimizes models, to what budgets, and in which formats they deliver
Evidence on the platforms you needAsk for live apps or web viewers on ARKit, ARCore, WebXR or visionOS, whichever apply
A privacy position on camera and face dataAsk how face or room geometry is processed, stored and deleted
Content updates without releasesAsk to see how a new model or variant gets published
Measurement tied to a business metricAsk what their report shows first: AR opens or the decision AR supports
Your ownershipConfirm you own the code, the models, the store accounts and the analytics

The same questions separate AR development companies that specialize in immersive work from general app shops that add AR on request, and they apply whether you hire a studio, a freelancer or an app development agency that also builds the rest of your product.

The skills an AR and VR team needs

An AR product needs more than an app developer: platform engineers, a 3D technical artist, a designer who understands spatial interfaces and a tester with a drawer full of devices.

Roles on an AR or VR project
RoleCore skillsWhy it matters
iOS engineerSwift, ARKit, RealityKit, SwiftUINative quality, RoomPlan and Quick Look integration
Android engineerKotlin, ARCore, JetpackDevice variety and Google Play requirements
Unity or XR engineerC#, AR Foundation, OpenXR, performance profilingCross-platform and headset builds
3D technical artistRetopology, UV and texture baking, USDZ and glTF exportModels that load fast and look right
Product designerSpatial interaction, coaching, accessibilityPeople know what to do in the first seconds
Backend engineerContent APIs, CDN, analytics eventsUpdates without releases and measurable outcomes
QA engineerDevice matrix, lighting and surface testingPlacement that holds outside the office

AR VR app development services we provide

Everything from a feasibility prototype to a multi-platform product, including the 3D pipeline and updates after launch.

  • AR mobile app development for iPhone, iPad and Android, native or cross-platform.
  • AR features added to an existing app, from product placement to guided workflows.
  • Web AR product viewers that open from a link or QR code, with Quick Look and Scene Viewer handoff.
  • Unity AR app development with AR Foundation for products that must reach phones and headsets.
  • Apple Vision Pro apps in visionOS, and Meta Quest and Android XR builds through Unity or OpenXR.
  • Virtual reality app development for training, simulation and design review.
  • 3D asset production: CAD conversion, photogrammetry clean-up, optimization and USDZ and glTF export.
  • Content services so models, variants and prices update without app releases.
  • Camera, face-tracking and room-scanning features designed around privacy rules.
  • Analytics, experiments and maintenance after launch.

Each engagement starts with discovery and a prototype. A company that needs AR app development services for one feature can stop after the first release; others keep the team on for content and platform updates. Whichever AR app development company you choose, insist on that order: prototype, then budget.

Planning an AR app or feature?

Tell us the product, the decision AR should support and the devices your users carry. We reply with a platform recommendation, a prototype plan and a planning estimate.

Get an AR proposal

Software and app development

Frequently asked questions

Can you build an app for a VR headset as well as for phones?
Yes. Headset apps run on Meta Quest through Unity, Unreal or OpenXR, on Apple Vision Pro through visionOS with SwiftUI and RealityKit, and on Android XR headsets through the Jetpack XR SDK, Unity or OpenXR. We recommend a headset only when the environment itself is what users must learn or experience, such as a hazardous procedure; otherwise phone AR or web AR reaches more people for less.
What does an AR and VR developer actually do?
An AR and VR developer builds software that places digital content in the real world or in a virtual one. Day to day that means working with ARKit, ARCore, RealityKit, Unity or OpenXR, handling tracking and placement, optimizing 3D models, designing spatial interactions and testing on real devices in real lighting. On a project team the role sits alongside a 3D technical artist, a designer and QA.
How do AR development companies differ from general app agencies?
Specialist AR studios tend to bring a 3D pipeline, device labs and spatial design experience; general app agencies bring product, backend and app store experience and sometimes add AR on request. The best fit has both: someone who can optimize a model to a triangle budget and someone who can ship and maintain the app around it. Ask any candidate for live AR work on the platforms you need.
What should the statement of work for an AR build spell out?
It should name the decision the AR supports and the metric that proves it, the device matrix, the number of models with their formats and budgets, fallbacks for unsupported devices, how content updates without releases, analytics events, privacy handling for camera and face data, acceptance tests in real rooms, and who owns the code, models and store accounts. Anything missing from that list tends to become a change order.
Can a company outside New York hire you for an AR project?
Yes. Progression Agency is based in New York City and works with clients across the United States and worldwide. AR projects run remotely: we test on the device list agreed at the start, share builds through TestFlight, Google Play testing tracks or a web link, and review prototypes on video calls in your own rooms, where lighting and surfaces matter most.
Which skills should an AR/VR developer bring to a project?
Platform skills (Swift with ARKit and RealityKit, Kotlin with ARCore, or C# with Unity AR Foundation and OpenXR), 3D literacy (polygon budgets, texture baking, USDZ and glTF), performance profiling, spatial interaction design and disciplined device testing. Headset work adds comfort testing and device management. One person rarely covers all of it, which is why AR projects are staffed as a small team.
What goes into building an augmented reality game?
A game design that uses the real world as its board: tabletop and room-scale play, location-based play with Google’s Geospatial API, or short branded games for campaigns. Game logic is usually built in Unity with AR Foundation so one codebase reaches iOS and Android, with the same 3D pipeline and device testing as any AR build. Launch marketing is a separate job, which our video game marketing team covers.
How is development in VR different from building a mobile app?
VR adds constraints a phone app never meets: rendering a scene for both eyes smoothly, preventing motion discomfort, designing for controllers and hands instead of taps, and testing on headsets people wear for long stretches. The 3D pipeline is heavier too, because the scene is the whole world rather than one object in a room. Planning, backend and analytics work much as they do for mobile.
How should I compare one augmented reality app development company with another?
Give each candidate the same brief and compare four things: the device plan they propose, the price and scope of a first prototype, how they will produce and optimize your 3D models, and what they will measure after launch. Then check live work on the platforms you need and confirm you will own the code, models and store accounts. Vague answers about 3D assets are the clearest warning sign.
Will AR work on Android phones that are not ARCore certified?
Native ARCore features run only on devices Google has certified. An app published as AR Optional still installs on other phones and can show a 3D viewer, photos or video in place of AR, while AR Required apps are offered on Google Play only to supported devices. On the web, model-viewer shows its interactive 3D view on any modern browser and offers AR only where a viewer is available.
Is web AR good enough for product placement on iPhone and Android?
For single products, often yes. On iPhone and iPad, AR Quick Look opens USDZ models from Safari at true scale; on Android, Scene Viewer or WebXR does the same with glTF. Web AR is weaker at persistence and deep customization: multi-object room planning, saved scenes and complex try-on usually justify a native app. A sensible path is to pilot on the web and build native once usage proves demand.
Which 3D file formats do we need to hand over?
Send whatever you have: native CAD, rendering files such as FBX or OBJ, or existing glTF and USDZ. We produce one master model per product and export glTF or GLB for Android, the web and game engines, plus USDZ for Apple’s viewers. If nothing exists, we model from drawings or build a first version from photographs with Apple’s Object Capture, then clean it up.
How large can a 3D model be for mobile AR?
Google’s Scene Viewer guidance gives a practical budget: a recommended limit of 100,000 triangles with 30,000 to 50,000 as the ideal range, up to 10 materials, textures no larger than 2048 by 2048 pixels, and a 10 MB model size, beyond which the experience may suffer. We hold USDZ exports for iPhone to the same budget and test on the oldest device you support.
Can product photos be turned into a 3D model?
Yes, with limits. Apple’s Object Capture, on iOS 17 and macOS 12 or later, builds a 3D model from a series of well-lit photographs taken from many different angles. It needs a dedicated photo session rather than existing catalog shots, and the result still needs clean-up, optimization and material checks before it is ready for AR. CAD, where it exists, gives more reliable dimensions.
Do users need a device with a LiDAR Scanner?
No. ARKit and ARCore track surfaces with the camera and motion sensors, and ARCore can build depth maps from the main camera on supported devices. LiDAR improves some features: Apple’s RoomPlan, which creates 3D floor plans with dimensions and furniture types, uses the LiDAR Scanner on iPhone and iPad. We design fallbacks so LiDAR-only features never block the core experience.
Will Apple reject an AR app that only displays a 3D model?
It may. App Store guideline 4.2.1 says 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. A catalog viewer is better served by AR Quick Look on the web, while a native app should add real function: measurement, configuration, guided steps or purchase from the AR view.
Is face-tracked virtual try-on restricted anywhere in the US?
Illinois’ Biometric Information Privacy Act lists a scan of face geometry as a biometric identifier and requires written notice and a written release before collection, with liquidated damages of $1,000 per negligent and $5,000 per intentional or reckless violation. Apple separately bars the use of facial mapping data for advertising or data mining. We design try-on so face data stays on the device, and your counsel decides which rules apply.
Should our AR app be built in Unity or natively?
Native wins when AR sits inside an existing native app or depends on platform-only features such as RoomPlan. Unity with AR Foundation wins when the product is 3D-first or game-like, or must reach headsets as well as phones from one codebase. Unity’s documentation notes that feature availability varies by platform, so both routes still need testing on every target device.
What does AR cost for a smaller retailer?
Start with the web. By our published planning ranges, a 3D product viewer with AR on an existing website costs $8,000-$40,000 over 3-8 weeks, and model preparation from CAD $2,000-$20,000 per product family. An AR feature inside an existing app runs $30,000-$80,000. We quote after a written scope, and a pilot on your best-selling products shows whether a larger build is worth it.
How soon can we test a prototype on our own phones?
Our plans put a one-scene prototype on your target devices within the first two to four weeks, once discovery has fixed the decision, the device list and the first model. You install it through TestFlight or a Google Play testing track, or open it from a web link, and try it in the rooms and lighting where customers or technicians will actually use it.
Can we update 3D models without a new app release?
Yes, and we recommend it. Models, variants and prices are served from a content service or CDN, so a new colorway goes live without store review. Apple’s guideline 4.2.3 asks apps that must download extra resources at first launch to disclose the size and prompt users first, so large libraries are fetched on demand rather than all at once.
Do existing Android apps run on Android XR headsets?
According to Google’s Android XR documentation, most Android apps are compatible with XR headsets and wired XR glasses, and existing 2D apps work by default, shown as a panel inside 3D space. That gives a quick presence on the platform. Spatial features such as 3D content, anchors or immersive scenes still need work with the Jetpack XR SDK, Unity or OpenXR.
Is WebXR a finished standard?
Not yet. The W3C’s WebXR Device API is a Candidate Recommendation Draft, dated 9 June 2026 on the W3C site, and the WebXR Augmented Reality Module that adds immersive-ar sessions is also a Candidate Recommendation Draft. Browser support differs, so web AR is built with a component such as model-viewer that falls back to Scene Viewer on Android and AR Quick Look on iPhone.
Who owns the models, code and store listings after launch?
You do. The source code, the master 3D models and their exports, the content service and the analytics setup are assigned to you, and the apps are published under your own Apple and Google developer accounts. That keeps you free to change teams later without rebuilding the asset library or losing your reviews and rankings in the stores.

Planning an AR feature or app?Tell us the product, the decision AR should help people make and the devices your users carry; we reply with a platform recommendation and a prototype plan.

Get an AR proposal

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.
Contact Us