BLOKY — Your Workflow Partner

Creative work shouldn't require hundreds of repetitive clicks and constant context switching. Most macropads only map shortcuts — they don't help you stay in flow or switch between completely different work contexts. I wanted one device that understood what you were working on and adapted to it automatically.

Bloky is a creator-focused workflow device with 9 programmable mechanical keys, 3 rotary knobs, and dynamic layer switching that automatically changes the entire keymap based on your active application. Not just a shortcut pad — a complete productivity ecosystem.

The companion app extends the hardware: dynamic layers switch automatically per application, a workflow launcher lets you open your entire toolset with one button press, and an OSD overlay shows exactly what each key does in real time so there's no memorising layouts.

Built end-to-end: RP2040 firmware in C, custom PCB in KiCad, enclosure designed in Fusion 360 and 3D printed in-house, companion app built alongside the firmware. 22+ units shipped to paying customers.

The first PCB had a trace routing mistake I didn't catch until 10 boards were already printed. Scrapped all of them.

Layer switching worked perfectly on my desk. First customer reported it wasn't registering half the time. Turned out to be a debounce timing issue that only appeared under real usage patterns I never tested.

The enclosure fit perfectly in Fusion 360. In real PLA it was 0.3mm too tight and the PCB wouldn't seat. Third revision fixed it.

I underestimated how much time packaging and shipping takes. First 5 orders took me an entire day. Now I've systemised it to under 2 hours for 10 orders.

The rotary knobs felt great in my hands. Three customers said they felt loose. Same hardware — completely different perception. That taught me more about user testing than any course.

The companion app introduced a new failure mode I didn't expect — the layer switching logic that worked perfectly in firmware broke when the app tried to override it simultaneously. Two systems controlling the same state is always a synchronisation problem waiting to happen.

Firmware is the easy part. Manufacturing consistency, customer expectations, software-hardware state synchronisation, and actually getting the product to someone's desk without damage — that's where hardware gets hard.