Territory 12Active
North Florence
18 streets · 126 addresses
- Assigned
- Today
- Due
- Sep 10
- Progress
- 64%
Development
Territory operations · Apple-native
TerritoryHub
See the territory. Know the state. Move the work.
An offline-first command center that brings territory records, maps, publishers, assignments, campaigns, S-13 history, search, recovery, and operational tools into one adaptive Apple workspace.
The experience
A territory command center that feels at home on iPad.
The website now mirrors TerritoryHub's real visual direction: dark navy depth, cool ice accents, restrained route fields, clear hierarchy, floating controls, and motion that explains state instead of decorating it.
Features
From the map to the history record, everything stays connected.
TerritoryHub is the administration side of the territory workflow. It keeps the operational record local-first while making assignment, mapping, campaign, search, and recovery work feel like one system.
Map-first territory records
Create and edit territories with addresses, coordinates, markers, colored boundaries, polygons, status, priority, notes, attachments, and selected photos.
Assignment operations
Plan, activate, return, complete, cancel, search, and review territory assignments with due dates and safeguards against invalid duplicate states.
S-13 and service-year history
Maintain synchronized digital territory history and official-form presentations with completion context, continuation pages, export, print, and sharing.
Campaign organization
Group territories into campaign work with goals, schedules, progress, and lifecycle controls.
Universal search
Search territories, publishers, assignments, campaigns, S-13 history, notes, tags, addresses, and activity from one workspace-aware system.
Recovery built in
Use versioned backups, integrity checks, attachment recovery, rollback protections, and separate Demo and Live workspaces.
Interface
Apple-native, not a spreadsheet with a map bolted on.
The production application uses adaptive SwiftUI navigation, map, search, assignment, record, settings, and recovery surfaces. Website illustrations communicate the interaction direction without pretending to be shipping screenshots.
One product, two Apple form factors.
Compact layouts prioritize focused bottom navigation and direct tasks, while iPad can expose persistent navigation, layered context, and richer operational depth.
- Dynamic Type and VoiceOver support
- Large interaction targets and keyboard-aware navigation
- Reduce Motion enforcement and personalization controls
Requirements
Current development requirements.
These requirements describe the current application repository and development path, not a public App Store listing.
- Devices
- iPhone and iPad
- Operating system
- iOS 17 or later
- UI framework
- SwiftUI
- Development
- Swift Playgrounds on iPad or Xcode
Roadmap
From verified core to public release.
The current main branch has a verified core milestone. Distribution work remains a separate release gate.
Core milestone verified
Repository, source, Xcode application build, packaged icon/privacy resources, simulator launch, and automated test gates have established the current engineering checkpoint.
Signing and device validation
Complete current signed builds and physical-device validation against the release candidate.
Controlled beta distribution
Use TestFlight and device beta evidence to isolate defects before broad distribution.
Store release gate
Complete final metadata, legal, privacy, support, accessibility, and App Store submission checks before public availability is declared.
Downloads
No public installer is published yet.
The website will only expose a download after an official artifact has been uploaded to the Raysor distribution store, versioned, checksummed, and attached to an approved release channel.
Developer channel
Internal development path
Repository development continues, but the website does not publish an unsigned or unverified development package as a public release.
Beta + Stable channels
Distribution gate not open
Beta and Stable remain unavailable until product-specific signing, device, and release validation is complete.
Companion workflow
TerritoryHub manages. Territory Field works the assignment.
The two products have different responsibilities so the administration experience and field-user experience can stay focused.