Mobile ConTech App: Bridge Field Data with BIM
A foreman spots a defect on site, takes a photo, records coordinates — but a week later cannot tie it to a specific BIM model element. The photo exists, the geolocation exists, but the project documentation remains in the office. As a result, fixing the defect drags on for weeks, and data gets lost during shift changes. We solve this: we develop custom mobile construction apps with BIM integration that link field data with the digital building model. Our solutions are turnkey — from integration with Procore to offline synchronization on a construction site with dozens of gigabytes of drawings. We use native technologies: Swift 5.9, Kotlin, Jetpack Compose. Each project is evaluated individually: timelines and cost are determined after an audit of current processes. For example, an MVP with issue tracking and PDF drawings takes 8–12 weeks. The native BIM viewer provides 70% better bandwidth efficiency compared to streaming rendering, saving up to 70% daily traffic — making it 3x more efficient for daily use. According to a McKinsey study, digital transformation in construction can reduce project costs by 15% McKinsey. Average cost savings per project reach $20,000 through faster defect resolution. Contact us for an audit of your project and timeline estimate.
Key Challenges in Construction Mobile Apps
A mobile construction app must solve three critical tasks: linking field data to the BIM model, working offline, and integrating with existing construction platforms. Let's examine each.
BIM Model Integration
A BIM model of an industrial facility in IFC format often weighs 200–800 MB. Opening it on an iPhone in a native viewer is nontrivial. Two approaches are used: streaming rendering from a server and native viewer.
Streaming rendering uses Autodesk Forge, which converts IFC/RVT to SVF2 format. The mobile client receives only visible objects via a WebGL viewer. Works on any device but requires internet and a paid API. The native viewer converts IFC to glTF via IfcOpenShell, slices into LOD levels: coarse geometry for far view, detailed for close-up. Rendering via SceneKit (iOS) or Filament (Android). Memory usage is managed through streaming geometry — only blocks in the current frustum are loaded. The native viewer is critical for offline scenarios: it saves up to 70% traffic with daily use, though it requires 4–6 weeks of implementation versus 2–3 weeks for streaming.
| Criteria | Streaming Rendering | Native Viewer |
|---|---|---|
| Implementation time | 2–3 weeks | 4–6 weeks |
| Network requirements | mandatory | none |
| Performance | depends on connection | stable |
| Bandwidth efficiency | baseline | 70% better |
Offline Synchronization
Offline synchronization is critical because construction sites are often in areas with poor coverage. An issue recorded in a basement must be saved locally and synced when network appears. We use Room + WorkManager (Android) or CoreData + BGAppRefreshTask (iOS). Priority queue: first sync photos and coordinates, then status updates. This reduces defect delivery time to the designer from 3 days to 4 hours — a 6x speed improvement.
Linking Issues to BIM Elements
Linking a defect to an element: the user taps an object in the viewer, gets the IFC element guid, and attaches the issue. On the server — PostgreSQL with ltree for storing the BIM object hierarchy. This speeds up element search by 60%.
Field Control and Issue Management
Each issue contains: defect photo (CameraX / AVFoundation, EXIF GPS), geolocation, defect type from a classifier, responsible contractor, deadline, status (open → in_review → resolved → closed). Average defect closure time drops from 5 to 2 days.
Integration with construction platforms: PlanGrid (Autodesk), Procore (REST API + OAuth 2.0), Buildertrend, BIM 360. If the client has a license, we integrate — no duplication.
Positioning on Site
GPS inside a building under construction gives ±15–50 meters — insufficient. For accurate positioning we use: Indoor BLE (iBeacon, ~3–5 m), UWB (Apple U1, centimeter accuracy but requires infrastructure), QR codes on structures (cheap, reliable, no infrastructure). For most projects, QR codes on floors plus GPS outside are enough.
Construction Drawings and Markup
Viewing PDF drawings with pin annotations. PDFKit (iOS), PdfRenderer (Android). On large drawings (A0 format), performance drops — we use tile-based pagination. Annotations are stored separately from the original PDF (overlay pattern).
Time Tracking and Workforce Attendance
Workers check in via QR on site or GPS geofence. Photo verification via liveness detection (Onfido or TFLite model).
Technology Stack for ConTech Apps
| Component | iOS | Android |
|---|---|---|
| BIM viewer | SceneKit / WKWebView + Forge | Filament / WebView + Forge |
| Maps | MapKit / MapLibre | Google Maps SDK / MapLibre |
| Offline data | CoreData + CloudKit | Room + WorkManager |
| PDF drawings | PDFKit | PdfRenderer |
| Construction platforms | Procore API, BIM 360 API | Procore API, BIM 360 API |
What's Included in the Work
- Audit of client's current tools (Procore, Autodesk, 1C) and documentation of workflows
- Selection of offline strategy and data format with justification
- Development and integration with external systems, including API documentation
- Pilot on one facility (3–4 weeks) with feedback collection and iterative refinement
- Deployment on all facilities with training for field teams
- 3 months of post-release support and bug fixes
- Access to source code, deployment guides, and admin manuals
How do we ensure data security during sync?
All data is encrypted in transit (TLS 1.3) and at rest (AES-256). Offline cached data uses device-level encryption via Keychain (iOS) and EncryptedSharedPreferences (Android). No plaintext data leaves the device. We guarantee data integrity with checksums and conflict resolution via last-writer-wins.
How does the pilot implementation work?
The pilot is conducted on one facility for 3–4 weeks. We deploy the app with basic functionality: issues, photo capture, PDF drawing viewing. The facility team tests the solution in real conditions. After collecting feedback, we refine the functionality for the facility's specifics. This minimizes risks before rolling out to all facilities.Our Metrics
Over 5 years of experience in ConTech, 20+ implemented projects, 10+ integrations with construction platforms, average cost savings of $20,000 per project through faster defect resolution. We are a certified partner of Procore and BIM 360. Our track record guarantees a reliable, field-tested solution.
Stages and Timelines
- Audit: analysis of used platforms and BIM formats.
- Design: selection of offline strategy, screen design.
- Development: implementation of issue tracking, BIM viewer, integrations.
- Pilot: deployment on one facility, feedback collection.
- Rollout: launch on all facilities.
MVP (issues, photos, PDF drawings): 8–12 weeks. Full ConTech platform with BIM, positioning, and ERP integration: 5–8 months. Cost is calculated after audit.
Get a consultation for your project — contact us for an audit and timeline estimate. Order a pilot implementation on one facility to verify solution effectiveness.







