When will the UHK 60 Bluetooth development begin? Looking at the process up to UHK V2, it appears that the sales strategy has been targeting professional users rather than general consumers. However, the UHK 80 wireless model seems to have been developed targeting general users. When I examine the UHK user documentation, it’s not written for general users - frankly, it’s unfriendly. There seems to be confusion in the sales strategy.
I’m really enjoying using this keyboard, and I had tremendous expectations for the wireless keyboard announcement, but I was greatly disappointed when I learned it was an 80-key model. Why aren’t you utilizing the original modular concept? Did you announce the 80 model because there wasn’t enough space to put a wireless module in the UHK 60 model? If so, how about putting the wireless module in the wrist rest and selling it that way? The 80 is too bulky.
If this is intended to expand the customer base by targeting general users, I recommend modifying the user manual to make it easily accessible to ordinary people. When explaining macro commands, using as many sample codes as possible would make it easier for general users to understand. There are also some broken explanation links.
Key Points:
Target audience confusion: Product targets general users, but documentation remains expert-level
Size concern: UHK 80 is too large for existing UHK 60 users
Modular philosophy: Original modular concept should be leveraged
Creative solution: Wireless module in wrist rest for UHK 60
Documentation issues: Need user-friendly manuals with more examples and fixed broken links
Suggestion: Either commit fully to general user market with improved documentation, or serve professional users with UHK 60 wireless solution using modular approach.
Note: I am Korean and used translation tools for this feedback. I hope my thoughts have been conveyed clearly.
It’s impractical to make the UHK 60 wireless via modules due to technical difficulties. Our product portfolio will include a 60% wireless model eventually, but I can’t provide a time estimate.
The UHK 80 wasn’t made for UHK 60 users. Rather, we’re expanding our portfolio.
Nobody has told us that your documentation is not user-friendly. What do you mean exactly, and where are the broken links? If you mean the smart macro documentation, it’s a feature set intended for technical users, not general ones, but we have a user guide and reference manual, which will be better integrated with Agent.
I don’t know how I came to refer to it
The link I referred to in the learning is as follows.
I’ve already converted the UK 60 keyboard into Bluetooth and am using it.
However, the disadvantage is that the line connecting the left and right keyboards in the middle cannot be removed and the short battery life is short.
I lie down and type on my keyboard.
I want to use the disconnected keyboard without the wires I’m connecting to.
I know it’s hard, but simply adding an example source to each command description in the user guide will help you understand a lot.
What I felt while going through various trials and errors to implement the desired macro function is that it would have been easier to understand if I had added a simple sample code and explained it.
I still don’t understand this. For example
{|} Braces allow grouping multiple commands as if they were a single command. Please note that from the point of view of the engine, braces are (almost) regular commands, and have to be followed by newlines like any other command. Therefore idioms like } else { are not possible at the moment.
I hope there will be more users using UK in the future, and this is what I wrote.
Please note that the user guide may be because my understanding is different from that of the general public.
I hope you are not using only the LLM to create your smart macros. The LLM you linked to is not provided by Ultimate Gadget Labs. While LLMs can help to solve problems, they also sometimes hallucinate, or their models have been trained with outdated information. So the LLM may give you incorrect answers, or incomplete macros.
I agree with you that more examples on how to use smart macro commands would be useful. Here in the forums a number of users (including me) have posted macros for various use cases (e.g. different ways to detect double-tapping, tapping-and-holding, home-row mods, snaptap, specific ways of layer switching, and more). Also, forum users here are usually quick to offer help with specific questions around smart macros.
We all learned to use the macro engine from the provided documentation, conversations with @kareltucek and trying out commands and gaining experience with how the macro engine works.
As for examples, I feel like it is overloaded with examples, but as its author, I admit I probably don’t see its blind spots due to an “authorship bias”.
I am happy to incorporate specific improvement suggestions, feedback (e.g., pointing at specific paragraphs and writing down what is unclear, what are your thoughts when reading it, where does the confusion stem from), or (the best kind) pull requests.
Until someone picks up the gauntlet, I am afraid you are stuck with community support here on the forum - which you are more then welcome to exploit for all it is worth as we are always happy to learn about new usecase ideas ;-).
