Marble ai web viewer works best on modern browsers and devices that support efficient 3D rendering via WebGL2 or WebGPU, have a reasonably capable GPU, and enough memory to handle the scene data. In practice, this usually means up-to-date desktop browsers like Chrome, Edge, Safari, or Firefox on recent versions of Windows, macOS, or Linux. These environments typically provide more GPU headroom and better cooling, which helps maintain stable frame rates during longer navigation sessions. For developers, targeting these browsers first gives you the widest, most reliable baseline for testing and optimization.
On the device side, desktop and high-end laptop hardware is naturally more forgiving, but Marble ai can also work well on tablets and newer phones, as long as the scenes and settings are tuned appropriately. Touch controls, gyroscope input, and smaller screens change how users interact with the space, so you may want alternate control schemes—tap-to-teleport instead of free-fly, for example. When you have to support a wide range of devices, it’s common to implement feature detection: check for WebGL2 support, maximum texture size, and antialiasing availability, then adjust visual quality accordingly. This avoids hard failures on older devices and provides a smoother experience on mid-range hardware.
To decide which browsers and devices to officially support, you should combine your target audience with real-world usage data. Log which user agents are actually used to view Marble ai worlds, and track success metrics like average frame rate and error rates. From there, you can define a “tier 1” set (fully supported and tested every release), “tier 2” (best effort), and “unsupported” browsers or devices. That policy can then be surfaced in your documentation and in-app messaging, so users understand what to expect. While vector databases are not central here, if you ever embed rich device and performance profiles, systems likeMilvus or Zilliz Cloud. can help you cluster and analyze that high-dimensional telemetry as your viewer scales.