Map-first territory records
Create and edit territories with addresses, coordinates, markers, colored boundaries, polygons, status, priority, notes, attachments, and selected photos.
Territory management
An offline-first, Apple-native territory management application that brings territory records, maps, publishers, assignments, campaigns, S-13 history, search, recovery, and operational tools into one adaptive workspace.
What it does
TerritoryHub is the administration side of the territory workflow. It keeps the operational record local-first while providing structured assignment, map, campaign, search, and recovery systems.
Create and edit territories with addresses, coordinates, markers, colored boundaries, polygons, status, priority, notes, attachments, and selected photos.
Plan, activate, return, complete, cancel, search, and review territory assignments with due dates and safeguards against invalid duplicate states.
Maintain synchronized digital territory history and official-form presentations with completion context, continuation pages, export, print, and sharing.
Group territories into campaign work with goals, schedules, progress, and lifecycle controls.
Search territories, publishers, assignments, campaigns, S-13 history, notes, tags, addresses, and activity from one workspace-aware system.
Use versioned backups, integrity checks, attachment recovery, rollback protections, and separate Demo and Live workspaces.
Interface
The production application uses an adaptive SwiftUI interface with dashboard, map, search, assignment, record, settings, and recovery surfaces. The visual panel below is a website illustration, not a fabricated shipping screenshot.
Compact layouts prioritize bottom navigation and focused workflows, while larger iPad layouts can expose more persistent navigation and operational context.
Requirements
These requirements describe the current application repository and development path, not a public App Store listing.
Roadmap
The current main branch has a verified core milestone. Distribution work remains a separate release gate.
Repository, source, Xcode application build, packaged icon/privacy resources, simulator launch, and automated test gates have established the current engineering checkpoint.
Complete current signed builds and physical-device validation against the release candidate.
Use TestFlight and device beta evidence to isolate defects before broad distribution.
Complete final metadata, legal, privacy, support, accessibility, and App Store submission checks before public availability is declared.
Downloads
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.
Repository development continues, but the website does not publish an unsigned or unverified development package as a public release.
Beta and Stable remain unavailable until product-specific signing, device, and release validation is complete.
Companion workflow
The two products have different responsibilities so the administration experience and field-user experience can stay focused.