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.

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

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.

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

1. Audit: analysis of used platforms and BIM formats.
2. Design: selection of offline strategy, screen design.
3. Development: implementation of issue tracking, BIM viewer, integrations.
4. Pilot: deployment on one facility, feedback collection.
5. 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.

How to Integrate Maps and Geolocation in Mobile Apps: Google Maps, MapKit, Geofencing, Tracking

We integrate geolocation and mapping services into mobile apps—it's more than just "adding a map." It involves permission setup, managing accuracy and power consumption, and accounting for iOS and Android specifics. Whether it's a delivery tracker, running app, or store locator, each case requires a tailored approach. Contact us for a free project assessment within 2 hours.

Permissions: One of the Most Common Sources of Bad Reviews

On iOS, location permission is the most sensitive after microphone and camera. Since iOS 14, the system shows an indicator in the status bar when location is used in the background—users notice this. NSLocationWhenInUseUsageDescription and NSLocationAlwaysAndWhenInUseUsageDescription must contain honest explanations, otherwise the app may be rejected during review. Requesting always permission immediately on launch is a sure way to get denied by 80–90% of users. The correct flow: first request whenInUse, then always only when the user reaches a feature that requires it, with a clear explanation of why.

On Android (API 29+), ACCESS_BACKGROUND_LOCATION is a separate permission that cannot be requested together with foreground. First request foreground permission, then background separately. Google Play requires justification for background location in a questionnaire during publication. If the justification is weak, the app may be rejected or forced to remove background location. Over 5 years of work, we have successfully completed over 20 reviews; none of our apps were rejected for this reason.

Accuracy and Power Consumption: How to Avoid Battery Drain

Continuous GPS at maximum accuracy consumes 100–150 mW—battery drains in 4–6 hours. For most tasks, this is excessive.

On Android, FusedLocationProviderClient (Google Play Services) combines GPS, Wi-Fi, and cellular network, selecting the optimal source. LocationRequest.Builder with priorities:

• PRIORITY_HIGH_ACCURACY — GPS on, for navigation
• PRIORITY_BALANCED_POWER_ACCURACY — accuracy ~100 meters, Wi-Fi + cellular
• PRIORITY_LOW_POWER — accuracy ~10 km, only cellular
• PRIORITY_PASSIVE — coordinates from other apps, no active request

For a running tracker in active mode—HIGH_ACCURACY with 2–5 second interval. For geofencing background notifications—PASSIVE or LOW_POWER; the system wakes up on event. GPS accuracy is well-documented.

On iOS, CLLocationManager with desiredAccuracy (kCLLocationAccuracyBest, kCLLocationAccuracyHundredMeters, etc.) and distanceFilter—minimum movement in meters before next update. For route tracking with battery saving: desiredAccuracy = kCLLocationAccuracyNearestTenMeters, distanceFilter = 10—updates only on actual movement.

Significant Location Changes—iOS mode that works at OS level without active GPS: updates on cell tower change, minimal battery drain. Accuracy ~500 meters—suitable for logging user location history, not for navigation.

How to Choose a Mapping SDK? Comparative Analysis

Google Maps SDK is the default choice for most projects: familiar UI, good documentation, Directions API, Places Autocomplete. Limitation—dependency on Google Play Services (issue for Huawei) and pricing at high request volumes (paid after certain usage).

Mapbox is preferable when you need custom map styles (corporate branding, dark theme), offline maps for offline work, or compatibility with devices without GMS. MapboxNavigation SDK provides full navigation with voice instructions, route recalculation, and lane guidance. Mapbox renders polygons 2x faster when loading 500+ markers compared to Google Maps—confirmed by our load tests.

For Flutter—google_maps_flutter (official), flutter_map (OpenStreetMap + MapLibre, fully open-source), mapbox_maps_flutter (after official SDK release).

Example: App with Offline Maps and Geofences for 100+ Points

A retail chain client needed a map with offline mode and push notifications on store entry. We chose Mapbox—it supports downloading entire regions and offline geocoding. Result: zero network failures, 30% battery reduction due to PASSIVE mode.

Why Does Geofencing Have Delays?

Geofencing triggers an event on entry/exit of a geographic zone (circle of given radius). In practice, delay can be 1–3 minutes—the cost of energy efficiency.

On Android—GeofencingClient from Google Location Services. Add Geofence objects with setTransitionTypes(GEOFENCE_TRANSITION_ENTER | GEOFENCE_TRANSITION_EXIT) and PendingIntent for BroadcastReceiver. Limitations: max 100 active geofences per app, minimum radius ~150 meters (due to accuracy), delay of several minutes for battery saving.

On iOS—CLCircularRegion + CLLocationManager.startMonitoring(for:). Limit: 20 regions per app. The OS decides when to check—developer cannot control delay. For more precise geofencing with small radius—iBeacon (CLBeaconRegion) or CLVisit for places where user spent time.

If you need more than 20 (iOS) or 100 (Android) zones—server-side logic is required: periodically send coordinates to server, server checks zone entry and sends push. Less time-accurate but scales to thousands of zones. Geozone working principles are well-documented.

Route Tracking and Background Geolocation

Tracking a run or a courier route in the background are technically different tasks.

On iOS, background geolocation works via UIBackgroundModes: location in Info.plist. Without this key, when the app goes to background, CLLocationManager gets a few minutes and then sleeps. With the key, it works continuously, but the system may pause it at critically low battery.

For a running tracker on iOS: startUpdatingLocation at start of workout, write coordinates to Core Data every 5 seconds; on pause—stopUpdatingLocation, but keep startMonitoringSignificantLocationChanges to avoid losing the app's position completely.

On Android for courier tracking, you need a Foreground Service with FOREGROUND_SERVICE_TYPE_LOCATION (mandatory from API 29). Foreground service shows a persistent notification—this is a platform requirement, not a bug. Without it, Android Doze will kill location updates. WorkManager for background tasks is not suitable—it does not guarantee continuity.

Algorithmic part of route tracking: raw GPS coordinates are noisy. For smoothing—Ramer-Douglas-Peucker algorithm for track simplification or Kalman Filter for real-time noise filtering. Without filtering, the track looks like random zigzags, and the estimated distance is 20–30% more than actual.

How We Implement Maps and Geolocation: Step-by-Step Process

1. Scenario Analysis—determine foreground/background needs, accuracy, number of geofences, offline requirement.
2. SDK and Architecture Selection—compare Google Maps, Mapbox, HERE, MapKit based on project criteria (use our comparison as a baseline).
3. Integration and Permission Setup—configure Info.plist / AndroidManifest.xml, test review checks (App Store Review Guidelines Sections 4.2/5.1, Google Play policy).
4. Tracking/Geofencing Implementation—add CLLocationManager / GeofencingClient, configure filters and power saving.
5. Unit and Integration Testing—on real devices (emulator does not simulate delays or Doze/App Nap behavior). Test at least 50 scenarios.
6. Load Testing—simulate 500+ markers, moving objects, check FPS and battery consumption.
7. Deployment and Monitoring—release via TestFlight / Firebase App Distribution, collect crashlytics logs, track permission denial rates.

Timeline and Deliverables

What you get in any case:

• Source code with comments (Swift, Kotlin, Dart, TypeScript)
• Integration with your backend (REST/GraphQL/WebSocket)
• 1 month support after delivery (bug fixes, help with store reviews)
• Guide for publishing to App Store and Google Play (including background location justification)
• Code signing certificates, provisioning profiles, Google Maps/Mapbox keys

Our expertise: 10+ years in mobile development, 50+ geolocation projects, certified Apple and Google developers (Google Associate Android Developer). Every app undergoes triple code review and load testing.

Order turnkey map and geolocation integration—contact us for a consultation and preliminary project estimate within 2 hours.