...
In our computer prototype, we did not implement or mock up the ability to delete, rename, or move items within the file browser. While we recognized that these abilities are very important from the perspective of flexibility and safety, we did not think they were the most interesting or unique parts of our interface and left them unimplemented. However, our heuristic evaluators uniformly pointed this out as a major issue. Figure 4 shows our delete and rename affordances, which are revealed when you hover over an item. Clicking on the delete button brings up a confirmation dialogue. Clicking on rename brings up the rename interface, which is the same as the new folder naming interface shown in Figure 3 where the folder's current name is replaced with an input, with the current name selected for pending delete. Clicking anywhere else on the gray highlighted area results in opening the note or folder in question. Taking the screenshots unfortunately got rid of the pointer, but hovering over most of the item has a pointing finger. Hovering over the note or folder icon results in a grabby hand, and you can in fact click and drag anywhere in the highlighted area and drop on any folder or the "Up A Level" section to move folders or notes up or down one level in our file hierarchy. This behavior is shown in Figure 5.
Implementation
After deciding on the webcam-based design, we had to choose which platform we were going to use for our implementation. We all preferred a web app in terms of creating a user interface, but capturing webcam output from a web app proved challenging. We hoped to be able to use the HTML5 getUserMedia API to capture webcam output. However, this is a very new technology -- only in the latest version of Chrome, and only if you enable experimental features. We eventually realized that chrome's implementation didn't have all of the features we needed yet: most importantly the ability to save video, but also the ability to differentiate between webcams plugged in to a laptop to access a front-facing webcam pointing at a lecturer. In the end, we were not able to use getUserMedia to implement live webcam capture for SETENTS, and had to resort to using a pre-recorded video and pretending that the playing video corresponded to a camera live view. This is the implementation limitation that has the single largest impact on the usability of our project, since it can be somewhat confusing having to pretend that a pre-recorded video corresponds to what you're seeing during a user test. And of course, it means that the killer feature of our app is not useful in the real world.
...