The last post in this week's Kinect for Windows SDK v1.8 theme week is a document that everyone doing any Kinect development should (must?) read and understand...
Developing Kinect application is very different than other kinds. It's not keyboard, mouse or touch. It's something different. Don't reinvent the wheel. Learn from the hard lessons of others. You don't have to start your design from scratch.
This 142 page document will help you hit the ground running and avoid costly mistakes...
Human Interface Guidelines (HIG)
Introduction
Welcome to the world of Microsoft Kinect for Windows–enabled applications. This document is your roadmap to building exciting human-computer interaction solutions you once thought were impossible.
We want to help make your experience with Microsoft Kinect for Windows, and your users' experiences, the best. So, we're going to set you off on a path toward success by sharing our most effective design tips, based on our long-term design, development, and usability work. You'll be able to focus on all those unique challenges you want to tackle.
Keep this guide at hand – because, as we regularly update it to reflect both our ongoing findings and the evolving capabilities of Kinect for Windows, you'll stay on the cutting edge.
Before we get into design tips, it will help to start with a couple of basics: a quick introduction to the Kinect for Windows sensor, software development kit (SDK), and Developer Toolkit, and some environment and sensor setup considerations.
Read more: Channel9
QR: 