DEV Community

fluidwire
fluidwire

Posted on • Originally published at fluidwire.com

Why Is Bluetooth Called Bluetooth?

Every day billions of devices whisper to each other over Bluetooth: earbuds, smartwatches, fitness bands, car stereos, and a growing ocean of Internet of Things sensors. Yet almost nobody stops to ask the obvious question. Why is it called Bluetooth? The answer is one of the best naming stories in tech history, and it starts more than a thousand years ago in Scandinavia.

A wireless standard named after a Viking king

Bluetooth is named after Harald "Bluetooth" Gormsson, a 10th-century king of Denmark who also brought parts of Norway under his rule. According to the popular account, his nickname came from a dead or discolored tooth that looked dark blue. His real historical claim to fame was unification: Harald pulled together warring Danish tribes into a single kingdom and helped convert them to Christianity.

That theme of unification is exactly why his name ended up on your phone. In 1997, Intel engineer Jim Kardach was helping lead an industry effort to create a single short-range wireless standard that could replace the tangle of incompatible cables and proprietary radio links between devices. Around the same time he had been reading about Viking history. The parallel was irresistible: just as King Harald united fractured tribes into one realm, this new radio standard would unite fragmented communication protocols under one banner. "Bluetooth" was proposed as a temporary codename.

The codename that never left

Codenames are supposed to be thrown away before launch. Marketing teams reportedly preferred alternatives, but the industry consortium could not agree on a polished name in time, and "Bluetooth" had already spread through the engineering community. By the time the technology shipped, the placeholder had become permanent. It is a good reminder for anyone building a product: the name you use internally has a way of escaping into the world, so choose it with care.

The logo is a Viking bind rune

The story hides in plain sight in the logo too. The familiar blue Bluetooth mark is a bind rune, two Younger Futhark runes merged into one symbol. It combines the runes for Harald's initials: Hagall (equivalent to H) and Bjarkan (equivalent to B). So the little icon on your headphones is literally the monogram of a Viking king who died over a thousand years ago.

Why the name still matters for IoT

The unification idea baked into the name turned out to be prophetic. Modern Bluetooth, and especially Bluetooth Low Energy (BLE), is now one of the backbones of the connected-device world. BLE was designed for exactly the constraints that define IoT hardware: tiny power budgets, coin-cell batteries that must last months or years, small data payloads, and short range. That is why you find it inside wearables, medical sensors, asset trackers, smart locks, and countless industrial monitoring nodes.

For anyone prototyping an embedded product today, Bluetooth is often the fastest path from a breadboard to something a phone can talk to. Popular microcontrollers like the ESP32 and the Nordic nRF series ship with BLE radios built in, which is why so many thesis projects and startup prototypes reach for them first. Understanding which wireless standard fits your power, range, and bandwidth needs is one of the earliest and most consequential design decisions in any IoT build.

From Viking king to connected device

The next time your earbuds pair automatically or a sensor quietly reports data to your phone, remember that the technology carries the name of a king whose whole legacy was bringing scattered pieces together. It is a fitting mascot for a protocol whose entire job is to connect things that would otherwise never speak.

If you are designing a Bluetooth or BLE product and want help taking it from silicon to cloud, get in touch with Fluidwire. We build IoT and embedded systems, and we are based in the Philippines working with teams worldwide.

Top comments (0)