AR App for US and UK Brands: What an India Build Really Costs

You run a furniture or retail brand in the US or the UK. You have watched shoppers place a sofa in their living room before they buy, the way IKEA Place and Wayfair let them, and you want that for your own catalogue. Then the quote from a local studio arrived and gave you pause. So you are weighing a different route: an AR app built by a senior team in India. This post is the honest version of that decision, written by people who build these apps for global brands.

What does an AR app India build actually cost?

There is no single price, because scope sets the number. Appico publishes starting prices instead of a flat figure: a well scoped MVP from $10,000, a full mobile app from $12,000, and larger multi platform builds up to about $150,000, with upkeep on a monthly plan. Those are appico's own numbers. This post will not print competitor ranges, because they cannot be verified.

The rate gap between markets is the part brands ask about most. A senior engineer in India costs less per day than an equally senior engineer in New York or London. That is a cost of living and salary difference, not a skill discount. You are buying the same experience at a lower rate. Say that plainly to yourself, because the moment you start hunting for the cheapest quote instead of the right rate, the logic breaks. For a full module by module breakdown of where the money goes, see the guide on what an AR furniture app costs to build.

The figure above compares the three common routes without putting numbers on them, because your real number depends on your catalogue and your feature list. The pattern is consistent across the market: an in-house hire gives full control in your own time zone at the highest cost, a local agency gives easy meetings at top rates with AR skill that varies by studio, and a senior India team gives a lower rate with a few overlap hours a day, on the condition that you pick the right partner. If you want to sanity check your own scope, the project cost calculator gives a starting estimate before any call.

Why do US and UK brands go offshore for AR?

Brands go offshore for AR for three practical reasons: the rate is lower for the same seniority, AR specialists are easier to find in a larger engineering pool, and a fixed scope build removes the payroll risk of hiring full time for a project that may run a few months. The goal is not to spend less on skill. It is to spend the same skill budget on more of the build.

AR is a specialist field inside app development. You need people who understand ARKit on iPhone and ARCore on Android, how the camera reads a room, and how a 3D model behaves on a phone. Hiring one or two such people in house in the US or UK is slow and expensive, and you carry them between projects. A dedicated app development partner already has them on the bench. If you are still at the idea stage and unsure what to hand a team, the guide on how to turn an idea into an app is a good first read.

Appico's founder, Sahil Singh, puts the value simply: a senior team in India lets a global brand ship a real product without a New York salary line for every engineer. The catch he adds in the same breath is that this only works with senior people. A cheap team is not the same offer.

How do you work across a nine hour time gap?

You work across it with overlap hours and written updates. India runs roughly nine and a half to ten and a half hours ahead of US time zones and four and a half to five and a half ahead of the UK, so the two working days meet in your morning and the team's evening. You book calls in that window, and for everything else you rely on a short written update every day, so no decision waits a full cycle.

In practice the time gap is an advantage more often than a problem. You end your day with a clear list of what you need, the team works while you sleep, and you wake to progress. This only works if the writing is good. A daily note that says what was done, what is blocked, and what needs your call turns the gap into a second shift. A team that only wants to talk on calls, with nothing written down, will lose you a day every time a question comes up. Ask any partner to show you a real update from a live project before you sign.

Who owns the code, the repos and the accounts?

You should own all of it, from the first commit. At appico the source code, the git repositories, the app store accounts, the analytics and any cloud accounts sit in your name from day one, and an NDA is available on request. This is a fixed part of how appico works, not an upgrade you pay for. Get the same in writing from any partner before work starts.

The reason this matters is control. If a partner keeps the repository in their own account and promises to hand it over at the end, they are holding the one thing that lets you switch teams or hire in house later. The same is true of the Apple and Google developer accounts and the analytics: if they are in the partner's name, your users and your data are too. Ownership from day one is not a legal nicety. It is the difference between hiring a team and renting your own product back from them. Read the ownership and export terms as carefully as the price.

How do you keep AR quality high with an offshore team?

You keep quality high the same way any good AR team does, wherever it sits: senior engineers, a 3D model pipeline done correctly, and testing in real rooms before launch. Distance does not lower quality. Skipping these three steps does, and a cheap team skips all three. Quality in AR is decided by the models and the tracking, and both are engineering problems, not luck.

The 3D model pipeline is where most AR apps are won or lost

Every product in your catalogue needs an accurate 3D model, and the model has to work on a phone. That means sensible polygon budgets so it renders smoothly, compressed textures so it downloads fast, and export to the right format for each platform. Apple's AR Quick Look uses the USDZ format to let iPhone users place an object in their space, while Google's Scene Viewer uses glTF 2.0 and glb to do the same on ARCore Android devices. A serious team exports every model to both from the start. The full walkthrough of getting the 3D model pipeline right covers budgets, formats and compression in depth.

This is also the biggest cost driver. For a large catalogue, model work can be 40 to 50 percent of the whole budget, more than the app code. A quote that names a price without asking how many products you have has not thought about the models, which tells you what kind of build you are buying.

Tracking and mock scene testing before launch

Tracking is how firmly the app locks a virtual sofa to the real floor as the user walks around it. Good tracking feels solid. Bad tracking makes the object slide, sink into the carpet or float, and shoppers lose trust in a second. Getting it right needs testing in real rooms, on real phones, in bright light and dim light, on wooden floors and patterned rugs, before the app ships. A senior team builds mock scenes and runs this testing as a matter of course. The platform choices behind tracking are worth understanding too, covered in this comparison of ARKit and ARCore.

Use the table above in any first call. Ask each question, and listen for whether the answer is a real demo on your product or a general promise. The checklist below is the same idea as a printable list you can carry into every meeting.

The honest risks of choosing a cheap AR partner

The main risk is simple: a cheap AR build breaks on the two things that are hardest, model quality and tracking, and those are the two things the user notices first. A team that wins on price alone gets there by using junior developers, skipping the model pipeline, and skipping real device testing. The app demos fine on the one phone in the one room where it was built, then falls apart on a customer's floor.

Sahil's line on this is that launching is one percent of the journey. Getting an AR app into the store is the easy part. Keeping it working across hundreds of devices, adding products to the catalogue, and fixing the odd room where tracking drifts is the real job, and a cheap partner is gone by then. His other blunt point: cheap apps do not succeed, because the saving on day one is paid back many times over in a rebuild. The appico team has watched brands come back to redo a bargain build, and the rescue almost always costs more than doing it once properly would have.

There is a related trap with fast prototype tools. It is easy to get a rough AR demo working quickly, then assume production is a short step away. It is not. Turning a demo into a stable app is most of the work, a point covered in detail in taking a prototype to production. Judge a partner on whether they can carry the last ninety nine percent, not the flashy first one.

When an AR app India build is not the right call

An India build is not always the answer, and honesty here saves everyone money. If your catalogue is tiny, a handful of products, a full custom app may be more than the sales justify, and a simpler web based AR view of a few models could do the job. If your brand needs constant in person, same hour collaboration with the build team, the time gap will frustrate you, and a local team may be worth the higher rate.

AR also does not fix a weak product or a thin catalogue. It reduces returns and lifts confidence for products people struggle to picture at home, as explained in how AR furniture apps cut returns and boost sales. If your returns are already low and your customers buy without hesitation, the app may not pay for itself. And if you have not settled your scope, no team, near or far, can quote you a fair price. Decide what the app must do first. The wider decision of how to build a room planning experience sits in the pillar guide on how to build an app like IKEA Place.

How to choose the right partner

Choose on evidence, not on the lowest number. Ask every partner to show a real AR app they have shipped, running on a device, and then to demo a rough version on one of your own products. Confirm in writing that you own the code and accounts, that the scope and price are fixed, that models export to both USDZ and glTF, and that there is a support plan for after launch. Appico works on fixed scope, milestone based pricing, so you know the cost before the build starts, and you can compare that against any quote line by line. Two of the cluster guides above, on cost and on the model pipeline, give you the questions to ask.

Our take

Building an AR app in India is one of the better value decisions a US or UK brand can make, on one condition: you hire for seniority, not for the lowest bid. The rate gap is real and it is not a discount on skill, so a senior India team gives you an experienced AR build at a price a local hire cannot match, with the code and accounts in your name from day one. Spend the saving on getting the models and the tracking right, because that is where cheap AR apps die.

If you want to put that to the test, you can talk to our AR app development team and ask us to demo on your own products, or read the full cost breakdown before you do. Bring your catalogue and your hardest questions. A real partner should welcome them.

Frequently asked questions