A handful of open formats and connectivity standards quietly decide whether devices from rival vendors can share data. Their adoption shapes what developers can build far more than any single product launch.

Standards as infrastructure

The most consequential developments in sport technology are often the least visible. A new device launch draws attention, but a widely adopted data standard quietly determines whether that device can work with anything else. Standards are infrastructure: when they are good and widely used, an entire ecosystem of interoperable tools becomes possible, and when they are absent, every connection has to be built by hand.

Two kinds of standard

It helps to separate connectivity standards from data standards. Connectivity standards govern how devices talk to each other at all, the wireless protocols that let a sensor pair with a phone. Data standards govern what the messages mean, the formats and schemas that make a reading interpretable once it arrives. A device needs both: a way to connect and a shared language for what flows across the connection.

Why adoption matters more than design

A technically elegant standard that nobody adopts changes nothing, while a merely adequate one with broad uptake reshapes the field. The value of a standard comes from how many devices and tools speak it, because that is what determines which combinations actually work. Watching which standards gain real traction is more informative than judging them on their design, since adoption, not elegance, decides their impact.

The cost of competing standards

When rival standards split the field, the fragmentation they were meant to cure returns in a new form. Developers must support several, users find that some devices simply do not work together, and the promised interoperability stays out of reach. Convergence on a small number of widely shared standards is usually better for everyone than a proliferation of competing ones, even imperfect standards, if they are common, beat better ones that are niche.

What to keep an eye on

The standards worth following are the ones developers build against by default and that new devices adopt without fuss, because those are the ones shaping what can be built. Their progress is a better leading indicator of the ecosystem's direction than any individual product. This site treats interoperability as a core topic and describes these standards in neutral terms, without endorsing particular bodies, formats, or vendors.