It's nice that we can start building with the SDK, but I'm more interesting in experiencing what I've made. I'd rather have the device and build a simple hello world demo that inspires me to build more vs spend a bunch of time diving deep into an sdk and while having no idea how the end user will experience the stuff I create. With iOS for example, you could develop a majority of apps by just using the simulator, since the experience is (mostly) 2d. But I remember when starting out, the more fun projects to work on were using the accelerometer. The only way to experience the magic in that case, was with an actual device. With Magic Leap, the entire experience is spatial. So it's probably the other way around where the device is mostly the only way to really understand what it is that you're building.
Yea very strange that they released the SDK and tools without the hardware. How r u supposed to know the ins and outs, quirks, user experience to expect on the glasses without playing around a bit with them first, maybe with a few pre supplied apps by magic leap. I can think of a few reasons, none of them good, to release tools before the platform
I think releasing the developer hardware too early can ruin the whole product launch. People will form their opinion based on the reviews of the devkit hardware and sample apps.
Launching the consumer product without apps is not good either. By launching the SDK early, developers can play around with it. Maybe they can even pick serious and promising apps to some "insider" program and provide access to real hardware.
This is a modern thing which I don't think applies to technology that is (ostensibly) category setting. In the early days of consumer computing, the hardware was released with a handful of supported software that the hardware maker teamed up on, then MAYBE a devkit would come out.
