Compass (iPad)

Problem / Context

Operations teams needed fast planning workflows across dense schedules where lag and data inconsistency directly impacted execution quality.

Constraints

• Enterprise security controls and network boundaries.
• Complex scheduling UI with large data volumes on iPad.
• Reliability requirements under partial or delayed API responses.

Approach / Architecture

Used SwiftUI with MVVM and explicit app state ownership. Data workflows were structured to isolate side effects, protect UI responsiveness, and preserve consistency between local persistence and service updates.

UI (SwiftUI Views)
  -> ViewModel (MVVM)
    -> Domain / State Coordinator
      -> Data Layer (SwiftData/Core Data + API)

Key Decisions

• Reduced view invalidation paths in list/grid-heavy screens.
• Moved expensive setup and reconciliation work off the main thread.
• Standardized state and data interfaces across modules to lower implementation drift.

Results / Impact

• Improved planner responsiveness during high-frequency interactions.
• Stabilized behavior for partial-data and delayed-network scenarios.
• Enabled faster, lower-risk feature delivery via consistent architecture patterns.

Tech Stack

SwiftUI, SwiftData / Core Data, MVVM, Combine, async/await, REST APIs, Instruments