i-Track: Taking REVIT Model Review Off the Workstation and Into the Field

Q: What is the difference between a REVIT plugin and a mobile BIM review app?

A REVIT plugin runs inside the Revit desktop application, typically automating or extending workflows for design and coordination teams. A mobile BIM review app uses cloud APIs like APS to serve model data to any device, enabling field review, issue reporting, and inspection without the Revit software. StudioKrew builds both, depending on where in the workflow the problem sits.

About the Platform

i-Track is a mobile and tablet application that enables AEC field teams to review REVIT models, raise geo-coded issues, and generate reports directly from any device, without needing a Revit-capable workstation.

Built on Autodesk Platform Services (APS) and Forge, i-Track processes REVIT models on the device, giving engineers, site managers, and QA teams the same model fidelity they expect on desktop, in the palm of their hand. The platform's standout capability is full offline operability: once a project is loaded, the team can work anywhere, with or without connectivity.

The Challenge REVIT models should travel with the team, not wait at a desk.

REVIT model reviews in construction and engineering projects have historically been tied to the workstation. A project manager, site engineer, or QA lead who needed to review a model, flag an issue, or log a comment had to be at a desktop with Revit installed and a machine powerful enough to run it. In the field, on site, or in a client meeting, that simply was not possible.

The consequences were predictable. Issues were noted on paper or recorded in a phone, then re-entered into the system later. Geo-tagged precision was lost. The gap between issue identification and logging created delays and inconsistencies in reporting. Teams were workstation-dependent when their work demanded they be mobile. The client needed to put the model directly in the hands of the people doing the actual work.

Platform Highlights

📱 REVIT model review on iOS, Android, and tablet devices
🌐 Autodesk APS and Forge powered model processing
📍 Geo-coded position tagging for issues and comments
📡 Full offline operability once a project is loaded
🔄 Automatic sync when connectivity is restored
📋 Structured issue and comment reporting directly from the app

The Solution

StudioKrew built i-Track from the ground up as a mobile-first AEC review platform. We used Autodesk APS and Forge to solve the core model processing challenge, and built native iOS and Android applications that delivered a full field-ready experience without any workstation dependency.

APS and Forge Model Processing

Native iOS Application (Swift)

Native Android Application (Kotlin)

Geo-Coded Issue and Comment Tagging

Offline Architecture and Auto-Sync

Structured Field Reporting System

StudioKrew's Role

StudioKrew was the product and engineering partner for i-Track from concept through to delivery. We designed the mobile UX for field conditions, integrated Autodesk APS and Forge APIs for model processing, built the native iOS and Android applications, and architected the offline-first data model with automatic sync. The client was under NDA and is not disclosed.

✅ Autodesk APS and Forge API integration for mobile model processing
✅ Native iOS app in Swift and Android app in Kotlin
✅ Full tablet support for site and field use
✅ Geo-coded position tagging with GPS accuracy
✅ Offline-first architecture with automatic sync on reconnect
✅ Structured issue and comment reporting with model annotations
✅ UX designed specifically for field and site conditions

Technology Stack

Powering Mobile-First REVIT Review with Autodesk APS, Forge, and Native Mobile Development
Every technology choice in i-Track was driven by the constraint of field use: the app needed to be fast, reliable, and fully functional with or without a network connection.

Autodesk APS and Forge

Autodesk Platform Services (APS) and Forge provided the cloud-based model translation layer that made REVIT model processing possible on mobile devices. Using the Model Derivative and Viewer APIs, we served full model data to iOS and Android without requiring Revit or a capable desktop on site.
Swift (iOS)

The iOS application was built natively in Swift to deliver the performance and reliability required for rendering complex REVIT model geometry on device. The native approach also gave us precise control over the offline data layer and GPS integration for geo-coded issue tagging.
Kotlin (Android)

The Android application was built in Kotlin with Jetpack Compose for the UI layer, delivering the same model review and issue reporting experience as iOS across the range of Android devices and tablets in use by the client's field teams.
Node.js

The backend API managed project distribution, model metadata, issue records, user access, and the sync queue for offline data. Node.js handled the event-driven architecture required for reliable offline-to-online data reconciliation when field teams reconnected.
MongoDB

MongoDB's document model suited the variable structure of AEC issue records, where each report could carry different combinations of position tags, geo-codes, annotated screenshots, and text comments. The offline data store on device used a compatible local document structure to simplify sync logic.
Offline-First Architecture

The offline architecture was built as a core requirement, not an add-on. Using local storage with a conflict-resolution sync strategy, the app maintained full functionality in basements, remote sites, and low-connectivity environments, then reconciled all data automatically when connectivity returned.

Team Composition

Project Manager

UI/UX Designer

QA Engineer

iOS Developers (Swift)

Android Developers (Kotlin)

APS Integration Engineer

REVIT API Developer

Outcome

i-Track changed the fundamental dynamic of how the client's field teams interacted with project data. Work that previously required a return to the office or a powered workstation on site could now happen anywhere, at any time, on any device.

Workstation Dependency Eliminated

Engineers and site managers could review full REVIT model geometry on a phone or tablet, navigate complex structures, and interact with model elements without any Revit installation or capable desktop required at the location.

Precise, Geo-Coded Issue Logging

Every issue raised in i-Track carried a position tag and GPS coordinates. Project managers received structured reports tied to exact locations, eliminating the back-and-forth that came from imprecise written or verbal issue descriptions and reducing resolution time significantly.

Full Offline Operability in Any Site Condition

The offline capability made i-Track viable across the full range of environments the client encountered, from basement plant rooms and remote construction sites to areas with poor or absent mobile connectivity. Teams worked without interruption regardless of signal.

Faster, More Consistent Reporting

Issue logging became faster and more consistent because the friction of the desktop-only workflow was removed. Reports generated directly in the field were structured, annotated, and geo-coded from the moment of capture, requiring no transcription or re-entry into a central system.

Why StudioKrew is the Right Partner for AEC Technology and Mobile BIM Development

AEC technology projects require a rare combination of domain knowledge and technical depth. You need a team that understands how AEC workflows actually work in the field, not just in theory, and can translate that into software that performs reliably under real site conditions. StudioKrew brings both.

We have hands-on experience with Autodesk Platform Services and Forge, using the Model Derivative, Viewer, Data Management, and Issues APIs to build production applications for AEC firms. We understand the constraints and capabilities of the APS ecosystem and how to build reliably within it.

Rendering complex REVIT model geometry on a mobile device is a performance challenge. We build natively in Swift and Kotlin rather than cross-platform frameworks when the use case demands it, giving us the control required for smooth, reliable model interaction in field conditions.

We have built offline-first applications where connectivity is unreliable by design, not by accident. Our sync architectures handle conflict resolution, data integrity, and resumable uploads so that field teams never lose work, regardless of what happens to their connection during a session.

StudioKrew builds across the full AEC technology stack: custom Revit add-ins, Dynamo scripts, APS and Forge integrations, and mobile BIM applications. We can identify where in your workflow a plugin is the right solution and where a mobile app serves the team better, and build either or both.

We regularly work under NDA and confidentiality agreements with AEC clients whose projects involve sensitive design data, proprietary workflows, and unreleased building programmes. We are comfortable operating within those constraints and can discuss our capabilities further under a mutual NDA.

Frequently Asked Questions

Common questions about mobile REVIT review, Autodesk APS and Forge integration, offline BIM applications, and how StudioKrew approaches AEC technology projects.

Yes. Using Autodesk Platform Services (APS) and Forge, REVIT models can be translated and served to mobile and tablet devices without requiring a Revit-capable desktop. StudioKrew built i-Track to do exactly this, enabling full model navigation and interaction on iOS and Android devices in the field.

Autodesk Platform Services (APS), previously known as Forge, is a set of cloud-based APIs that allow developers to extract, translate, and display CAD and BIM model data in custom applications. StudioKrew uses APS and Forge to build mobile and web applications that interact with REVIT, AutoCAD, and other Autodesk formats without requiring the host software on the user's device.

Geo-coded issue tagging allows a user to place a position marker on a specific point in a model or on site, with the device's GPS coordinates attached to the report. This ties every issue log to a precise physical location, removing the ambiguity of written or verbal descriptions and making follow-up and resolution significantly faster.

In i-Track, once a project is downloaded to the user's device, the full model and its associated data are available without an internet connection. Field teams can navigate models, raise issues, and add comments regardless of connectivity. When a connection is restored, all changes sync automatically to the central system.

Yes. StudioKrew has hands-on experience with Autodesk Platform Services and Forge, building custom mobile and web applications that consume APS APIs for model viewing, issue tracking, and design review workflows. We work with AEC firms, MEP contractors, and engineering companies to remove desktop dependency from field processes.

A REVIT plugin runs inside the Revit desktop application, automating or extending workflows for design and coordination teams. A mobile BIM review app uses cloud APIs like APS to serve model data to any device, enabling field review, issue reporting, and inspection without the Revit software. StudioKrew builds both, depending on where in the workflow the problem sits.

Yes. StudioKrew regularly signs NDA and confidentiality agreements with AEC clients whose projects involve sensitive design data and proprietary workflows. i-Track was developed for a client whose identity is protected under such an agreement. We are happy to discuss our capabilities further under a mutual NDA.

i-Track: Taking REVIT Model Review Off the Workstation and Into the Field

About the Platform