My colleagues have heard me say this several hundred times over the last few months. They have taken delight in the different search terms I have had to come up with; partly to test the glassware, but also just to entertain them. It’s rather liberating to talk to yourself at your desk, despite the ridicule from your colleagues.
Of course, you can also scan a barcode: “Ok Glass scan a product”.
We started this experiment in June last year. We had a prototype working, and filmed a conceptual video about how customers might use the glassware. Since then, it has changed substantially, although the principle functions remain. We have refined and shortened the user journeys and also clarified the experience to make it consistent with the Glass design patterns.
If you are already a Glass wearer, you should find the experience very familiar and you can try the glassware out. As this is a very early experiment you can only add items to your basket and view nutritional information, but it’s enough to give a sense of what it would be like to interact with Tesco on this type of hardware.
From a developers’ perspective, working with Glass has been a joy. The updates to Android Studio that have made Android development more accessible all apply to Glass development. The Glass Development Kit (GDK) documentation is good and getting better. The community is helpful and proactive about sharing knowledge, especially on stackoverflow. The Glass team at Google does all they can to try to make sure the glassware delivers the best experience possible. This is a challenge given how Glass is still being developed, so it can be somewhat of a moving target. The Glass software platform went through 6 updates in the time we worked with it, which shows how much Google is still investing in the platform.
Given the steady flow of software updates, and the various articles that have been published alluding to updated Glass hardware, I can’t help but feel this is still the beginning of the journey for Glass and for Tesco.