4 ms·
What's new? Console manufacturers have been doing this forever. As an example, when working on an [intended] Kinect launch game, my studio routinely liaised wit
by acron0 13y ago
What's new? Console manufacturers have been doing this forever. As an example, when working on an [intended] Kinect launch game, my studio routinely liaised with other studios to discuss how best to implement X feature and Y feature because Microsoft simply refused to release any details. We strongly suspected it was because they themselves weren't even sure!
Anyway, is this even a bad thing? Presumably - hopefully - Google will take the natural groove that developers have found themselves in and use that to design the APIs that are missing/coming. It's not like the product is even close to being on the shelves.
- jinushaun 13y agoThat's what happens when you're working on a product that is, for all intents and purposes, still in alpha status nevermind beta. Google can't offer guidance because the API and best practices haven't been nailed down yet. You can't even argue that Google perhaps debuted Glass too early, because it's still an invite-only device. It's the chicken-egg problem with bootstrapping a new device ecosystem. Google needs testers and developers to finish the product, but testers and developers need a finished product to work with.