Skip to content

Mobile Companion — Overview

Computtite Mobile Companion is the mobile operational client for field workflows. It provides hardware identification, batch operations, and real-time inventory synchronization on Android and iOS devices.

The Mobile Companion operates exclusively in conjunction with Supabase Cloud workspaces provisioned and administered through Computtite Desktop. Workspaces in Local Mode must be migrated to Cloud Mode to enable mobile synchronization. For architecture specifics, consult Local Mode and Cloud Mode.

Operational Scope

The Companion focuses on physical, on-site hardware lifecycle operations:

Supported operations:

  • Optical scanning of computtite:// QR codes and Code-128 linear barcodes.
  • Batch scanning into an in-memory Scan Bag for bulk transitions (assignment, return, maintenance hold, audit verification).
  • Departmental physical reconciliation audits against server catalog expectations.
  • Point-of-service status and custody updates.
  • Real-time event telemetry and health alert monitoring.
  • Directory search for assets and organizational personnel.
  • On-device QR label generation and system share-sheet export.

Desktop-exclusive operations:

  • Custom type schema design and field definitions (Forge Hub at /workspace/activos).
  • Workspace governance, user invitations, and access profile configuration (/workspace/administration/).
  • Formal analytical reporting and external cloud exports (CSV, XLSX, PDF, Google Sheets, Notion).
  • Local-only SQLite operations.

Current Version and Compatibility

Computtite Mobile Companion v1.0.0 — operational release for Android and iOS. Authentication can be performed via email/password or using Desktop Magic Pairing QR codes generated under /workspace/profile.

System Requirements

  • Operating System: Android 10+ or iOS 15+.
  • Workspace: Active Computtite Cloud workspace (backed by Supabase).
  • Authentication: Valid user credentials or active Magic Pairing session token.
  • Network Connectivity: Persistent HTTPS/WSS connection required; offline caching is restricted to session scratchpads.

Role-Based Access Control and Row-Level Security

All mobile queries and mutations operate within the context of the user’s authenticated Supabase JWT. Platform roles (Owner, Admin, Member, Read-Only) and custom visibility profiles configured in Desktop apply directly to mobile sessions, enforced by PostgreSQL Row-Level Security (RLS) policies at the database layer.