SupaKewber first-party research

Most common Bluetooth smart-cube connection errors

Validated error buckets show whether unavailable APIs, permissions, GATT state or initialization failures dominate.

SUPAKEWBER PRACTICE DATA

Research question

Why do browser smart-cube connections fail?

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…

Definition

What this measures

Validated error buckets show whether unavailable APIs, permissions, GATT state or initialization failures dominate.

Methodology

How it is calculated

Raw exception text is classified locally into a short approved error taxonomy before the event is stored.

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

An error bucket identifies the observed software stage, not always the underlying hardware cause.

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.

Browse every dataset