3 posts tagged with "sdk-release"

Source. June 23, 2026 weekly sync — Competitive Research (Valeria).

What's new​

Radar released a new Web version 5.0.0 and 5.1.0 with a structural change to how fraud signals are delivered:

• Fraud detection moved to a separate, easy-to-use JS module — clients can now opt in and opt out of individual fraud signals rather than taking an all-or-nothing bundle.
• New signal classes called out: emulator detection, screen sharing detection, and an IP check hardcoded to every 30 seconds.

Why it matters​

The modular JS architecture makes it easier for operators to toggle fraud checks — which cuts both ways: faster iteration for Radar, but also a configuration surface where gaming integrations might ship with screen-sharing or emulator checks disabled unless we validate each deployment.

The 30-second IP polling is a concrete cadence we can test against — especially relevant given undetected iOS screen-sharing gaps on Radar deployments this same cycle (Wind Creek PA, CIV-91).

Watch point​

Confirm whether any live gaming integrations have upgraded to Web 5.x and which fraud modules are enabled by default vs opt-in.

Radar profile → · June 23 weekly sync →

What's new. Radar SDK iOS + Android v3.31.0 released April 24, 2026. The notable feature: when Radar's backend is unreachable, the SDK generates geofence entry/exit events directly on the device from cached data, tagged as offline.

It's a backend-toggled feature (Radar's backend enables it per integration), so we don't yet know whether it will be enabled for gaming markets. Tracking intensity also adjusts automatically based on geofence context — even mid-outage.

Why it matters. This is a meaningful step in Radar's strategic direction documented in the Apr 14 weekly: shifting from "where is the user?" to "can we continuously trust this location?" The 3-week-to-2-month release cadence is producing functionality that's interesting in retail / non- gaming contexts but unproven in regulated contexts.

Watch point. We need to validate whether offline-generated geofence events satisfy regulatory requirements (the regulator typically expects a server-side decision and full audit trail per transaction). If Radar enables offline events on a gaming integration, this is a finding worth escalating.

GitHub monitoring. As of Apr 14, we are subscribed to both XPoint and Radar GitHub repos to track new releases, SDK changes, and any publicly visible technical updates going forward.

Radar profile →

Source. April 14, 2026 weekly research sync.
Coverage window. April 2025 → April 2026 (full Radar SDK changelog).

Cadence​

Radar ships every 3 weeks to a couple of months. We are now subscribed to both XPoint and Radar GitHub repositories to track new releases, SDK changes, and any publicly visible technical updates going forward.

Strategic direction​

Clear shift from "where is the user?" to "can we continuously trust this location?" — via four axes:

1. IP-triggered re-validation — location re-checked on network / IP change.
2. Multi-signal decisioning — motion, device context, network alongside GPS.
3. Indoor / vertical accuracy — floor-level detection on mobile plus BLE beacons.
4. Modular fraud architecture — plugin-based, allows rapid new detection logic.

Why it matters​

This is the architectural pitch Radar is making to non-gaming customers (retail, mobility) — and the same plumbing is what lets them say "we're adding compliance signals quickly." Worth watching whether the v3.31.0 offline geolocation events (April 24) are enabled on any gaming integration — that would be a notable regulator-attention moment.

Radar profile → · April 14 weekly sync → · v3.31.0 offline events →