3 ms·

"So many missed opportunities here" is pretty much Google's motto.

by wahsd 11y ago

fixermark 11y ago
And yet they put the platform out at all, which is more than can be said for a lot of other companies out there. It's still the most compact headmounted viewer I've seen, and the fact it runs on Android (even modified Android) and not some off-the-wall one-off OS that you'd have to learn the libraries of from scratch is a huge boon. I still tinker with mine, even though it never lived up to the hype of being something you'd wear all the time.
- ocdtrekkie 11y ago
  Yeah, they heavily gimped the potential of it being an Android device though. Since all of the UI was in a closed, proprietary package, there was no meaningful ability to extend the device. Sure, you could flash a ROM on it, but you couldn't build anything with the Glass UI on such. When I bought it, I figured the ROM community would be able to ensure I could do what I wanted with it, but the platform was too locked down for that to ever really happen.
  - fixermark 11y ago
    I never had a problem developing on it [https://github.com/fixermark/nausicaa]; https://github.com/fixermark/nausicaa]; what sort of things were you hoping it would do?
    - ocdtrekkie 11y ago
      I would've liked to see a lot of things. Glass's biggest strength was notifications, yet I couldn't even use it for on-call notifications from work because it didn't support any email addresses but Gmail (and nobody ever made a third party mail client). The Wear compatibility basically came after I'd already stopped using it, pretty much. I would've liked to see keyboard input from my little Bluetooth keyboard accepted, even Googlers showed it using that keyboard with an Linux install, but there was no significant work on alternate input methods on stock. A lot of situations, voice was fine, but a lot of times it would've been nice to pull a discreet keypad out of my pocket instead.
- jimrandomh 11y ago
  Would've been better to have not been Android at all, actually. As it was, they offered up the usual Android APIs, but only as a trap: as the version numbers ticked up, they broke and removed them. I tried to develop that way, and it was one of the most incredibly hostile development experiences I've ever had.

"So many missed opportunities here" is pretty much Google's motto.

by wahsd 11y ago

"So many missed opportunities here" is pretty much Google's motto.

And yet they put the platform out at all, which is more than can be said for a lot of other companies out there. It's still the most compact headmounted viewer I've seen, and the fact it runs on Android (even modified Android) and not some off-the-wall one-off OS that you'd have to learn the libraries of from scratch is a huge boon. I still tinker with mine, even though it never lived up to the hype of being something you'd wear all the time.

ocdtrekkie 11y ago
Yeah, they heavily gimped the potential of it being an Android device though. Since all of the UI was in a closed, proprietary package, there was no meaningful ability to extend the device. Sure, you could flash a ROM on it, but you couldn't build anything with the Glass UI on such. When I bought it, I figured the ROM community would be able to ensure I could do what I wanted with it, but the platform was too locked down for that to ever really happen.
- fixermark 11y ago
  I never had a problem developing on it [https://github.com/fixermark/nausicaa]; https://github.com/fixermark/nausicaa]; what sort of things were you hoping it would do?
  - ocdtrekkie 11y ago
    I would've liked to see a lot of things. Glass's biggest strength was notifications, yet I couldn't even use it for on-call notifications from work because it didn't support any email addresses but Gmail (and nobody ever made a third party mail client). The Wear compatibility basically came after I'd already stopped using it, pretty much. I would've liked to see keyboard input from my little Bluetooth keyboard accepted, even Googlers showed it using that keyboard with an Linux install, but there was no significant work on alternate input methods on stock. A lot of situations, voice was fine, but a lot of times it would've been nice to pull a discreet keypad out of my pocket instead.
jimrandomh 11y ago
Would've been better to have not been Android at all, actually. As it was, they offered up the usual Android APIs, but only as a trap: as the version numbers ticked up, they broke and removed them. I tried to develop that way, and it was one of the most incredibly hostile development experiences I've ever had.