Andrew Zusman is a user experience designer and blogger. He is a graduate of Netcraft Academy, an institute for user experience education, and a UX designer at Inkod-Hypera. He is an alumnus of Indiana University. Andrew is a native Hoosier, but currently resides in Tel-Aviv with his girlfriend and their dog, Indy.

In ten years, Twine may very well be called a “classic” in sensor design.

Sensor design is a field with little press and incredible importance. Mobile applications often combine a variety of different sensors to create an experience.

An example of multiple sensors creating an experience can be seen in thousands of iPhone apps. These apps combine GPS, accelerometers, and cameras (to name a few) to create unique ways to present materials or provide an experience. One example is a stargazing application that allows users to point their phone toward the sky and see various constellations, even if they are indoors. These types of apps have become so commonplace that few people consider the sensors at work when they use an app unless one sensor is singled out (for example, Waze is clearly based on GPS).

Twine, however, may very well be considered “classic” because it is a physical piece of equipment separate from a mobile device and it uses multiple sensors to collect and send information.

The possibilities for enhanced experiences with Twine probably aren’t endless. Twine has limitations, but it is often limitations that give rise to commonality. If a Twine were considered so common as to be passe in our everyday lives, I believe that the company would consider it a resounding success. It seems as though a small sensor-based piece of standalone technology is just the type of everyday item that could be incredibly popular in the future.