Google Goggles

» see google.com/mobile/goggles as it lived, on the wayback machine

~ the goodbye ~

google goggles shipped on android in late 2009 as a labs experiment, then properly launched on iOS in october 2010 inside the google mobile app. the pitch was simple: point your camera at the world and search comes back. it could identify landmarks by shape plus gps. it could OCR printed text and translate it. barcodes brought up product pages, wine labels pulled up reviews. famously the app could even solve sudoku puzzles from a photo of the grid.

most of these features barely worked at launch. landmark detection was good if you were standing in front of the eiffel tower in clear light, less good if you were in front of a less famous building in shade. OCR was a marvel on flat printed text and a disaster on anything curved. but in 2010, the bar for "a phone app that recognized a thing in a photo" was on the floor, and google was the only large company shipping anything that did this on a consumer device.

i was working on computer vision adjacent stuff by the time goggles became interesting to me, around 2014-2015 when the deep learning wave had broken open and CNNs were finally good enough to do actual visual recognition outside a lab. goggles' early years used hand-engineered features and shallow classifiers. you could feel the seams. the app worked best when you were testing it on the exact categories the team had focused on, and gave up on the long tail. for a CS engineer it was a useful baseline of what was production-shippable in 2010 versus what the field could do once gpus and bigger datasets arrived.

~ the chronicle ~

~ what it was ~

under the hood, goggles was a thin client that sent your photo to google's servers and got a json blob back with whatever google thought was in the image. the on-device side did very little. that was the right architecture for 2010, given how little compute android phones actually had then. it also meant the latency was bad on slow connections, which was most connections in most places.

partnerships gave the app the moments it is remembered for. the metropolitan museum of art collaborated with google in december 2011 so visitors could point goggles at any artwork on display and get the full curator card. for a brief period it was the most futuristic thing you could do at a museum without a special hardware tag.

~ the next chapter ~

iOS goggles got removed from the google mobile app in may 2014, well before the android version was officially killed. that was the first signal the team had moved on. the android app kept getting minor updates through 2018 but no real feature work. google lens, announced at google I/O 2017, was the actual successor: better neural net backbone, integrated into google photos and assistant from day one, with a cleaner UI. on august 20 2018 the goggles apk got its final update, version 1.9.4, with a notice telling users to install lens or photos instead.

looking at goggles in 2026, it sits as one of the cleaner examples of a real product that was ahead of its tech stack. the idea was right. the silicon and the models were not ready for it yet. when they were ready six years later, google did not revive goggles. it just shipped a better version under a different name and let the original go quiet.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »