...
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. Second, we do not provide actual information about the laundry machines. This step will only be fixed once we have hardware to interact with; in our exploration of the user interface, this component can reasonably remain shallow forever. A final shallow area, and one that also would require some hardware functionality to truly work, is that of planned actions or timed actions. For example, our app says that it can provide a notification "when the next machine is free". Knowing this information - determining when a machine becomes free - is a hardware problem. There is also a software problem; right now, we don't actually send a notification. This is an aspect we could test by setting the notifications to send after a fixed, short timer instead of when an actual timer expires, and this is an aspect which we will want to make some progress on for our next iteration.