Zac Batten Inefy workbench

TraverseOps public app

Field operations map and work orders.

Designed around a Supabase-style data model; the public version uses sample data for safe review while showing a map-first asset workspace with inspections, work orders, import validation, reports, and role-aware controls that stay usable on a phone.

Open workspace Read case study
Status
Public sample-data prototype
Last updated
May 2026

Production readiness

Sample records, not an active field deployment.

The public version is useful for reviewing asset maps, inspection/work-order flows, imports, reports, and role-shaped UI. It remains sample-only because it does not enforce production authentication, permissions, offline sync, audit logging, or production map/data reliability. A field rollout would require tenant-safe data access, import validation, mobile device testing, logs, backups, and map-source alerts.

Read production plan Use sample app

Testing and QA notes

QA checks device and data-state risks.

Automated tests: no public test suite is linked yet. Manual QA covers loading/resetting sample data, tab switching, map-marker selection, filters, inspection and work-order forms, import staging, report summaries, keyboard focus, mobile touch targets, and repeated empty/reset states. Browser checks should include narrow phones, tablets, desktop widths, reduced motion, and long labels or notes that could break layout.

Known limitations: the app does not simulate production authentication, offline sync conflicts, production GIS services, bulk import security, or actual field-device network loss.

Read QA notes Run sample flow

Deployment and run notes

Sample-data browser app with no public secrets.

Hosted/run location: GitHub Pages serves traverseops-demo.html, traverseops-demo.js, shared CSS, and local screenshots/assets. Environment/config: no environment variables are required; sample assets, inspections, work orders, and import states live in client-side JavaScript. External APIs/services: this public app does not connect to GIS services, Supabase, authentication, or municipal APIs.

Local development: run python -m http.server 8000 from the portfolio repo root and open /traverseops-demo.html. Security: keep production asset data, service-role keys, GIS credentials, and private imports out of public files; production would move validation and permissions server-side.

Read run details Open workspace

Workspace

North Harbor zone

Tap through the tabs to inspect assets, create field records, validate imports, and review sample reports.

Sample workspace ready. Select a marker or open a task tab.

Map workspace

Tap an asset marker.

North Harbor

Next step

Compare the app with the case study.

The case study explains the architecture, data model, public limits, and production plan behind this mobile-friendly sample workspace.

Read case study Back to Work