Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Adaptive Hardware: Context Aware Interfaces (2013)

microsoft.com

Post reply on HN
Print view View original

21–30 of 38 posts

Re: Adaptive Hardware: Context Aware Interfaces (2013)

#21

Post by userbinator »

What I find amusing is that through the series of videos, the "keyboard" slowly morphs from something with plenty of tactile feedback, moving keys, and other "physicalness" to a tactile-less flashy touchscreen thing that I would not want to be typing on for any length of time. Nevermind the fact that the keys can show images that change; to me, a good keyboard is one I can operate effortlessly and comfortably without looking at it.

At the other extreme, there's http://www.daskeyboard.com/

Re: Adaptive Hardware: Context Aware Interfaces (2013)

#22

Post by ethbro »

Here's the question I have. If you have morphing context aware keys, how do you avoid the tragedy of disparate iconography across apps?

I haven't watched much of the material, so pointers welcomed. But "ctrl+s in this app saves" seems preferable to "which icon is save in this app"?

Re: Adaptive Hardware: Context Aware Interfaces (2013)

#23

Post by bdcravens »

ethbro wrote: post #19
abrookewood wrote: post #16

Earlier quoted context omitted.

It's more a case of someone on HN reminding everyone that Apple didn't really 'revolutionise' the keyboard and that everything old is new again. Lenovo did this (adaptive keyboard strip) when they replaced the function keys on the X1 Carbon with something similar to what Apple are doing now. FWIW I absolutely hated it. Edit: Added lenovo.

Mods edited it. I think the date is key. This isn't MS speaking to Apple, just HN reminding us how science gets done.

I also suspect it's drive-by commenting, drawing conclusions based solely on the article title and personal bias.

Re: Adaptive Hardware: Context Aware Interfaces (2013)

#24

Post by userbinator »

arkitaip wrote: post #4

It's a shame that keyboards with programmable key images didn't get more widespread usage beyond Optimus [1]. I currently have a Corsair K95 RBG keyboard and it's programmable 18x3 keys [1] are near unusable because I can never figure out what G1 or G2 does. But if I had programmable key images... [1] http://www.artlebedev.com/optimus/ [2] http://www.corsair.com/en-us/landing/k95-rgb

https://www.engadget.com/2008/02/22/optimus-maximus-at-long-...

The Optimus was also not very comfortable for actual typing use, which probably put off a lot of potential customers.

Re: Adaptive Hardware: Context Aware Interfaces (2013)

#25

Post by matt4077 »

ethbro wrote: post #22

Here's the question I have. If you have morphing context aware keys, how do you avoid the tragedy of disparate iconography across apps? I haven't watched much of the material, so pointers welcomed. But "ctrl+s in this app saves" seems preferable to "which icon is save in this app"?

Apple (used to be) very good about getting developers to adhere to the standards. Failing that, I'm hoping for an intermediate layer where developers expose the actions but users can customize the presentation.

Re: Adaptive Hardware: Context Aware Interfaces (2013)

#26

Post by amelius »

arkitaip wrote: post #4

It's a shame that keyboards with programmable key images didn't get more widespread usage beyond Optimus [1]. I currently have a Corsair K95 RBG keyboard and it's programmable 18x3 keys [1] are near unusable because I can never figure out what G1 or G2 does. But if I had programmable key images... [1] http://www.artlebedev.com/optimus/ [2] http://www.corsair.com/en-us/landing/k95-rgb

Do people actually look at their keyboard when typing?

I think tactile feedback is still the biggest possible feature of a (real) keyboard.

Re: Adaptive Hardware: Context Aware Interfaces (2013)

#28

Post by victornomad »

I own a Thinkpad X1 second generation with a touch bar, its not as sophisticated as this or the new MBP but I really hate it.

It lacks feedback when pressing the button. Trying to find the correct button without looking to the keyboard is quite difficul since the virtual buttons dont have relief. I find it as well quite annoying since moving your sight down makes you feel out of place

If you check online the Thinkpad X1 2nd gen is one of the most hated Thinkpads, because of the touchbar and the trackpad...

Re: Adaptive Hardware: Context Aware Interfaces (2013)

#29

Post by ramblenode »

arkitaip wrote: post #4

It's a shame that keyboards with programmable key images didn't get more widespread usage beyond Optimus [1]. I currently have a Corsair K95 RBG keyboard and it's programmable 18x3 keys [1] are near unusable because I can never figure out what G1 or G2 does. But if I had programmable key images... [1] http://www.artlebedev.com/optimus/ [2] http://www.corsair.com/en-us/landing/k95-rgb

Kind of cool, but I'm trying to think of what this offers over just eye candy. Maybe it could aid key combinations, e.g. pressing the meta key illuminates other parts of the keyboard for completion. Finger DDR, whack-a-mole?

As others have mentioned, looking at the keyboard is generally something to be avoided. The premise for this is sort of a workflow antipattern.

Re: Adaptive Hardware: Context Aware Interfaces (2013)

#30

Post by taneq »

userbinator wrote: post #21

What I find amusing is that through the series of videos, the "keyboard" slowly morphs from something with plenty of tactile feedback, moving keys, and other "physicalness" to a tactile-less flashy touchscreen thing that I would not want to be typing on for any length of time. Nevermind the fact that the keys can show images that change; to me, a good keyboard is one I can operate effortlessly and comfortably without…

I've been using a Das Keyboard Ultimate for the past couple of years, I love the feel of it. I've got the Cherry Brown switches so it's a tad quieter than the full clicky ones, too. They're very vulnerable to liquids, though - one teaspoon-sized splash of water on mine and the 'w' key stopped working. In the end I pulled it apart and swapped the switches around (who uses scroll lock anyway?) and it's fine again, but I was surprised how little it took.
Post reply on HN