FieldBook.
An offline-first iOS and macOS app for service businesses that schedule crews across days, sites and time zones, and need it to work with no signal.
- Type
- Concept build
- Role
- Product design, Swift development
- Year
- 2026
- Swift
- SwiftUI
- SwiftData
- CloudKit
NOTE // This is a concept build: a self-initiated project that shows how I would architect this kind of product. It is not a client engagement, and the targets below are design goals, not reported results.
Technical_Hurdle:
Managing thousands of offline-first service records with complex scheduling logic on iOS and macOS.
Execution_Resolution:
Leveraged SwiftData for localized persistence and sync. Built a custom scheduling engine in Swift to handle edge cases like time-zone shifts and recurring multi-day appointments.
The Approach
- 01
Local-first by default
Every record lives on the device first and syncs through CloudKit in the background, so a technician in a basement still sees the whole day's jobs.
- 02
A scheduling engine with tests
Recurrence, daylight-saving shifts and multi-day jobs are handled by a pure Swift module covered by unit tests, kept separate from the UI.
- 03
One codebase, two platforms
SwiftUI views adapt from an iPhone checklist in the field to a dense multi-column planner on the Mac in the office.
Design Targets
- Full functionality with no network connection
- Correct schedules across time zones and DST changes
- Shared SwiftUI code between iOS and macOS