Welcome back to Input Origins, our monthly foray through the evolution of input, from the most popular input methods to the most obscure.
This month, rather than covering another input device, we'll be covering an input method that's been reinvented over and over for nearly a century. It serves as a testimony that the line between HCI and UX is blurrier than you might think.
Series Editor: Ariel Amar
The Rotary Dial in action - each wind of the wheel fires perfectly timed pulses that step the exchange's machinery to your number
How an Undertaker Invented the Dial Phone
Let's dial back a century, to telephony's first UX crisis. Back in the 1890s, dialing a number meant tapping three push-buttons. Calling 235? Tap the Hundreds-Button twice, the Tens-Button three times, the Units-Button five times. Miscount once, wrong number, and callers miscounted all the time.
And before that? You didn't dial at all! You lifted the phone, a human operator answered, and plugged your call through. Operators had full power to listen in, delay you, or "lose" you. Which is exactly how it all started:
Almon Strowger, a Kansas City undertaker, discovered the local operator was routing his funeral calls to her husband, his competitor! Strowger swore to get even with the telephone operators and "put every last one of them out of a job."
And he delivered.
His 'Automatic Telephone Exchange' went live in La Porte, Indiana, in 1892, no operator required. But the system was prone to caller mistakes by miscounting. So in 1896 his own engineers replaced the buttons with a spring-loaded wheel: the caller wound the rotary to the number, and the spring wound back at a governed speed, firing perfectly timed pulses. Thus, the phone dial was born.
Apple's answer to a thousand button presses - Spin, select.
Spin to Win: Apple's Interface Bet
It was 2001. Steve Jobs had returned to the company just a few years earlier. Back when Apple was mainly selling computers. It was the height of the MP3 boom, countless devices flooding the market, and Apple was secretly planning an MP3 player of its own. During the final iPod mockup meeting, the talented Tony Fadell, recruited weeks earlier to head the iPod endeavor, presented three prototypes, one of which was chosen and became the iconic iPod.
At that same meeting, Apple's Senior VP of Worldwide Product Marketing, Phil Schiller, presented mockups featuring a scroll wheel! Schiller thought of the idea as a solution to the troubling interface problem MP3 players faced at the time. They used 'plus' and 'minus' buttons to navigate menus and songs, one item at a time, and when your player holds thousands of songs, that means thousands of presses just to scroll through a list. Tedious, right? But with a scroll wheel, a quick flick of the finger sailed through the entire library.
The Microsoft IntelliMouse (1996) - The mouse that made the scroll wheel standard.
The First Doom Scroll (Revisited)
Longtime Input Origins readers already know how the scroll wheel was born (Input Origins #17):
In 1993, Microsoft's Eric Michelman noticed how Excel users were struggling with long sheets navigation, dragging the scroll bar endlessly. While dabbling with a solution of his own, a joystick-like lever, he came across a hardware team at Microsoft with the opposite problem: they'd put a scroll wheel on a mouse, but couldn't find a use case for it. A use case with no device met a device with no use case. The IntelliMouse shipped in 1996, the first scroll-wheel mouse.
It's Your Turn to Reinvent the Wheel
Mudra Studio exposes the EMG signals, finger pressure and IMU motion behind every gesture, ready to be vibe-coded into your own project.
None of these three devices actually share any technology with each other. What they share is the rotary gesture. The engineers were not designing machinery per se; they were designing how the control feels. That is UX, decades before the term existed. Often, input technology and UX converge. The line between them is often not that clear.
Which brings us to today.
Now you can define your own input experience on top of Mudra' technology.
Mudra Studio sits on Mudra's SDK and hands you the raw ingredients: gesture detection, finger pressure, neural signals, so you can vibe-code your own way of controlling your devices. You need a Mudra Link device.
Strowger needed engineers. You just need a free afternoon and some coffee. Start vibe-coding your EMG experience with Mudra Studio.
Visit the Mudra Studio page
