Offline Team Inspection App

• Three-column inspection form built for landscape iPad: pick the building, unit and area on the left, the inspectable item in the middle, and record defects on the right.
• The standard's full defect catalog on the device: 65 items and 432 defect rows, each with its D-number, severity, regular and voucher (HCV) correction times and area-specific points, plus four sections of reference text per defect. All of it works with no signal.
• One-tap capture with locations, comments, one-tap canned comments and photos for each defect. No Save buttons: every edit saves itself.
• Color-coded areas (Outside green, Inside purple, Unit blue) at the client's request, with the same rules as the website for when each area opens (Inside needs a building, Unit needs a unit).
• Photos from the camera or library, resized to a 2048 px long edge, compressed to 2 MB or less and stripped of GPS data, then queued until they can upload.
• Sync status at a glance and a My Captures hand-back check that tells the inspector whether everything is safe on the server before leaving the property.
• Two offline PDF reports: the Full Deficiency Report and the 24-Hour List (Life-Threatening and Severe), laid out like the website's reports and shared to Mail, AirDrop, Print or Files.
• Roles and inspection locks that mirror the website's own rules.

Screens shown with sample data. They're mockups redrawn from the real app layouts, and every property, unit, person and inspection number in them is made up.

• SwiftUI views over @Observable stores, a local SQLite database through GRDB, a sync engine, and an API client protocol with seven calls. Today a built-in mock server implements that protocol; switching to the live API changes only the transport.
• Offline journal (outbox pattern). Every capture writes the record and an "intent" to an append-only journal in the same database transaction, so nothing is lost if the app is closed or the battery dies. Sync replays the journal in order, and replaying the same changes twice is harmless.
• Identity across the offline gap. Buildings, units, defects and locations created offline get their own IDs on the device, which the server maps to its IDs when it accepts them.
• Merge without overwriting. Downloads from the server never overwrite edits still waiting on the iPad, so two inspectors on the same property don't lose each other's work.
• Photos wait for their records. A photo uploads only after the location it belongs to exists on the server.
• Native PDF reports drawn with UIGraphicsPDFRenderer on a background thread, with row heights measured from the wrapped text and small photo thumbnails to keep files light.

StackSwift 5, SwiftUI, Observation, GRDB 7 (SQLite), Swift concurrency, PhotosUI, UIKit PDF rendering, PDFKit, XCTest, Xcode 16, iPadOS 17+.

• Audit first. Capturing every write the website makes showed exactly what the app had to reproduce, and gave the client's developer fixes to make before the app relied on that path.
• A mock server that doubles as the spec. It enforces the same rules the real server must (locks, roles, idempotent replay), and the client's developer builds against it.
• API built together with the client's developer over five rounds of sample data plus two login samples. All 3,851 timestamps were checked for correct UTC conversion, including across the daylight-saving change.
• Source data kept exactly as the client has it. When analysis turned up questionable values in a few catalog rows, they went back to the client as questions instead of being quietly patched in the app.