Some features started with a simple question. Some experiences became smoother because someone pointed out a detail we almost missed.
Co-creation is not a slogan for us. It happens when real usage is taken seriously, and when we are willing to step back and review the entire setup—not just the product itself.
The stories below are not marketing cases. They are moments where listening carefully led to doing things better.
Featured Stories
These aren’t “success cases.” They’re small moments where listening carefully led to shipping better behavior.
The spec was correct, yet the experience wasn’t. The key was the monitor: two HDMI ports, different bandwidth.
Move the cable to the higher-bandwidth port and 2K at 120 Hz appears instantly.
Lock stopped the image, but the HDMI link still looked “alive” to some monitors.
A firmware update fully shut down the HDMI output—so sleep mode works as expected.
The user expected the KVM to switch to the computer that’s actually running—not just follow a timer.
That question led to a firmware upgrade: switching now responds to device power state.
The device worked perfectly. The sound didn’t. We shipped a firmware adjustment to reduce buzzer volume.
Calmer switching, better focus—small change, daily impact.
EDID simulation can make the OS think a second display still exists.
We added an EDID toggle—so windows return to the active screen automatically.
Keep the display on PC 1, while keyboard/mouse control PC 2—without breaking default behavior.
Not everyone needs it. For those who do, it unlocks a better way to work.
Not always. But every piece of feedback is reviewed carefully and discussed seriously.
Yes. Whether it's a technical limitation or a compatibility concern, we'll explain it clearly.
No. Co-creation is not an event—it's how we work.
Every story above started with one real user and one real question.
Co-creation
Products don’t get better in theory. They get better in real workflows— through real feedback and careful iteration.
Co-creation isn’t about handing decisions to users.
It’s about turning what you notice into product behavior.
If you’ve ever thought
“it should work like this”,
that’s exactly what we want to hear.
