Web Bluetooth explained
Web Bluetooth gives a secure website controlled access to nearby Bluetooth Low Energy services after the user chooses a device. SupaKewber uses that access for GAN move data and cube-state updates.
Direct answer
SupaKewber calls the browser’s device chooser after you press Connect Cube, requests known GAN Bluetooth services and starts notifications from the cube. Each decoded turn updates the virtual state, allowing automatic start, solved-state stop, CFOP milestones and live race progress.
Step by step
Use SupaKewber over HTTPS; Web Bluetooth is not exposed to ordinary insecure websites.
Press Connect Cube so the browser is allowed to show its permission chooser.
The browser, not the website, presents the device list and records your choice.
SupaKewber opens the GATT server and selects the matching GAN protocol generation.
Move notifications or polling updates feed the timer, virtual cube and analysis system.
Complete guide
A page cannot silently scan every nearby device. The API requires a secure context, a user gesture and explicit device selection. Permission applies to the chosen site and device rather than granting the entire web open access.
The browser can also block the feature through site settings, operating-system policy or enterprise management. A present Bluetooth radio does not guarantee that navigator.bluetooth is available to the page.
GAN cubes expose proprietary service and characteristic identifiers over the Generic Attribute Profile. Commands, state packets and move notifications differ by protocol generation and may be encrypted.
SupaKewber maps those packets into standard cube moves. Once decoded, the rest of the timing and CFOP analysis logic can operate independently of the underlying transport generation.
A turn event changes the internal 3×3 state and the on-screen player. After the scramble is confirmed, the first new move starts the solve. State checks recognize Cross, first two layers and last-layer orientation.
The final solved state stops timing. Cumulative milestone times are converted into individual stage splits for the result and session averages.
Web Bluetooth support is not uniform across browsers and operating systems. Safari and standard Firefox do not expose the API, and iPhone or iPad Chromium-branded browsers still use Apple’s underlying browser engine.
Connection quality also depends on the host Bluetooth stack and cube firmware. Web Bluetooth is the bridge, not a guarantee that every proprietary cube protocol or hardware revision is supported.
Quick answers
No. The chooser must follow a user gesture and the user selects the device.
Hardware access is restricted to secure contexts to reduce abuse.
It is the Bluetooth Low Energy service and characteristic model used to exchange cube commands and state.
No. The website must implement each proprietary protocol and service family.
Practice with feedback
SupaKewber connects timing, smart-cube telemetry, training and online competition in one browser workflow.
Try Web Bluetooth timing