Perhaps this technology could be used to show the irobot with gestures where to retrieve something, where to vacuum (Roomba does a poor job of understanding the layout of a cluttered environment), or even where not to go. It could also be used to model the desired actions at a distance in a hazardous environment.
For comercial apps... how about a sign language interpreter/translator.?
how about being able to control your phone with touchless gestures.
This is opening a whole new line for user interfaces. I think it a good strike MS is making... Apple brought the touch screen interface, MS is bringing the Kinect interface. Is it called 3d gesture controller?
Good question, what will happen to the MS-Nokia alliance? Will it rise? I bet use cases are already being designed.
Later this year Microsoft will announce its own 3D imaging technology that it acquired from Canesta last year. This will be a single chip, owned by Microsoft, that does everything that Kinect does. Kinect is NOT Microsoft's technology, but just licensed from PrimeSense. This is probably behind the non-commercial prohibition. If you want to go commercial, contact Microsoft about its forthcoming single-chip solution.
It's great to have SDKs and standard APIs; it means applications can be developed faster. However, I am disappointed that users will be prohibited from developing commercial applications. This restriction will stifle innovation and productivity.
The move will surely enable wider application. I find the downsizing of Kinect (I can't believe I love downsizing.) being exciting. If a Windows Mobile enabled smartphone can do what Kinect can, who knows what's going to happen to Microsoft-Nokia alliance.
I don't understand the prohibition from making commercial products with this. Sure, hobbyists can have fun, but it seems to me that there's a lot of real commercial potential here.
Can anyone shed some light on that restriction? Does MS have a separate commercial licensing program?
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.