public active Last verified 2026-04-10

TwinView

Standalone property digital-twin application for hybrid 360 capture, Matterport-backed premium twins, inspections, and client sharing.

Owners
platform-experience
Source Repos
PlatformApplications/TwinView
Systems
Topolo Auth, TwinView
Tags
digital-twins, property, capture, auth

What It Is

TwinView is a standalone digital-twin application for residential and commercial property capture, hosted tours, inspection workflows, and client-facing share surfaces.

Architecture

TwinView is a Topolo-hosted third-party application. It keeps its own product surface, data model, and runtime while relying on Topolo Auth for browser sign-in, session refresh, logout, and service registration.

The current product model is hybrid:

  • TwinView-owned panorama360 twins for lower-cost 360 capture and hosted tour workflows
  • Matterport-backed matterport twins for premium scan jobs that need higher-fidelity presentation or downstream export handling

Runtime Surfaces

  • application host: https://twinview.app
  • API host: https://api.twinview.app

API Reference

The current curated API surface is implemented in the TwinView worker runtime. It covers properties, units, capture jobs, twins, annotations, inspection tasks, uploads, share views, and Matterport connection metadata.

Auth and Permissions

TwinView uses the shared Topolo browser auth client and a dedicated Auth service registration. It should not add an app-local account system or custom refresh protocol.

Data Ownership

TwinView owns property records, capture jobs, twin records, annotations, inspection tasks, public share state, and TwinView-specific integration metadata. Topolo Auth owns identity, session validation, service registration, and launcher metadata.

Deployments

TwinView deploys as a Cloudflare Pages frontend plus a Worker API runtime documented in its internal handbook.

Failure Modes

  • the Pages surface and API drift to different environments
  • browser auth drifts away from the shared Topolo cookie-refresh contract
  • Twin metadata diverges between panorama360 and matterport source paths
  • public share pages drift away from the documented mobile and design-language constraints

Debugging

Start with /systems/twinview, then verify the deployed Pages frontend, Worker API health, and Auth service registration together before changing application code.

Change Log / Verification

  • Added the canonical TwinView application coverage on 2026-04-10, including the hybrid panorama360 and matterport runtime model and the shared Topolo Auth dependency
  • Verified the production TwinView runtime surfaces on 2026-04-10 at twinview.app and api.twinview.app