AR & WebAR
Put digital content where it helps someone decide.
A product in a room, an exhibit with context, an object that starts a story. We build scoped augmented-reality experiences around a useful action, the devices people actually have and a clear route when AR is unavailable.
DIRECT ANSWER
Augmented reality development places interactive digital content in a camera view of the real world. Wavect scopes phone and browser experiences with defined placement behavior, permissions, supported devices and a useful alternative without AR.
Best for
- Product previews or visitor experiences with a clear real-world context
- Teams adding a bounded AR interaction to a website or mobile app
Consider another approach
- A product viewer that only needs rotation and variant selection
- A headset experience with spatial hands or controllers
Choose the route before building the scene
Start with where people discover the experience: a product page, QR code, NFC tag or an installed app. Compare a simple platform viewer, an interactive browser experience and a native feature against the required actions. WebXR has browser and permission requirements; WebAR does not behave identically everywhere. For an existing app, Mobile Apps owns the surrounding navigation, account and release work.
Make placement understandable and recoverable
Define the surface or image target, expected object dimensions, repositioning and instructions when tracking becomes unreliable. Plain or reflective surroundings need an explicit trial in the intended setting; ARCore documents limitations in surface detection. Decide whether to hide, freeze or re-place content when tracking is lost. Persistent placement across visits and shared placement across devices are separate requirements, not assumptions attached to an AR label.
Keep the asset and the product information aligned
Agree model scale, orientation, material appearance, download size and the number of objects visible together. Link the displayed model to the correct product or content version. 3D Modelling covers asset creation and preparation. If camera placement adds little, an interactive 3D viewer can support inspection and configuration directly. Product dimensions should remain readable as text; visual placement is an aid to understanding the object.
Illustrative acceptance: place a product, then return to it
A visitor opens a lamp preview from its product page. On an agreed device, the lamp appears at the specified scale and can be placed again. After the camera is interrupted, the interface explains how to resume rather than leaving an unexplained floating object. Denied camera access or unsupported AR leads to the model, dimensions and product information without a dead end. The selected lamp remains consistent throughout. This is a proposed acceptance exercise, not a customer result.
Keep published entry points useful as content changes
An AR entry link can remain on a printed label after a campaign changes. Agree who can publish content, what needs approval and where visitors go when an item is retired. Prepare a previewable release that keeps the model, instructions and destination together, with a way to restore the previous version. Changing a QR destination should not silently send visitors to a different product.
Test the full visit on the target devices
Acceptance names the phones, operating systems, browsers, lighting conditions and network assumptions to test. We cover permission denial, slow assets, interruptions and the return to the original page. Agree whether any images or spatial data are stored, and who owns hosting and updates. Handover includes source, approved assets, the device matrix, fallback behavior and instructions for replacing content without breaking placement.
Questions before you start
No. A browser or platform viewer may cover the intended interaction. We compare that route with an app when device features, offline behavior or deeper integration justify installation.
We agree a tested device and browser matrix. Scene Viewer and Apple Quick Look offer different platform routes. Unsupported combinations need an ordinary product or 3D view.
No. Bring the source material and usage rights you have. We assess whether existing models can be adapted or whether new assets are needed, with that work priced and accepted explicitly.
Headset passthrough, spatial input and room-scale sessions belong to VR & XR Development. This page focuses on phone and browser journeys; the two can share approved assets.
Yes. Choose one action, one representative asset and a defined device set. The pilot should resolve a specific question about usefulness, tracking or delivery before adding more content.
Scope your AR experience
Tell us what someone should see or do in their surroundings. Include the intended devices, entry point, available 3D assets and the setting where the experience will be used.