The Company App: Offline-First Operations Platform

Context

Small businesses operating with 8–25 employees across warehouse and office environments face a structural coordination problem: the data they need to run operations — inventory levels, order status, dispatch assignments — lives in multiple disconnected systems. Warehouse staff update a spreadsheet. Office staff check a different one. Dispatch logs are handwritten. Customer communication happens over email.

No single source of truth exists. Teams routinely act on stale data. Fulfillment errors are a predictable consequence of the architecture, not a failure of individual effort.

Problem

The team operated across 4–5 tools: spreadsheets for inventory, messaging apps for team coordination, paper dispatch logs, and email for client communication. No tool communicated with another. Warehouse and office staff frequently worked from stale data — a fulfillment pick might reference inventory that had already been committed to a different order.

The instinct is to solve this with a web platform and a shared database. The problem: warehouse connectivity is unreliable. A system that requires a server connection to function would fail at the point where it matters most — on the warehouse floor during a stock count or dispatch run.

Constraints

• —Warehouse connectivity is unreliable — fully offline operation was required, with automatic sync on reconnection
• —Multi-user concurrent writes required conflict resolution without a custom backend
• —Sensitive business data (supplier contacts, pricing, order volumes) could not transit third-party services
• —No IT department on the client side — zero-maintenance sync infrastructure was a hard requirement
• —iPad form factor needed to work in warehouse scanning contexts: large tap targets, minimal navigation depth

Architecture Approach

The constraint that shaped everything: warehouse staff cannot wait for a server response. Offline-first was not a feature request — it was the design premise. Every architectural decision flows from that.

Implementation: Offline-Aware UI State

Every view that shows synced data needs to communicate its sync state to the user — not as a banner, but inline. The pattern used across the app surfaces pending changes count and last-sync timestamp as lightweight metadata attached to each list item:

// Observe CloudKit sync events via NotificationCenter
// and surface pending record count to UI without blocking

class SyncMonitor: ObservableObject {
    @Published var pendingCount: Int = 0
    @Published var lastSyncDate: Date?

    init(container: NSPersistentCloudKitContainer) {
        NotificationCenter.default.addObserver(
            forName: NSPersistentCloudKitContainer
                .eventChangedNotification,
            object: container,
            queue: .main
        ) { [weak self] notification in
            guard let event = notification.userInfo?[
                NSPersistentCloudKitContainer.eventNotificationUserInfoKey
            ] as? NSPersistentCloudKitContainer.Event else { return }

            if event.succeeded {
                self?.lastSyncDate = event.endDate
            }
        }
    }
}

// In SwiftUI view: show offline badge when pending > 0
struct InventoryRowView: View {
    let item: InventoryItem
    @ObservedObject var syncMonitor: SyncMonitor

    var body: some View {
        HStack {
            VStack(alignment: .leading) {
                Text(item.name)
                Text("\(item.quantity) units")
                    .foregroundStyle(.secondary)
            }
            Spacer()
            if syncMonitor.pendingCount > 0 {
                Image(systemName: "arrow.triangle.2.circlepath")
                    .foregroundStyle(.orange)
                    .imageScale(.small)
            }
        }
    }
}

Solution Highlights

• •NSPersistentCloudKitContainer — zero-backend sync through Apple infrastructure, no server costs
• •Separate private/shared CloudKit stores for role-based data isolation at the persistence layer
• •Log-structured stock movements for conflict-safe concurrent inventory updates
• •Partial sync: field staff receive only their assigned dispatch subset via CloudKit record zones
• •iPad split-view layouts with large tap targets and offline-aware status indicators
• •Zero third-party dependencies — every SDK is a first-party Apple framework

Key Technical Learnings

Technical FAQ