Yeah I've been consulting this a lot lately. Been writing a data-dense desktop application and trying to make it as good to use on keyboard-only users as it is for mouse-using users.
I figure the closer I get to that, the easier the port to gui.cs will be.
Another good UX book I found was "The Definitive Guide to the .NET Compact Framework" by Larry Roof and Dan Fergus. Yes, it had mostly back-end stuff, but the UX concepts taught the reader to consider his audience.
Is the person using your app likely to be using it in a dock hooked to a full keyboard like you, Mr. Dev?
No, he will be standing next to a cellphone tower wearing gloves and trying to get the Falcon x3 out of the sunlight enough to see what the screen is showing him.
Okay then, make the buttons big enough for a gloved finger to mash, use combo-boxes everywhere you can stand it. So what if its ugly - if its functional and the user never has to use the SIP, then fine.
I figure the closer I get to that, the easier the port to gui.cs will be.
Another good UX book I found was "The Definitive Guide to the .NET Compact Framework" by Larry Roof and Dan Fergus. Yes, it had mostly back-end stuff, but the UX concepts taught the reader to consider his audience.
Is the person using your app likely to be using it in a dock hooked to a full keyboard like you, Mr. Dev?
No, he will be standing next to a cellphone tower wearing gloves and trying to get the Falcon x3 out of the sunlight enough to see what the screen is showing him.
Okay then, make the buttons big enough for a gloved finger to mash, use combo-boxes everywhere you can stand it. So what if its ugly - if its functional and the user never has to use the SIP, then fine.