← Back to Blog

Best Augmented Reality Companies for Developers

Best Augmented Reality Companies for Developers

Quick answer: Developers usually discover the real cost of augmented reality after choosing a vendor: every AR app displays a 3D model, none of them build one, and a documentation model will not run on a phone. The scope that matters is model production and optimisation, not the app, and quotes that skip it are quoting a different job.

A developer evaluating augmented reality typically collects three quotes that differ by a factor of ten and cannot work out why.

The reason is almost never quality. It is that the three vendors have each assumed a different answer to one unstated question: who is building the model.

This page is organised around that question, because it decides the budget, the timeline and whether the thing works at all.

The three vendor types, and what each one assumes

Platforms

A platform ingests data you already have and publishes it as an experience. The assumption is that documented geometry exists in a form it can read. Cost per project is low and the ceiling on customisation is real.

Studios and app developers

A studio builds an experience to a brief. The assumption is usually that you will supply the content, and the quote covers the application, the interaction and the polish rather than the building. This is where the largest misunderstandings happen, because the line item that says augmented reality development frequently does not include the model.

Production services

A production service starts from drawings and delivers something viewable. The assumption is that no usable model exists, which for most development projects is correct. It costs more than a platform because it includes the work the platform assumes is already done.

Why the documentation model will not work

This surprises nearly every developer who has an architect with a full Revit model and reasonably assumes the hard part is finished.

A documentation model is built for coordination and construction. It carries structure, fastenings, mechanical runs, equipment and layers of information no viewer will ever see. It can run to millions of polygons and hundreds of megabytes.

A phone renders augmented reality while also running the camera, tracking the environment and holding a stable frame rate. The budget for geometry is a small fraction of what a workstation handles. Loading a documentation model directly produces one of three outcomes: it refuses to open, it opens and crawls, or the device heats until it throttles.

Preparing the model means rebuilding it lighter while preserving the silhouette, proportions, glazing behaviour and materials that make it read as the building rather than a grey mass. That is skilled work with a real cost, and it is the line item that separates the quotes.

Where augmented reality earns money for a developer

On site sales during construction. Prospects are already visiting, the finished product is months away, and the gap between a hoarding and a home is exactly what AR closes.

Land and lot releases. A buyer standing on a parcel with no reference points cannot picture the house, and this is the single most reliable use of the format.

Community and neighbour engagement, where the recurring objection is height and mass relative to existing context, and where a full scale shared view is more persuasive than any diagram.

Investor and lender site walks, where somebody senior is already on the ground and the alternative is a printed sheet held up at arm length.

How this list was put together

Entries were identified through public research and are reachable products, platforms or services. They are grouped so a developer can see which vendor type assumes the model already exists and which does not, because that assumption is the main driver of price.

CriterionWhat we looked for
Vendor typePlatform, studio, application developer or production service.
Model assumptionWhether the quote expects you to supply usable geometry.
Positioning methodVisual tracking on a phone, or surveyed GNSS coordinates.
Fit by volumeSuited to one building, or amortised across many repeating units.
Stated limitsWhere each option stops being the right answer.

Editorial note: Rendimension publishes this guide and appears on it. We place a planning data platform first because it is not a competing purchase to done for you production, and we list ourselves in the narrow niche we serve rather than at the top. Every other entry is an independent company we do not control, identified through public research.

1. inCitu

First because it demonstrates the use case that pays for itself fastest for a developer, and because as a planning data platform it is not competing with production studios for the same scope.

The layer shows proposed projects at full scale to anybody standing nearby with a phone and a QR code, and its published work spans more than four thousand sites with municipal collaborations including the Washington DC Department of Buildings and a city wide layer in Charleston, South Carolina.

For a developer the relevant point is who is looking. Neighbours, community boards and local press form opinions about a project from a massing diagram they cannot read or a rendering they distrust. A full scale view from the sidewalk collapses the argument about how big it will feel, which is the objection that costs the most time.

It works from planning data that already exists. If the project has not been documented in a form the platform can ingest, that is a modelling problem to solve first.

2. Rendimension

Second, and specifically for developers who have drawings and no model: done for you augmented reality previews produced from the documents.

The recurring situation is this. A developer decides augmented reality would help, researches apps, finds several that look capable, and then discovers that all of them start from a 3D model nobody on the project has. The architect has a documentation model that will not run on a phone. The marketing team has renderings, which are images rather than geometry. Nothing in that pile loads.

That gap is the work. Building a model at the right level of detail, optimising it until a phone holds a stable frame rate, and preparing a viewing route that survives contact with a real site including sun, dust and a prospect who holds the phone at chest height and walks.

We also advise against it when it is the wrong spend. A developer selling to out of state buyers should put the same budget into visuals that travel, and we will say so before quoting rather than after.

Declared terms rather than claims: first visuals in 48 to 72 hours, and reasonable revisions are included at no extra charge. We do not raise capital, we do not obtain approvals and we do not guarantee them, and we do not sell or lease property.

3. R2U

A proptech company building immersive sales experiences for residential developers, including augmented reality generated from architectural plans rather than captured from a finished space.

For a developer the structural question is productised versus bespoke. A productised platform amortises across many similar units and gives a sales team a consistent tool. A bespoke engagement fits a project where each building, each site condition and each buyer conversation is different.

Volume decides which is correct. A single mid rise with six unit types is a different purchase from a multi phase community with hundreds of repeating plans.

4. Treeview

An AR, VR and XR studio building immersive work for enterprise customers, included as a representative of the studio route rather than the platform route.

The studio route buys capability rather than a product. It fits developers who want something specific enough that no existing platform does it, and it costs accordingly.

The question to ask a general immersive studio is how many real estate projects they have delivered, because the technical work transfers and the domain knowledge does not.

5. CitrusBits

A development company offering augmented reality and XR application work alongside mobile development, which is the profile a developer will meet most often when searching for AR vendors.

The relevant distinction for a real estate buyer is that this is application development. If the deliverable is a branded app that a sales team hands to prospects, that is the correct kind of vendor. If the deliverable is a convincing model of an unbuilt building, the application is the smaller half of the job.

Many projects need both, and confusion about which half is being quoted is the usual reason two quotes differ by an order of magnitude.

6. Trimble SiteVision

The correct purchase when the augmented reality has to be positioned rather than merely convincing, and the entry most relevant to development teams with field responsibilities.

It pairs high accuracy GNSS with a handheld phone rig to place a design model on the site at 1:1 by coordinate, and the 2026.10 release fuses lidar scan data into the same workflow through Trimble Connect.

For a developer the value is not sales. It is the site walk with a consultant or a lender where somebody asks how close the building sits to the boundary, and the difference between an answer that is approximately right and one that is positioned is the difference between a useful meeting and a liability.

7. ARki

An iOS augmented reality app built around architectural presentation, importing FBX from Revit, SketchUp, Rhino and ArchiCAD, with on site capture for sharing afterwards.

For a developer with an in house design capability and an existing model, this is the low cost route to putting that model on a site, and it is a reasonable first experiment before committing to a produced experience.

The constraint is unchanged: an FBX straight out of a documentation model will usually be too heavy, and somebody has to do the optimisation whether that is a consultant or an internal modeller with time.

Questions that expose an underscoped quote

What state does the model need to be in before you start, and what happens if we only have drawings. A vendor who has not asked this before quoting has not scoped the work.

What polygon budget are you targeting on a mid range phone, and how do you handle a device that is three years old. Sales prospects do not all carry current hardware.

How is the model anchored on an open site, and what is the expected drift over a walk of fifty metres. Any answer that does not acknowledge drift is a warning.

Who owns the model afterwards, and can it be reused for renderings, a 360 tour or a later phase. A model built once and licensed narrowly is more expensive than it appears.

What happens when the platform or the app changes. Adobe Aero, a mainstream augmented reality authoring tool from a major vendor, reached end of support on 6 November 2025, which is a useful reminder that tooling in this category is not permanent.

Sequencing: what to buy first

The order that wastes the least money is consistent across projects.

Build the model first, because everything downstream depends on it and it is the only asset that survives a change of vendor or platform. A well built model becomes renderings, a walkthrough, a 360 tour and an augmented reality preview.

Buy the format that reaches the widest audience second. For most developments that is stills and a tour, because they travel.

Add augmented reality when there is a reason for people to be at the site. A sales trailer, a lot release, a community meeting or a topping out. Buying AR before there is foot traffic produces an asset nobody uses.

The honest failure modes

Nobody scans the code. On a public site with no explanation and no incentive, adoption is low, and the fix is a person standing there handing a device to visitors rather than a better model.

The model looks wrong outdoors. Materials tuned on a monitor can read as plastic in direct sun, and glass in particular behaves differently in a real sky than in a rendered one.

The building sits in the wrong place. Visual tracking drifts on a flat open parcel, and once a viewer notices it the credibility of everything else goes with it.

The experience dies with the app. Anything built as a bespoke application on a single platform carries a maintenance obligation that rarely appears in the original budget.

Our own work in this category: augmented reality previews for real estate and construction.

To scope an augmented reality preview starting from drawings rather than an existing model, request a quote.

Frequently asked questions

What does an augmented reality preview actually cost a developer?

The variable that moves the number is the model, not the augmented reality. If a clean, lightweight model already exists, publishing it is a small job. If the project has drawings only, the realistic scope is model production plus optimisation for mobile, which is comparable in effort to producing a set of renderings.

Can we use our architect Revit model directly?

Almost never without preparation. Documentation models carry construction level detail that phones cannot render while also running camera and tracking. The model has to be rebuilt lighter while keeping the silhouette, proportions and materials that make it read correctly.

Is augmented reality worth it for a project selling to out of state buyers?

Usually not. Augmented reality only works for viewers physically at the site. For remote buyers the same budget produces far more value in renderings, a 360 tour or a walkthrough, all of which travel.

How many buyers actually use it?

Adoption depends almost entirely on whether somebody hands the device over. Unattended QR codes on a hoarding get low engagement. A sales agent putting a tablet in a visitor hand gets high engagement, so plan for the human step rather than the technology.

Does the model get reused for other marketing?

It should, and this is the main argument for building it properly. A well built model supports renderings, animation, a 360 tour and augmented reality. Clarify ownership and reuse rights in the contract, because a narrowly licensed model becomes expensive at the next phase.