I have some great clients that enable me to play around with tons of interesting new stuff like the Magic Leap One. It’s great because you get to take a look at the latest and greatest but it can also suck pretty hard. It can suck because new stuff mostly does not come with instructions or those instructions were a “TBD” on the backlog. Yea yea, it seems like I am just whingeing about nothing but it’s easy to forget how frustrating a crash with no feedback is. This speaks volumes to the quality of SDKs being produced nowadays and of course, to that wonder that is the internet.

With moving some of our demos to the Magic Leap One, it was a mixed bag. Getting up and running was easy peasy! Beautifully documented with precise easy to find instructions. We had the device so no messing around with simulators.

A few things to note:

To get a certificate for deploying to a device, you will need a DUNS number (DUN & Bradstreet) If you have ever published stuff as a company on iOS, you should already have it. Good news, unlike the Apple App Store, approval was a couple of seconds. I have been told you can get a temporary certificate from Magic Leap but how and where I have no idea.The device takes a little bit of time to be found by the deploying computer. Before deploying your app, you will need to use the Magic Leap console, mldb, to check for devices. Command “mldb devices”…