The tool in your hand
Someone is halfway through a home-improvement job, holding a moisture meter against a wall, trying to read a small analog dial and remember the number long enough to matter. The tool does one thing. It has no memory, no context, no way to tell you whether that reading is high for this room on this humid afternoon. You write it on the back of your hand and move to the next wall. Ryobi Phone Works was built for that person, by turning the phone already in their pocket into the brain of the tool.
The problem

A digital replacement for an analog tool is one wrong decision away from a gimmick. If the app only mirrors a dial on a screen, you have added batteries and a pairing step and taken away reliability. So the real brief was value: use what the phone already has, its screen, sensors, camera, and radios, to make the tool genuinely more useful than the analog one it replaces, at or below the same price.
There was a second, harder problem underneath. Ryobi Phone Works was not one tool, it was eight: a moisture meter, a laser level, an inspection scope, a laser distance measurer, an infrared thermometer, a stud finder, a laser pointer, and noise-suppressing earbuds. Each carries its own decades-old expectation of how it should behave. The design job was to make each one feel native to its own use, and yet make all eight feel like a single product from a single brand.
The system

The move was to off-board the tool. By pushing the processing and the display onto the phone, the physical devices became light, compact, and streamlined, and the app picked up everything a bare tool never had: a timestamp and a location on every reading, a camera heads-up display, typed or voice notes, easy sharing, and a running archive of measurements you could actually go back to.
That reframed each tool. The moisture meter now showed water content against the day’s local humidity, so a number meant something. The distance measurer turned raw length into area, volume, and continuous measurement. The infrared thermometer tracked surface temperature live on a camera HUD. The inspection scope streamed from behind a wall to the screen in your hand. Same measurement, far more context.
The design work

My part sat in the interaction layer, and specifically in the hardest requirement: one UI language across all eight tools. Every screen had to be immediately legible for its own tool, and consistent enough across the set that learning one taught you the next. Shared structure, shared patterns for a live reading, a capture, a saved record, so the app read as one considered product rather than eight utilities bolted together, while still feeling like part of the Ryobi hardware family it belonged to.
The thesis we kept returning to was intimacy. The phone is the device people keep closest, and attaching a tool and a task to it deepens the relationship with that task. Getting that right meant merging the digital interface with the industrial design, honouring the analog legacy each tool came from instead of erasing it.
What it taught me
Ryobi Phone Works was recognised by Core77 in 2015, and I want to be precise about that: it was a team’s work at x cube labs for Techtronic Industries, and I was one of its interaction designers. What it taught me has stayed with every connected-hardware project since. When a product is a system of many parts, the design job is not the prettiest screen, it is the shared language that lets all the parts feel like one thing in the user’s hands.