This document is a single-file operator manual for the OPSx web interface. It covers the login workflow, room layout, controls, settings, permissions, supported platforms, the optional AES-GCM end-to-end encryption mode, and the current demo-room limit.
Desktop Chrome, Android browsers, and iOS browsers are supported for the web client.
The interface is responsive and adapts between handset and larger-screen layouts.
The web client has two primary states: the sign-in page and the active room page. After authentication, users enter a room with a header bar, user list, video and map tabs, an optional settings panel, and per-user toggles for microphone, camera, and location sharing.
The main workspace switches between a multi-user video view and a live map view. The map can center on users who are broadcasting location data.
The client stores the last-used room code, callsign, optional AES-GCM passphrase, and display preferences in the browser for faster reuse on the same device.
Users join by entering a shared room code and a unique callsign.
The callsign becomes the user identity shown to other users in the room.
Case-insensitive room access code used to resolve the target room.
Unique user identity. Supported format is 1 to 32 characters using letters, numbers, period, underscore, and hyphen.
If enabled, the user enters a shared passphrase and the client prepares end-to-end media encryption before connecting to the room.
The user panel shows all current callsigns, supports live search, and indicates whether each user is publishing audio, video, and recent location.
Shows a grid of remote video tracks. On larger screens the number of tiles per row is controlled in Settings. Smaller screens automatically reduce the layout.
Displays user location markers and supported map layers. Callsign labels can be shown only on hover or always visible, depending on operator preference.
The header contains the live room name, the active callsign, and the primary user controls.
Toggles local microphone publishing on or off.
Toggles local camera publishing on or off. The client prefers the rear-facing camera where available.
Starts or stops location broadcast to the room. When off, the user's marker is removed from the shared map.
Keeps supported devices from sleeping during active use. Availability depends on browser support.
Opens the settings sheet for appearance, map, video, and telemetry preferences.
Enters or exits browser fullscreen mode for maximum viewing area.
Leaves the room and returns the user to the sign-in state.
Shows or hides the user panel. On smaller screens it opens as a side sheet.
Settings are applied live and saved to the browser. They affect only the local user unless otherwise noted.
Theme options: Dark, Light, Night.
Night mode is intended for reduced-light use and follows the same per-user preference model as the other display settings.
Tiles Across: 1, 2, 3, or 4 on large screens.
Small screens automatically use the mobile layout regardless of this setting.
Basemap options: OSM, Satellite, Streets, Topo.
Callsign Labels: On Hover or Always On.
Location Broadcast: Broadcasting or Silent.
Silent mode stops local position transmission and removes the user's marker from the shared map.
The web client relies on browser permission prompts. Operators should expect permission behavior to vary slightly by platform, but the access categories are the same.
The login screen includes an AES-GCM toggle for optional end-to-end media
encryption. When this option is enabled and a passphrase is supplied, the client prepares
an AES-GCM key provider and encryption worker before connecting to the room, then enables
encrypted media handling for the session. Drone publishers do not enter the key on the
drone side; they inherit the encryption behavior from the OPSx SC-configured session.
If AES-GCM is not enabled, the room still uses TLS transport encryption, but AES-GCM is
the stronger end-to-end encryption mode.
The current supported browser and device scope for the web client is:
Supported for mobile access, including the responsive sign-in, user roster, map view, and media controls.
Supported for mobile field use, including location sharing, audio/video toggles, and the settings sheet.
Supported for desktop and compatible mobile deployments. Chrome provides the fullest support for advanced web capabilities such as wake lock and fullscreen.
Demo rooms are limited to a number of users. Once the room reaches the configured visible-user capacity, additional join attempts should be treated as full-capacity conditions.
Independent AR is currently in beta as a per-user option, with the same toggle model used by the current local interface settings.
Each user can enable or disable Independent AR locally without forcing the same mode on every other user. This keeps it consistent with the current per-user approach used for display and telemetry controls.