Browser compatibility
The smart-cube button depends on Web Bluetooth, not simply whether the device has Bluetooth. Use this guide before treating a missing connection option as a cube failure.
Direct answer
Current Chrome or Edge on supported Windows and macOS systems, Chrome on ChromeOS and Chrome on Android are the recommended choices. Standard Safari and Firefox do not expose Web Bluetooth. Chrome and Edge on iPhone or iPad cannot add it because they use Apple’s browser engine.
Step by step
Use a current stable Chrome or Edge build so Web Bluetooth fixes and permission behavior are up to date.
Hardware access is available on the secure SupaKewber origin, not an arbitrary downloaded copy.
Allow nearby devices or Bluetooth when the browser or operating system asks.
The chooser must be triggered by pressing Connect Cube; it cannot open automatically.
If the platform lacks Web Bluetooth, use keyboard or touch timing without losing access to scrambles and averages.
Complete guide
Chrome documents Web Bluetooth availability across ChromeOS, Android, macOS and modern Windows. Microsoft Edge exposes Web Bluetooth controls on Windows, macOS and Android. These are the combinations SupaKewber recommends first.
Linux support may depend on browser flags and the system Bluetooth stack. Because that environment varies widely, it should be treated as an advanced setup rather than the default recommendation.
Web Bluetooth is not a cross-browser baseline feature. Firefox does not currently ship the API in a normal installation, and Safari does not expose it to ordinary web pages.
On iPhone and iPad, alternative browser brands use Apple’s browser engine. Installing Chrome or Edge there does not create the desktop Chromium Web Bluetooth implementation.
If navigator.bluetooth is absent, the browser does not expose the API. If the API exists but the chooser does not appear, site permission, enterprise policy, insecure context or a broken user-gesture chain may be blocking it.
SupaKewber reports common unsupported states and keeps Manual timing available. A working chooser followed by a device failure should be investigated with the GAN connection guides instead.
Chrome on Android is the most direct mobile option. Enable Bluetooth and grant nearby-device permission. Some Android versions historically tied Bluetooth scanning to location settings, so operating-system prompts should be followed even though SupaKewber does not use location for cube timing.
Specialized iOS Web BLE browsers may expose their own bridge, but compatibility, security model and long-term behavior differ from standard browser support. A desktop or Android Chromium setup is easier to document and troubleshoot.
Quick answers
No. It uses Apple’s browser engine and does not expose the required standard Web Bluetooth API.
Not in a standard current installation.
Microsoft documents support and policies on Windows, macOS and Android, but not iOS.
Yes as a manual timer and learning platform; direct smart-cube pairing is unavailable.
Practice with feedback
SupaKewber connects timing, smart-cube telemetry, training and online competition in one browser workflow.
Check and connect your cube