Skip to content
Thorbis
Back to roadmap

Platform Quality

Thorbis Offline-First Command Platform

PlannedLater in 2026Design and architecture review

One durable command platform so technicians and office staff can keep working through dead zones, with honest sync status, safe payments, and the same rules on web, mobile, and desktop.

Overview

Field crews lose signal in basements, rural routes, and metal buildings, but the job does not wait. Thorbis Offline-First is a single command platform that lets every client save work locally first, show you exactly what is on the device versus confirmed on the server, and sync safely when connection returns. Instead of bolting retries onto hundreds of separate buttons, every mutation, online or offline, follows the same path: write a durable local command, update the screen optimistically, transmit when possible, and reconcile with server truth. Web, admin, mobile, and desktop share the same behavior. Thorbis will be honest about what cannot complete offline: live phone audio, new card entry, bank verification, and AI generation require connection. Cash and manual payments, notes, photos, forms, drafts, and queued SMS or email intents can be captured locally with clear “saved on device” / “queued, not sent” / “awaiting confirmation” language, never pretending money moved or a message was delivered until the server acknowledges it. A Sync Center under Settings shows pending work, conflicts, storage usage, and plain-language fixes when something needs attention.

What we're building

Field crews lose signal in basements, rural routes, and metal buildings, but the job doesn't wait. Bolting retries onto hundreds of separate buttons leaves crews unsure what actually saved and what's still stuck on the phone.

Thorbis Offline-First is a single command platform where every change, online or offline, follows the same path: write a durable local command, update the screen optimistically, transmit when possible, and reconcile with server truth, the same way on web, admin, mobile, and desktop. A Sync Center shows pending work, conflicts, storage use, and plain-language fixes when something needs attention.

It stays honest about limits: cash and manual payments, notes, photos, forms, and queued messages can be captured locally with clear "saved on device," "queued, not sent," and "awaiting confirmation" language, while live phone audio, new card entry, bank verification, and AI generation still require a connection.

What you'll be able to do

  • Phase 0: AST mutation inventory and CI gate for offline action classification
  • Phase 1: Shared OfflineCommand schema, error schema, and generated action registry
  • Phase 2: Sync API v1 (push, pull, bootstrap) with durable Postgres idempotency
  • Phase 3: Local storage adapters, web/admin IndexedDB, mobile SQLite, desktop SQLite/IPC
  • Phase 4: Jobs vertical slice, cached job, note, photo, material, safe status, offline restart, sync, conflict
  • Phase 5: Field operations, forms, signatures, time, equipment, estimates, invoice drafts, completion
  • Phase 6: Office and admin, customers, scheduling, dispatch, settings, inventory
  • Phase 7: Communications replay through outbox (queued never shown as sent)
  • Phase 8: Payment-intent safety, manual payments, Terminal offline option, phone fallbacks
  • Phase 9: Chaos and data-loss test suite (24h offline, 10k commands, attachment stress)
  • Permanent cross-app connection bar and Settings → Offline & Sync center
  • Offline data packs with dynamic storage limits and tenant-isolated encryption
  • Attachment pipeline with dependency graph blocking job completion until uploads ack
  • Domain-specific conflict resolution preserving both local and server versions
  • Same domain service path for web, admin, mobile, desktop, and sync replay

Rollout plan

  1. 01

    Shared command foundation

    In progress

    Establish one command schema, a generated action registry, and a push/pull/bootstrap sync API with durable idempotency.

  2. 02

    Vertical slices across clients

    In progress

    Bring jobs, field operations, and office workflows offline with local storage adapters for web, admin, mobile, and desktop.

  3. 03

    Comms, payments, and chaos hardening

    In progress

    Add outbox message replay, payment-intent safety, and a data-loss test suite covering long offline windows and heavy command volume.

Milestones

  • Not started:

    Command and sync core

    Ship the shared command and error schema and Sync API v1 with Postgres idempotency.

  • Not started:

    Local storage adapters

    Deliver IndexedDB, mobile SQLite, and desktop storage on one domain service path.

  • Not started:

    Jobs offline slice

    Prove cached job, note, photo, status, restart, sync, and conflict end to end.

  • Not started:

    Sync Center and safety

    Ship the connection bar, Sync Center, payment-intent safety, and queued-never-sent messaging.

More in Platform Quality

How to send useful feedback

Name the blocked role

Product feedback is more useful when it names the owner, dispatcher, technician, office user, or customer affected.

Explain the workaround

Describe what your team does today and where the process fails under real work.

Define success

Share what would change after launch: time saved, fewer manual steps, cleaner records, or better customer follow-up.

Built for operators

A shared operating layer behind every page

Whether a buyer starts on an industry, feature, migration, or tool page, Thorbis routes the conversation back to the same product system: jobs, money, customers, and team work in one place.

01

One workspace

CRM, dispatch, estimates, invoices, payments, and reporting stay connected.

02

Unlimited users

Bring owners, office staff, dispatchers, techs, and managers into the same system.

03

Guided switch

Migration planning, validation, and cutover support are built into the buying path.