Browser & Device Support
Which environments the BRNDTS Ads SDK supports, what happens in unsupported ones, and how to handle them gracefully in your integration.
Support tiers
The SDK defines a three-tier compatibility matrix. Tier 1 is fully covered by the automated test suite. Tier 2 receives best-effort support. Tier 3 environments are detected at startup - the SDK exits cleanly without touching the video player.
- Chrome
- Edge (Chromium)
- Firefox + ESR
- Safari 16+
- iOS Safari 16+
- Opera (Chromium)
- Samsung Internet (Chromium)
- Brave (Chromium)
- Chrome on ChromeOS
- IE 11
- Legacy EdgeHTML (pre-Chromium)
- UC Browser
- Old Android WebViews
- Smart TVs & non-standard runtimes
Required browser APIs
The SDK checks for these APIs at startup - before any network call, feature-flag check, or DOM work. If any are missing, ready resolves to false.
| API | Used for |
|---|---|
| WebSocket | Real-time ad signaling - no polling fallback |
| ResizeObserver | Responsive ad container sizing |
| HTMLVideoElement | Video player integration |
When any required API is missing, the SDK logs a warning to the console:
Handling unsupported browsers
On an unsupported browser, await ads.ready returns false - the same signal as a connection failure. No extra handling needed beyond the standard ready check:
What happens on an unsupported browser
await ads.readyreturnsfalse- No exception is thrown
- No network requests are made
- The host video player is unaffected
Tested devices
Tier 1 coverage across the most common form factors.