Nifty device, held back by execution
For starters, this thing is really great. I spent a good chunk of time feeling it out and setting it up for my use case, and that was a generally painless experience other than the fact that you MUST use a Chromium browser to do so (-1 there).
After a couple days using it, though, there are some problems beginning to show: the only thing that works well is simple "clicks" and that feels nice by itself. If you bind anything to require holding, including the default "scroll" binding, there is a noticeable delay before the device decides you are holding the button.
Let's say, for instance, you track over to a window and then want to scroll: you'll hold the scroll button and move the wheel, but there's a maybe 200-300ms delay between when you start holding the button and it starts detecting that it's held. Meaning your cursor will move before it decides you do intend to scroll.
Need to click and drag, say, to reposition a window? You'll have to step through that process in a clunky way or the cursor will move off of what you want to drag. This is a huge let down if you want to select some text: I'm constantly missing the first character because the device doesn't handle this well at all.
This compounds with anything like chords you might configure: in my case, I set a 2-button hold to enter gesture mode, with some useful stuff behind that. It's practically unusable, though, without slowing me down because I have to wait a beat before I enter a gesture since it doesn't think I'm "holding" the buttons yet.
There is no way to configure this in the software, either. Which, again, requires a specific browser family to even work in the first place, and they offer no install. Support is an AI chat bot that doesn't seem to recognize this product even exists.
So that's not great. I'm not happy with my purchase until they do something about the software and firmware, and put a real human somewhere in the loop.
