Request territory
Start the workflow from a simple field-user request rather than exposing administration complexity.
Development
Field assignments
Territory Field
A lightweight iPhone and iPad companion built around one field workflow: request a territory, receive it, understand it immediately, work it offline, record progress, and return it.
What it does
Keep the field experience simple.
Territory Field deliberately does not become a second administration app. TerritoryHub owns map authority and congregation-side management; Territory Field stays centered on the assignment in the user’s hands.
Receive clearly
Present the assignment, territory identity, boundaries, and essential context in a form that can be understood quickly.
Work offline
Keep the core field workflow usable without depending on a live network connection.
Record progress
Capture field-service progress locally with a workflow designed for fast, practical updates.
Return the assignment
Close the loop by returning the territory and synchronizing the state back to the management side when connectivity allows.
Stay lightweight
Keep navigation, data entry, and assignment context focused on the field user instead of duplicating TerritoryHub.
Interface
Assignment first.
The production app is designed to adapt across compact iPhone layouts and larger iPad layouts. This website panel illustrates the information hierarchy without pretending to be a shipping screenshot.
Less navigation. More territory.
The field experience prioritizes the active assignment, map context, progress, and return path. Larger layouts may expose more persistent context, while compact layouts stay thumb-friendly.
- Local-first field state
- Map and assignment context
- Simple progress and return workflow
Requirements
Current development path.
Territory Field is currently opened from its Swift package in Swift Playgrounds on iPad or in Xcode with a current Swift toolchain.
- Devices
- iPhone and iPad
- Development package
- TerritoryField.swiftpm
- Toolchain
- Swift 6.1 or newer
- Connectivity model
- Core field workflow remains usable offline
Roadmap
From local-first companion to synchronized field client.
The product keeps offline usability as a non-negotiable boundary while cloud synchronization is layered in around it.
Complete core field workflow
Finish the request, receive, understand, work, progress, and return experience with strong local behavior.
Validate adaptive navigation
Keep compact devices focused while allowing larger iPad layouts to expose useful persistent context.
Connect Cloud V2 synchronization
Synchronize assignment snapshots and queued field mutations without making connectivity a prerequisite for field work.
Open controlled distribution
Publish a signed beta only after device, data-integrity, offline, and synchronization gates pass.
Downloads
Public distribution is not open.
No public installer or App Store acquisition path is published by the website until an approved, signed release artifact exists.
Developer channel
Active development
The source package is under active engineering. The public website does not expose repository development packages as end-user releases.
Beta + Stable channels
Awaiting release gates
Controlled and public channels remain closed until the product’s distribution criteria are satisfied.
Administration side
Need to manage the territories themselves?
TerritoryHub owns the congregation-side territory records, maps, assignments, campaigns, and history that Territory Field consumes.