←back to thread

Coding without a laptop: Two weeks with AR glasses and Linux on Android

(holdtherobot.com)
677 points mikenew | 2 comments | 14 May 25 15:11 UTC | HN request time: 0s | source
Show context
TuringNYC ◴[18 May 25 00:11 UTC] No.44017964[source]▶
On a somewhat related note, I feel any specialized device development should come hand-in-hand with a great developer experience with a well-designed simulator experience.

I was an original Google Glass developer (2013) and not allowing development via a simulator was one of their biggest mistakes ever. You had to continuously test squinting into the actual hardware. After about 25min it would overheat and you were forced into a cooldown period of about 30min. You couldnt easily put together tests or parallelize testing mundane parts of the app off-device. I ended up with the worst headaches after three months and we pivoted our business to something else soon after.

replies(1): >>44018891 #
1. throwaway314155 ◴[18 May 25 03:53 UTC] No.44018891[source]▶
I mean if you couldn't stand using the device long enough to test it (not that you should have to - i agree on that), maybe the problem was that the device simply wasn't in anyone kind of ready state to be shipped as a revolutionary new way of interfacing with computers. Like christ, it would overheat after 25 minutes?
replies(1): >>44019141 #
2. linkregister ◴[18 May 25 05:09 UTC] No.44019141[source]▶
Being one of the 3rd party developers to create apps for a nascent platform is a great position for your business to be in. It just so happened that Google Glass didn't work out. But imagine being an early developer for Android or iOS.