...
Originally, we represented our data in the form of Figure 2.1. Several users had trouble deciphering this graph. It was supposed to represent other people traveling to a similar location during a similar time range. In order to make our design more simplistic and consistent with the real world, we decided to change the data representation page to map, seen in Figure 2.2. (Later we would combine this map page with the first map page where users enter their destination information.)
Figure 2.1. Users found this interface because people are not typically represented as line graphs in the real world.
Figure 2.2. The new interface allowed users to adjust the radius from their destination as well as the date range.
Calendars and Map
We also decided to place the calendar and map on the same page for the sake of simplicity and consistency. During paper prototyping, we had a sequence of three pages: an initial map page to enter a destination, a calendar page to select a date range, and a summary page with a map to display other people traveling to a close destination within the same time range. The summary page's map was slightly different from the map on the first page because it had adjustable bars to change the date range and change the radius. For many users, they were confused by the two really similar but slightly different maps. They also could not see direct feedback as they were setting their traveling dates and destinations. As a result, we decided to place the calendar and map on the same page. Moreover, we decided to discard the adjustable bar for dates and instead allow users to adjust their date range directly on the calendar. The radius adjuster was kept.
...