...
The overall structure of our application is similar to the one we initially envisioned when constructing our paper prototype. It is data-centric, with two dimensions of tabs controlling the information displayed in the main, split-pane interface. A graph is displayed in the top pane, with textual data and related actions (e.g. selling power, changing device settings) available in the bottom pane. Tabs across the top of the screen allow the user to change the source of the data shown: from consumption devices, generator devices, or from the power grid. Tabs along the left side of the screen allow the user to control the time interval for which data is shown. An earlier or later time period can be chosen by swiping across the graph, or by using the date pickers above the graph.images
| | | |
Main screen. The application opens on the Consumption tab, displaying data from the current date in daily view. | Viewing consumption by device. By checking the boxes next to each device, the data relevant to that device is shown in the graph, in addition to the total. | Viewing stored power by device. The Reserves tab is analogous to the Consumption tab, but shows the amount of power being generated rather than consumed. | Scheduling a transaction. The split-pane view allows price data to be viewed in the top pane while a transaction is being scheduled in the bottom pane. |
Design Decisions
- Major initial design decision: parallel data views vs. one consolidated data view
- Paper prototyping feedback: "sell power" button in storage tab for learnability, clearer labels for graphs, naming for device tree and list, draw attention to existing cues such as checkboxes and data snippets
- Computer prototyping feedback: consistency of tabs, meaning of labels (top tabs and device vs. tree view), date pickers, organization/emphasis of important data to make interface less intimidating, legibility and alignments
- Overall tradeoff: amount of information vs. complexity of display; reduced the visual complexity of data by eliminating certain features, e.g. graph aggregation and usage/cost switch
...