Our design specifies that our User Interface is for a mobile application. Therefore, we chose to use the Android operating system for our first computer prototype. Android makes it reasonably easy to distribute and debug a prototype of an application.
Our prototype should work on Android 4.0 ("Ice Cream Sandwich"), but it also has backwards-compatibility enough to work on phones as far back as Android 2.1 ("Eclair").
Instructions on using our Prototype
Important: do not rotate the phone while using our prototype. Rotating the phone will cause our app demonstration to refresh, losing conversations and notes that the system ought to preserve. This issue should be fixed by the next prototype iteration.
Shallow components of our User Interface?
Some of the components of our UI are not fully implemented, and will have to wait for later design iterations. These components include storage of previous notes, and user information handling. All of the system state as far as current notes consists of "canned" state for now, because we don't have multiple users or effective preservation of the state they put on the laundry machines. Another shallow component is the inter-user messaging (we don't actually send any messages, just display entered text for now).
In general the shallow areas can be divided into several categories: first, inter-user interactions are shallow in our prototype. We currently only use canned interactions.