Page History

...

{html}<a href="javascript:showhide('design2');" id="design2show">Show this design</a>{html}

{html}<div id="design2" class="hidable">{html}

1) Time-budget centered design

Image Added

Interface assumes that the user only knows how much time they have and which days they are able to use for a visit.

In an effort to shield the user from the daunting task of the astronomically large amount of possible time arrangements, the user only selects three things (a) which day to visit on (b) how much time they have for the visit (c) which things available that day they want to see.

The screen starts out with only 7 cells, one per day, with small icons inside. The icons are not meant to show specifically what is available that day, but to give the user an idea regarding how much is available that day. If the user wants to plan for a future date, or just buy tickets for it, he can. However, this design does not favor that, as we think that due to constant reconstruction, rescheduling, moving, etc. the staff only have a good idea of the upcoming week.

After a day is clicked, icons for all animals, sessions, and exhibitions appear. These don't have words; only pictures. If one is clicked, more information is shown, along with an option to 'checkmark' this item.

Once the user has marked the icons he is interested in visiting, a set of instructions similar to those obtained from Google Maps upon clicking 'Get Directions'. These specifically tell the user when to arrive, when to go where, how to move around the building using visible landmarks (turn right once you see the round shark tank).

Finally, icons for the following options are shown below: (a) Print the plan (b) Email yourself the plan (c) Buy tickets for this date.

Notes: Finding visual landmarks might be too difficult. The interface should let the user know if he choose too many items to see for his time-budget somehow. A very strong idea that came up while we presented these was that distance and estimated walking time should be incorporated into the schedules.

2) Exploration-centered design
Image Added

This interface assumes that the user does not want to think about time, and simply wants to know where things are and how to get to them efficiently (i.e., not going back and forth)

The interface looks like the map found inside the aquarium. There are icons with images of animals on top of certain locations. If the user clicks them, information shows up along with an 'Add' option.

A schedule is kept below the screen and is constantly updated. This schedule does not specify times, simply the order in which events take place.

Arrows are drawn on the actual map connecting the locations selected by the user. These arrows have text displaying the estimated time it takes to walk from point A to B.

The interface takes care of avoiding redundant paths and tries to make everything a loop.

Buying tickets is automatically added to the schedule; if the user clicks the ticket logo, they can buy them online.

This interface assumes that the user is planning (and buying tickets) for the current day.

3) Explicit scheduling

Image Added

This interface assumes the user wants to directly control every aspect of the timing. Instead of choosing a day of the week, the user inputs a date. Instead of selecting the time budget, the user explicitly inputs when he will arrive and leave.

After this information is entered, a list of available sessions, animals, and exhibitions are shown along with 'checkmark' boxes next to them.

The user then begins clicking on the ones he is interested in.

A schedule is maintained below. It is somewhat simple (ordered icons for each visiting event) but also has detailed timed information below it (e.g., buy tickets at 1pm, go to tank A at 1:30pm). The option to buy tickets online is added to the beginning of the schedule.

{html}</div>{html}

...