Industry guide · 12 min read ·
AR and VR app development for real products
Before you brief a AR app development company, it helps to know which parts of a AR or VR app are genuinely hard. This guide covers the market reality, the feature set that is table stakes, the three engineering problems that decide whether the product survives contact with real users, the compliance load, the numbers to measure, and what the work costs.
The market reality
Most AR projects fail because they were a demo looking for a job. The ones that work replace a measurable cost: returns from wrong-size purchases, an on-site technician visit, or classroom time for a dangerous procedure.
Everything below follows from that. If a proposal you receive does not address it directly, the team has priced the screens and ignored the product.
The feature set that is table stakes
None of this differentiates you. All of it is required before anyone will take the product seriously, so it belongs in the v1 budget rather than the phase-two wish list.
- Plane and object detection tuned for the real environment
- Accurate scale and occlusion so the illusion survives movement
- Graceful fallback to 2D when tracking fails or hardware is unsupported
- Asset pipeline with LODs and compressed textures
- Capture and share, because AR spreads socially
- Session analytics that show where tracking is lost
The three problems that actually decide the outcome
Environments are hostile — Reflective floors, low light, featureless walls and glass all break tracking. Test in the actual stores, warehouses or homes where the app will be used, not in a well-lit studio.
Asset pipelines are half the project — Converting product CAD or scanned models into mobile-ready assets at acceptable quality and file size is ongoing operational work, not a one-off task. Budget for it as a pipeline with owners.
Comfort and safety in VR — Frame-rate floors, locomotion choices, session length guidance and clear boundary handling are not optional. Discomfort ends adoption instantly and permanently.
Compliance and risk
Camera and spatial data are sensitive: be explicit about what leaves the device. Accessibility alternatives are required for anyone who cannot use the AR path, and workplace deployments may need safety sign-off.
Schedule compliance work in parallel with the build, not after it. Every team that treats it as a launch-week gate misses their date, and the fixes are architectural rather than cosmetic.
The numbers that matter after launch
Instrument these before you ship. A AR or VR app without measurement is a guess with a release cycle.
- Return-rate change for products with AR try-on
- AR session completion versus abandonment
- Tracking loss events per session
- Task time saved versus the non-AR baseline
- Share rate of AR captures
What it costs and how long it takes
A focused AR feature inside an existing app typically runs $45,000 to $120,000. Standalone VR training products start higher because content production dominates.
A realistic timeline is two to three weeks of discovery, three to five weeks establishing design and core flows, then eight to fourteen weeks of build and QA before a production launch. Parallelising design and engineering after the first flows are settled is what keeps that schedule honest.
Recommended stack
ARKit and ARCore natively, or Unity when the content pipeline and cross-headset reach justify it. Choose based on where the assets and the team already live.
The right answer depends on your roadmap, not on what a vendor staffs most easily. Ask any firm to justify its recommendation against the specific hard problems above.
Choosing a AR app development company
Ask for a shipped product in this category that you can install today. Ask which named engineers will work on yours. Ask how they handled the three hard problems above on that project, specifically. Then ask what they would do differently now.
WVE Labs is a digital product company founded in 2015. Product strategy, design and engineering sit under one roof, and mobile has been at the heart of the studio for more than a decade — it remains one of our deepest areas of expertise. We have delivered for startups, growth companies and established organisations including Sony, Honda, Guardian, Marriott, USC, Maui Jim and California State University. Engagements start at $25,000.
- A live, installable product in this category
- Named senior engineers, available before contract
- A specific answer to each hard problem above
- Weekly demos on a working build, not status decks
- Full ownership of code, cloud accounts and store listings
The takeaway
The difference between a AR or VR app that works and one that quietly dies is almost never the interface. It is dispatch logic, data pipelines, offline behaviour, compliance and measurement — so brief for those, and hire the team that talks about them unprompted.