AR for Marketing & Sales · 7 min read
The Augmented Reality Development Process in Indonesia: A Buyer's Guide
Most businesses that search for "jasa pembuatan augmented reality" or an AR agency in Indonesia have never commissioned one before, so a vendor's quote is hard to judge on its own. This guide breaks down what an augmented reality project actually involves — the stages, the realistic timeline, the cost drivers, and the questions worth asking before signing anything.
If you've been quoted anywhere from a few million rupiah to the equivalent of tens of thousands of US dollars for what sounds like the same thing — "an AR experience for our brand" — the spread usually isn't a scam on one end or a bargain on the other. It almost always means the two vendors scoped completely different projects. This guide walks through what actually happens during an augmented reality build, so a proposal is easier to evaluate on its merits.
What does "jasa pembuatan augmented reality" actually cover?
The phrase covers a wide range of work: a browser-based WebAR filter that runs from a QR code, a native AR app published to the App Store and Google Play, an AR product viewer embedded on an e-commerce page, or an AR marker that triggers a video overlay on packaging. Each of these is a different build with a different team, timeline and SDK — which is why "how much does AR cost" has no single answer until the scope is defined.
How long does an augmented reality project actually take?
A single browser-based WebAR experience with one 3D model typically takes two to four weeks from kickoff to a live link. A multi-feature AR app with several scenes, tracking types or a catalog of products usually runs eight to sixteen weeks. An enterprise build with custom object recognition, spatial mapping or integration into an existing app can take four to six months or longer. Vendors who quote a firm delivery date before seeing your assets or confirming the platform are usually guessing.
Industry process guides generally break the work into the same sequence regardless of project size: requirements and scope, choosing the technical approach, 3D asset creation, development and SDK integration, device testing, and launch. CodeIT's development guide lays out this sequence in nine concrete steps, from defining the product vision through app store or server release, and is a useful reference if you want to see how much detail a competent proposal should cover.
What are the main stages of an AR build?
- Discovery and scope. What the AR experience needs to do, on what devices, and for which audience. This is where a vendor should be asking you questions, not just listing deliverables.
- Choosing WebAR vs. a native app. WebAR runs in the phone's browser with no install; a native app can do more (persistent tracking, offline use) but costs more and takes longer to approve and update.
- 3D asset creation. Models, textures and animations, either built from scratch or converted from existing CAD/product files. This is frequently the most time-consuming part of the project, not the coding.
- SDK and platform selection. Tools like Google ARCore, Apple ARKit, Vuforia or 8th Wall are chosen based on tracking type (marker-based, markerless, location-based) and target devices.
- Development and integration. The actual build, plus connecting it to a website, app or e-commerce listing.
- Testing across devices. AR tracking behaves differently across phone models, camera quality and lighting conditions — this stage catches what a single-device demo misses.
- Launch and handover. Deployment, plus documentation on who can update the content afterward.
WebAR or a native app — which does your project actually need?
Most marketing, retail and sales use cases in Indonesia — product visualization, packaging activations, showroom experiences, trade booth demos — are well served by WebAR: a shopper scans a QR code or taps a link and the AR view opens immediately in Chrome or Safari, with nothing to download. A native app is worth the extra cost and timeline mainly when the experience needs to work reliably offline, needs deep device integration, or is itself the product (a training simulator, for example, rather than a marketing tool).
How much should augmented reality cost?
Published international pricing guides give a sense of the range, though none of these figures are Indonesia-specific or an InReality quote — use them to sanity-check a proposal, not as a price list. CodeIT's development guide puts a simple demo AR application at around $10,000, scaling to over $300,000 for a complex, fully custom build. DesignRush's 2026 AR pricing guide breaks this down further: simple marker-based AR for a small business at roughly $5,000–$15,000, and complex markerless AR with real-time object recognition or 3D mapping for larger deployments at $50,000–$250,000 or more, with 3D modeling alone often running $5,000–$30,000 depending on detail and animation. Object recognition and gesture-control features are typically quoted separately, in the $10,000–$50,000 range, because they require their own testing pass.
The figure that matters for your project isn't the industry range — it's which end of it your scope sits on. A single-product WebAR viewer for one campaign and a multi-SKU AR catalog with custom tracking are not the same order of cost, even though both are "augmented reality." For a project-specific estimate against InReality's own packages, see our pricing page or get in touch directly.
What should you ask before hiring an AR vendor?
- Can I see a live demo, not just a video or mockup? A real AR experience running on your own phone, in your own lighting, tells you more than a highlight reel.
- Which SDK will you use, and why? The answer should match your use case (marker-based for packaging, markerless for space visualization, location-based for venue experiences) — a vague answer is a signal the vendor hasn't scoped the technical approach yet.
- Who builds the 3D assets — in-house or outsourced? This affects both quality control and timeline, since asset creation is usually the longest stage.
- How many devices and OS versions will this be tested on? AR tracking quality varies a lot by phone camera and processor; a vendor who tests on one flagship device only is not testing for your actual audience.
- Who owns the assets and code after launch, and what does updating the content later cost? Get this in writing before the project starts, not after.
Red flags worth watching for
A fixed quote given before any discovery conversation, a portfolio made entirely of mockups or renders rather than screen recordings of working experiences, and vague answers about which SDK or AR type the project will use are the three most common signs that a proposal was written to win the deal rather than to describe the actual work. A credible vendor will usually want to understand your audience and devices before naming a number.
If you're further along and ready to scope a specific project — a WebAR product viewer, a packaging activation or a sales demo tool — InReality Solutions builds AR for sales and marketing and AR for e-commerce for brands across Indonesia, including the Jakarta-based AR production work described on our services page. Our portfolio shows recorded examples rather than renders, for exactly the reason above.
Frequently Asked Questions
Does augmented reality always require downloading an app?
No. WebAR runs directly inside a phone's existing browser (Chrome or Safari) — the user taps a link or scans a QR code and the AR view opens immediately. A native app is only needed for use cases that require offline access or deep device integration.
How much does it cost to build an AR experience?
Published industry ranges run from roughly $5,000 for a simple marker-based AR experience to $250,000 or more for a complex markerless build with custom object recognition. These are general international figures, not an Indonesia-specific or InReality quote — the right number depends entirely on scope.
How long should I budget for an AR project?
A single WebAR experience typically takes two to four weeks. A multi-feature AR app usually takes eight to sixteen weeks. An enterprise build with custom tracking can take four to six months or longer, depending on asset complexity and testing requirements.
What's the difference between WebAR and a native AR app?
WebAR runs in a mobile browser with no install and is faster and cheaper to build and update; a native app can support offline use and deeper device features but costs more, takes longer, and requires app store approval for updates.
Who owns the 3D assets and code after the project ends?
This should be written into the contract before work begins, not assumed. Ask specifically about ownership of 3D models, source code and any proprietary tracking configuration, and what it costs to update the content later.
Founder & Managing Director · LinkedIn
Ready to Build Your New Reality?
Tell us about your brand and goals — we'll show you what's possible.