Skip to content

Interface, accessibility, and mobile roadmap

The desktop tuner puts receiver controls on the left, the spectrum and waterfall in the center, and signal intelligence on the right. On a narrow screen, use the navigation tabs to switch between those tasks.

On desktop, drag the inner edge of Receiver controls or Signal intelligence to resize it. The spectrum keeps room in the center. Focus a divider and use Left/Right to move it, or Home/End for the smallest/largest width. Double-click the divider to restore its default width. The chevrons collapse and reopen the panels. The browser remembers each width on this device for this appliance origin.

Current interface

  • The primary tuner combines receiver/mode/audio controls, spectrum/waterfall, signal evidence, and independent lane status. Text-size and spectrum/waterfall sizing preferences are persisted. GPU rendering has explicit WebGPU/WebGL2/ Canvas2D paths, not one assumed backend.
  • Spectrum wheel input pans; waterfall wheel input zooms around the pointer; the left dB gutter uses the selected tuning step. VFO/filter/divider drags capture the pointer, and the focused spectrum accepts left/right Arrow keys. See receiver navigation.
  • Clicking a signal inspects it without tuning. Double-click or the inspector action invokes the same explicit assisted activation, subject to pins, cancellation, undo and decoder admission. See operator authority.
  • Signal rows preserve parent identity/order. Live and historical waterfall annotations use capture/RF geometry; details distinguish evidence from hypotheses. The feature inventory identifies absent metrics rather than filling them with guesses.
  • The detachable decoder workspace has persisted movable/resizable panels. It is a same-origin portal into the main owner's workers, not a second receiver client.
  • Narrow layouts already expose Listen, Signals, Receivers, Controls, Info and Documentation navigation. Responsive CSS, touch-capable pointer controls, labels and reduced-motion styling exist; they do not close Phase 5's wider mobile workflow or prove full keyboard/screen-reader coverage.

Implementation anchors under components/rfsentry-web/: src/ui/App.tsx, SpectrumCanvas.tsx, uiPreferences.ts, styles.css and src/detection/SignalDetector.ts. These are source-inspection findings, not a new browser acceptance test.

Design requirements

The original frontend requirements follow. Preserve their intended behavior where implementation is narrower:

  • Dragging an arbitrary new passband, clicking a historical trace to start IQ replay, and general multi-touch pinch navigation are not established by the inspected spectrum handlers. Current historical annotation clicks select evidence; DVR time controls separately select IQ.
  • Notch/noise-processing and complete per-mode/per-receiver state remain wider requirements; implemented pins and lane preferences do not prove every requested control.
  • The original top-N envelope averages describe the coarse stability policy. Fine-edge stabilization also uses robust outward percentiles and paired measurements; the published boundary contract remains authoritative. A moving power peak never defines the envelope.
  • Proposed Listen | Scan | Signals | Controls navigation and mobile automatic scanning remain Phase 4/5 scope, not the shipped responsive tabs. Background scanning, wake-lock reliability and mobile throughput require independent qualification.

Visual Direction

  • High-DPI spectrum above a deep, fluid waterfall.
  • Perceptually uniform, selectable waterfall palettes.
  • A graphite or dark-neutral control surface with restrained semantic color.
  • Excellent typography and numeric alignment.
  • A large, precise frequency readout.
  • Clear spacing and hierarchy without wasting spectrum area.
  • Subtle depth and translucent overlays without excessive glass effects.
  • Smooth motion that never interferes with audio or tuning.
  • Original icons and controls rather than copied SDR++ assets.

Primary Interaction

  • GPU-rendered pan and zoom centered under the cursor.
  • Draggable VFO and filter edges.
  • Configurable mouse-wheel tuning steps.
  • Direct frequency entry.
  • Keyboard fine and coarse tuning.
  • Click once on a detected signal to select and pin its measurements without changing receiver or DSP settings.
  • Double-click a detected signal to invoke intelligent activation: tune, configure every supported unpinned setting, refine, and start an applicable decoder through the shared activation policy.
  • Hover to see a compact evidence card.
  • Drag across the spectrum to create a manual passband.
  • Pause and inspect waterfall history.
  • Click a recent historical trace to replay it from the IQ ring buffer.

Signal Presentation

  • One translucent, waterfall-confined live corridor per confirmed parent emission; internal FFT islands never receive normal user-visible corridors.
  • One historical activity rectangle per emission period, attached to the retained identity and scrolling with the waterfall pixels. Suppress its outline while the corresponding live corridor is present, then reveal it after the live occurrence ends.
  • Stable envelope edges taken directly from lower/upper measurements rather than recentered on a moving power peak. Responsive averages the widest three envelopes over one second, Balanced the widest eight over four seconds, and Stable the widest 16 over ten seconds.
  • Evidence-state chips that do not rely on color alone and do not imply an uncalibrated probability.
  • Compact labels at normal zoom.
  • Detailed cards only on hover or selection.
  • A stable Signals in view rail that does not reorder while the operator is reading or making a selection; ended signals dim in place and expire on a visible policy.
  • SNR, bandwidth, mode, activity, duration, drift, service hypothesis, and decoder state.
  • Clear distinction between measured facts and inferred labels.
  • Unknown signals should still receive useful measurement cards.
  • A visible per-lane Signal detection toggle, default on. The disabled state says Detection paused, removes detector clutter, and leaves the receiver, waterfall, listening, and manual controls usable.
  • An optional diagnostic overlay for noise baseline, seed/grow thresholds, raw islands, parent grouping, artifact flags, and rejected candidates. It is off by default and never changes publication policy.

Selected-Signal Inspector

The inspector should show:

  • Receiver and antenna alias.
  • RF and estimated carrier frequency.
  • Mode and alternatives.
  • Conservative evidence class and separate detection, artifact, coherence, modulation, periodicity/framing, information-content, and decode evidence.
  • Counterevidence, plausible alternatives, and recommended next IQ analysis.
  • Filter bandwidth.
  • SNR and noise floor.
  • Occupied bandwidth.
  • Drift and frequency error.
  • Duty cycle and timing pattern.
  • Decoder synchronization, FEC, CRC, and BER where available.
  • Decoded text and structured fields.
  • Recording and export controls.
  • A link to deeper analysis views.
  • A prominent Tune VFO to center / Tune intelligently action that uses the same activation command as double-click, previews or explains automatic changes, reports refinement/decoder progress, and offers undo.

Manual Controls

Manual mode, bandwidth, gain, AGC, squelch, notch, de-emphasis, PPM, frequency, and audio controls must always remain available.

The user should have:

  • A visible Auto/Manual state.
  • One-click return to Auto.
  • Undo for the last automatic adjustment.
  • Pinning of individual settings so Auto cannot change them.
  • Per-mode presets.
  • Per-receiver saved state.

Suggested Desktop Layout

Receiver | Frequency | Mode | Performance | Record

Spectrum with VFO/filter and detected-signal overlays
Waterfall with time cursor and replayable history

Signals in view          Selected signal / decoder output
ranked candidates        evidence, measurements, messages

Manual tuner controls and audio controls

Simplified Mobile View

The platform must provide a deliberately simplified mobile interface, not merely shrink the desktop layout. Automatic scanning is a primary mobile use case, while manual tuning and full signal information remain available.

Mobile Navigation

A suggested compact navigation model is:

Listen | Scan | Signals | Controls
  • Listen: frequency, mode, audio, compact spectrum/waterfall, and the selected signal.
  • Scan: scan plan, ranges, speed, start/pause/stop, progress, detection policy, and action rules.
  • Signals: current candidates, held detections, history, recordings, and decoder results.
  • Controls: manual frequency entry, fine/coarse stepping, mode, filter, gain, AGC, squelch, PPM, performance profile, and receiver selection.

Mobile Auto Scan

  • Large touch targets for Start, Pause, Resume, Stop, Listen, Record, Ignore, and Continue.
  • Quick scan presets plus access to full multi-band scan-plan editing.
  • A prominent current frequency, band, progress indicator, and elapsed time.
  • A detection sheet that can stop on one or several signals and let the user choose which signal to hear, record, decode, inspect, dismiss, or bookmark.
  • Configurable automatic actions identical to the desktop feature.
  • Clear indication that scanning keeps the selected receiver and USB bank awake.
  • Best-effort prevention of screen sleep while an active foreground scan is running, where the browser permits it.
  • Explicit pause/fault indication if mobile browser suspension or network loss interrupts the sample stream.

Mobile Manual Tuning

  • Direct numeric frequency entry.
  • Large fine and coarse -/+ tuning controls.
  • Horizontal swipe tuning on the spectrum.
  • Pinch zoom and drag pan.
  • Draggable filter edges with touch-friendly hit areas.
  • Mode and bandwidth presets.
  • Gain, AGC, squelch, notch, and audio controls in expandable groups.
  • A one-tap transfer from an automatic detection into manual control.

Mobile Signal Information

Signal measurements, classifier evidence, alternatives, decoder output, and recording controls should appear in a scrollable bottom sheet or dedicated signal page. The mobile view must not hide uncertainty or reduce a rich decoder result to only a mode label.

The compact mobile header or Signals sheet must expose the same master Signal detection toggle as desktop. It defaults on, clearly shows paused and warmup states, and must not require opening expert controls.

Mobile Performance

  • Default to Eco or an adaptive bandwidth-conscious profile.
  • Allow Balanced or Analysis mode when the phone and network demonstrate that they can sustain it.
  • Reduce waterfall resolution or cadence before compromising audio.
  • Avoid hover-only interactions.
  • Preserve state across portrait/landscape changes.
  • Treat foreground scanning as the initial supported behavior; background scanning must not be promised until browser suspension behavior is proven.
  • Reuse the shipped PWA manifest and optional rfsentry-client workstation launcher without making installation mandatory. The launcher may protect an active workstation session from Chrome background throttling, but it does not relax browser sandbox, TLS, origin, or site-isolation boundaries.

Responsiveness and Accessibility

  • Desktop-first design with a considered tablet layout.
  • A purpose-built simplified mobile layout is required.
  • Certificate onboarding is the first purpose-built mobile surface: /trust/ detects the form factor/platform, prioritizes Android or iPhone/iPad steps, supplies large touch targets and preserves equally deliberate desktop paths.
  • Color-blind-safe palettes and status indicators.
  • Complete keyboard control.
  • Reduced-motion support.
  • Screen-reader labels for controls and decoded events.
  • No use of color as the sole indication of state.
  • Avoid main-thread work that can disrupt audio.

UI Performance Targets

  • Immediate response to pointer and wheel input.
  • Smooth spectrum pan and zoom at display refresh rate.
  • Stable waterfall cadence under normal DSP load.
  • No growing queues or memory use during a long session.
  • Audio must take priority over animation.
  • Detailed analysis panels may reduce their update rate before the primary tuner becomes less responsive.

Acceptance and maintenance

The receiver roadmap tracks automatic scanning, and the client roadmap tracks the simplified mobile workflow. Both remain deferred. Full keyboard coverage, screen-reader navigation, color-independent cues, touch controls and reduced motion still need representative interaction tests.

Use the validation contract, not a passing stylesheet build, to establish UI quality, continuity or measured frame pacing. Keep display refresh separate from evidence acquisition and preserve audio, manual tuning and event retention while optional panels update less often.