Hey there! I'd like to do such measurements eventually, and optimize the firmware accordingly, but only after things settle down. Right now, we still have to bring the modules to market which take priority.

Hey László, Any plans on doing those measurements any time soon? I was reading Dan Luu's article too and would really like to know how my future UHK would compare to other keyboards.

Trevor, thanks for your comments. I respect your preferences, and moreover, try to stay open to the possibility that my own preferences are really inefficiencies, that could be improved.

None of that withstanding, I must say this is objectively not true “There are few to no applications that require regular use of the function buttons”.

I don’t doubt it’s true for the scenarios you work in, but I seen it all the time.

Do you do software development? I’ve noticed one wildcard seems to be how large and how long a person works on a project for on average. I’ve been on the one-project-approaching-os-complexity side for years at a time, but have recently been doing consulting where the projects (or at least how long you work on them) can be much shorter and much more varied. Depth vs. Breadth if you will. That can lead to a preference for what I mentioned, of remapping keys when the efficiency gain is decisive, in order to try and retain speed for multiple environments at once.

It's pretty normal for keyboards to access the function row by holding a function key and pressing the corresponding button on the number row. For example, the pok3r layout which I am typing on. http://i.imgur.com/7ixnajm.png?1

There are few to no applications that require regular use of the function buttons. The design of traditional keyboards themselves cause this: you have to take a hand off of the keys, probably look down, and move it to a different place in order to hit that one function button, then return to position.

If anything, I find that having this layout strengthens my muscle memory, because it allows you to double-dip with the muscle memory you already have for the number row, which you use way more often without looking down. The function keys become more accessible while requiring zero additional space.

Hi Lee,

Thanks a lot for the nice words!

Yes, developers are our primary target market, indeed. The UHK is a 60% keyboard which basically means that it only features the alphanumeric block of regular keyboards. This design results in minimal hand movement at the expense of heavier chording. It's not for everyone, but many people love it. Luckily, I don't have to use other keyboards, so I'm not sure how hard it is to switch from time to time, and unfortunately, I don't know about such statistics.

Eventually, we'll probably release a 80% keyboard featuring F keys, Esc, and the navigation block, but there's no ETA on that one yet.

Hope I could answer your question. Feel free to follow up with additional questions.

First amazingly cool project, it took a lot of creativity, hard work, and guts to get this far, so I’m sure you’ll cross the finish line in good form, best of luck to the team involved.

Now to a dumb question. I assume developers are part of the target market? If so, am I the only one that freaked after realizing there is no row for FKeys? I assume there’s a reason it makes sense, but I’ve only recently discovered the whole keyboard subculture, and Ive ead your faq but couldn’t find anything on the subject.

My only baseless guess, is maybe an obsession with compactness and portability (which does look cool) was rationalized by having the ability to remap all fkeys commands to custom combinations?

If that’s the case, I wonder if I’m in the minority by preferring to deal with the bulk. I travel all the time consulting so keeping minimal mass is important. At the same time I don’t want to compromise, occasionally I’ve even carried large monitors along with me if there is nothing decent on site.

The reason its hard to consider remapping not a compromise is because there are always periods where you have to temporarily use someone else’s keyboard. So if I can be efficient with a standard key combination, I’ll try not to remap it to retain muscle memory benefits when driving someone else’s rig, let alone it’s one less thing I have to train myself on.

Thanks and again best to you.

Hey Dan, We have yet to conduct such measurements. I expect us to rank quite favorably because our processors are fast and our firmware is fully interrupt based. I'd like to write a blog post about this eventually.

I have a question (didn't see it mentioned in FAQs or in the comments to previous blog posts). What's the keypress-to-USB latency of UHK? This question was inspired by Dan Luu's blog post about today's keyboards being significant contributors to keypress-to-screen-update latencies: https://danluu.com/keyboard-latency/

Thanks!