Definition
What this measures
Coarse anonymous outcomes reveal where browser-based Bluetooth succeeds and where setup still creates friction.
SupaKewber first-party research
Smart-cube connection success by browser and device
Coarse anonymous outcomes reveal where browser-based Bluetooth succeeds and where setup still creates friction.
SUPAKEWBER PRACTICE DATA
Research question
Which browsers and smart-cube families connect most reliably?
The live dataset will publish a quantified answer automatically after it reaches at least 20 distinct users and 100 eligible observations.
Published results
Aggregate benchmark table
Every displayed cell has passed the public sample threshold. Empty tables are a deliberate “not enough evidence yet,” never a fabricated estimate.
Loading current publication state…
Methodology
How it is calculated
Success is a completed connection divided by completed success plus failure outcomes, grouped by coarse browser, operating system and cube family.
Inclusion rules
What enters the sample
- Eligible SupaKewber observations with valid measurement fields.
- Only aggregate cells above the stated privacy and stability threshold.
Exclusion rules
What is removed
- Deleted, invalid or structurally inconsistent records.
- Small cells that could be misleading or identify a narrow group.
Interpretation limit
What this dataset cannot prove
This is operational SupaKewber telemetry, not a controlled hardware laboratory test. User-cancelled chooser events are excluded.
SupaKewber data describes people who use this platform; it is not automatically representative of every speedcuber. Definitions and thresholds stay attached to every JSON download so the number cannot be separated from its method.
Source separation
This is practice data, not an official competition result.
SupaKewber records browser practice and platform interactions. Official WCA results appear only on separately labeled WCA analysis pages with the required WCA attribution and export date.