Itimpi - to your point, yes that’s right, new features like tap for sticky CTRL will be implemented via the updated infrastructure code, which we’re working on right now.
Pinky Ctrl-A to support legacy editor styles, like the emacs case discussed above, is one of the user requests for specialized use-cases. It’s a good example of why we invested more to expand the software infrastructure.
For general release, we have to make sure there’s plenty of capacity in the code footprint to quickly accommodate any needs that emerge as the installed base grows. That user base will quickly increase a thousand-fold. As we start releasing high volume, staff is typically very busy the first few months. We won’t have a lot of bandwidth to focus on fine needle-threading then, so it’s wise to resolve any of this kind of stuff in advance. Just to be clear, while there’s a ton of cool feature ideas from users, we’ll get to those after GR. Right now, our focus is only on what might interfere with a reasonably common use case. That’s what’s important to settle upfront.
Pinky CTRL is a good example. This didn’t stand out to us initially, but it’s warranted. Here’s the scenario -
Emacs users are experts at using CTRL with their pinky to access editor shortcuts. Even though all 6 right and left modkeys are supported on TextBlade, some emacs users want to use the same location that they’ve long used - installing CTRL in place of caps lock, next to the A key. So we had to provide them a way to do this.
The operative phenomenon here is that once users get to like the upsides of TextBlade, they tend to want the same experience on each of their other platforms. Even if only a rare one of their use-cases may need something extra, if they hit that case, it sticks out.
In essence, if a picture looks say, 95% perfect, we tend to stare at the missing piece. It’s in our nature - we’re wired to notice exceptions. The more complete the puzzle, the more obvious the piece that’s needed. For most users, we’ve already cleared this gate, and the picture is complete. They can do anything they did before, and better.
But for a few users, there are some things they need to facilitate one of these less common use-cases, so we’ve been responding with firmware updates. That’s why we just published the new cloud map that’s built for emacs users.
This same user psychology phenomenon - “OK, I like this. Now I need another thing too.” - this plays out in parallel with the hardware accessory ecosystem. Users get to liking TextBlade in their main location, and then want to use it in other locations - not just a desk or table or bar, but on a couch, easy chair, or even bed. And with lots of different screens, with all their different case sizes. Users have told us they really want such an accessory, and some have even improvised devices on their own. So it’s beyond just a casual want, and has evolved into more concrete demand. We couldn’t find anything on the market that did the job, so we built it from scratch.
We’re now testing some of these new accessories with users. They’re not announced yet, but we’ll add them to our store after GR. It’s sort of surprising how useful they are, and how they facilitate adoption in completely new uses. Kind of exciting to see this ecosystem organically taking shape. Thanks for all the great input from our customers.
Hope this insight is helpful.