Construction AR Mobile Application Development
A BIM model weighs 800 MB and lives in Autodesk Revit on a workstation. A site supervisor looks at a tablet, trying to match the blueprint with what stands before them. AR closes this gap: properly implemented IFC model anchoring to real space reveals wiring inside walls before plastering. Incorrectly—drift accumulates in 10 seconds, and rebar "drifts" half a meter from its actual location.
Main Technical Challenge: Positioning Accuracy
Unlike retail, where 5 cm error is acceptable, construction demands 2–3 cm precision. ARKit and ARCore provide visual odometry accurate to 5–15 mm over short distances in good lighting—acceptable. But construction sites complicate matters:
Monochrome surfaces. Concrete floor without texture, white walls—feature points have nothing to anchor to. ARKit loses tracking and resets session. Solution: forced initialization via QR markers (ARImageTrackingConfiguration) or ArUco markers attached to structural elements with known coordinates. Marker carries ID → app pulls coordinates from BIM → world origin set with marker precision.
LiDAR as requirement. For construction applications, recommend iPad Pro 2021+ or iPhone 12 Pro+. ARWorldTrackingConfiguration with sceneReconstruction: .meshWithClassification builds mesh of real space—allows collision checking of BIM models with physical objects (wall offset 8 cm from project) and correct AR rendering.
Drift over movement. Over 500+ sq. m, visual odometry accumulates error. Integrate geodetic data via GPS (outdoor) or UWB beacons (indoor, 10–30 cm accuracy) for periodic world anchor correction.
Working with BIM Content
IFC models don't load directly in ARKit. Conversion pipeline:
-
IFC → glTF/USDZ via
ifcconvert(IfcOpenShell) or Autodesk Forge API - Geometry simplification: complete Revit model is unviable on mobile. Build LOD system server-side: by distance to object, deliver varying detail models
- Streaming: don't load entire floor at once, load by sectors via
ARGeoAnchoror custom coordinate grid
On iOS use RealityKit with ModelEntity for rendering, on Android—ARCore + Filament renderer. BIM layers (structure, utilities, finishes) toggle as visibility switches in UI.
Additional Scenarios
Quality control. Camera scans finished element, algorithm compares to BIM—deviation map overlaid on AR image. Use ARMeshAnchor + point cloud comparison.
Defect documentation. Photo with AR markup anchors to specific BIM point via world anchor—on next visit, defect auto-locates.
Project Workflow
Audit client's BIM pipeline → design UX for field conditions (gloves, sun, screen dirt) → develop IFC converter → AR module with marker initialization → integrate with project system (Autodesk ACC, Procore or custom backend) → field testing on real site → support.
Timeline: pilot module with basic BIM overlay—6–10 weeks. Full system with QC functions, offline mode, and project platform sync—4–7 months. Cost individual.