Skip to main content

2 posts tagged with "verify-desktop"

View All Tags
MissedUX / messaging

Radar desktop UX issues: auto-launch, hotspot incompatibility, 4% CPU pulses, macOS/Chrome compat gaps

RadarBetSaracen
radarsaracenverify-desktopcpuauto-launch

Source. April 14, 2026 weekly sync — Installation, Network, and Software Compatibility sections.

The findings​

  • Mobile Hotspot Incompatibility — geolocation verification is unstable when connected via mobile hotspots on Mac + Windows; prevents legitimate wagering.
  • Installation Workflow — access denial during web installation triggers persistent download prompts, regardless of whether the software is already on the system.
  • Auto-Launch — Radar initiates automatically on system startup (Mac + Windows) without consent. Intrusive UX, support load.
  • Desktop CPU — location checks trigger 4% CPU spikes every 10s at 600m from the border. Consistent resource drain — and the closer you get to the border, the more frequent the checks.
  • Software Compatibility — inconsistent Radar performance across macOS Tahoe 26.0.1 vs 26.3.1 and Chrome 146 vs 147. Point releases break the integration.

Why it matters​

Three of these (auto-launch, install prompts, hotspot incompat) generate support tickets. The CPU pulses are not catastrophic but become noticeable on poker tables. The macOS / Chrome version sensitivity is the most concerning — Radar's desktop integration is fragile across the exact version range that most US users sit on.

For BetSaracen players this stacks on top of the existing generic "account security" error messaging (no diagnostic data, high self-troubleshoot friction).

Radar profile → · April 14 weekly sync →

MissedNear borderUX / messaging

Radar / Saracen AR desktop: Chrome-incompatible Verify app + no bet within 1km of AR border

RadarBetSaracen
radarsaracenchromear-borderverify-desktop

Source. March 24, 2026 weekly sync — Field Testing section.
Internal reference. CIV-20: Saracen Arkansas – Radar: conduct full competitor validation

What we tested.

  1. Installed Radar Verify on a Windows laptop and on a Mac, attempted to start a betting session via Chrome on both.
  2. Attempted bet placement from within ~1 km of the Arkansas state line, on a Windows laptop tethered to a mobile hotspot.

What happened.

  • Radar Verify does not work in Chrome — confirmed on both Windows and Mac.
  • No successful bet could be placed within 1 km of the AR border. Radar bounced between "State not Allowed" and "Buffer Zone" errors as the tester moved.

Why it matters. Chrome is the most common desktop browser in the US. Combined with the near-border accuracy gap (no bet within 1 km), this is a double UX + compliance failure on Radar's flagship regulated-sportsbook reference (BetSaracen).

Radar profile → · March 24 weekly sync →