From CS 160 User Interfaces Sp10

Jump to: navigation, search

Application author: KOVACS,ARPAD Q


Welcome Screen

8. Aesthetic/Minimalist design:

The button for "1: Planning your Trip" and the "Continue" point to the same place. Also, the tabs (1,2,3) have the same functions as above. There is redundancy in the choices available to the user each time they see the welcome page. This clutters up the page and makes the app seem intimidating with so many options, and is also misleading. Rating: 2, It's mostly a cosmetic problem, with high frequency but low impact and is not persistent: the user can overcome it when they realize there is only three pages.

The buttons and the tabs are redundant.

Planning your Trip page

3. user control and freedom:

When choosing a station, the user can't dismiss the scroll wheel if the station they've picked is already chosen. Also, when the user scrolls to the station they want, the wheel disappears, instead of asking them to "confirm", thus they have to make their decision in one "sweep". Rating: 4, it is a high frequency violation, persistent, and hard to overcome since the users can't take their time picking a station.

You can't dismiss this scroll wheel, nor does it persist after stopping at a choice.

5. Error prevention:

The user can put in the same station for origin and destination. The app seems to default to Daly City/Oakland 12th street. Rating: 2, it's an infrequent problem since users would only enter the same station by accident, and they would notice if the trip plan is different from what they entered.

It's possible to put in the same station for origin and destination.

7. Flexibility and efficiency of use:

The user must pass through the "Buying a ticket" tutorial, even if they already know how to do it. Rating: 2, it occurs with high frequency (on each trip plan) and is high impact (wastes their time), but is not persistent since the user can habituate to scrolling to the bottom of the screen.

This page is very long and you need to look at every time.

Buying a Ticket page

1. Visibility of system status

The user can't tell where to scroll down(obscured by tab bar). Users see the tutorial screen and don't know where to go next. Rating: 2, the user is misled the first time upon using the app, but once they realize they need to scroll down to access more content, they aren't likely to make the same mistake.

It's not clear that I have to scroll down here.

2. Match between system and real world

The button on buying a ticket page has the label "Next". "Next" has ambiguous meaning (it should say that they are being brought to the train schedule page) Rating: 1, the user can overcome it since there are no other options, so it is low persistence and impact.

It's unclear what "Next" means.

Finding which train to ride page

1. Visibility of system status

Time isn't reflected in actual schedule. It's not clear that the given train schedule matches the input time. persistence: can't really overcome, without understanding how system works Rating: 3. The user wants to confirm that the schedule given to them matches their input each trip, so it is a high frequency violation, and it is high impact and persistent since they must know the information and can't overcome it without understanding how the time matching is implemented.

It's difficult to verify that the given schedule matches my time input.

10. Help and documentation

There's too much help given on the Train schedule page, and too many words obscure the actual data for train departure time. Rating: 2, the violation occurs with high frequency, but the problem is not persistent since users learn to "pick out" the relevant information from the layout.

We have to look at this each time.

7. Flexibility and efficiency of use

Scrolling is confusing: Trying to scroll the time wheel scrolls the page, and it's not clear which area scrolls what. This might be better on the actual iPhone device. Rating: 4, it seems impossible to scroll just the time wheel by itself, so users essentially can't change times: this is a very frequent and high impact violation.

Trying to scroll the wheel scrolls the page.

8. Aesthetic and minimalist design

The time chooser is very fine grained, at the minute level: this makes selecting a particular time tedious. It could be improved with 15 minute blocks. Rating: 3, since users frequently need to select a time, and this problem can't be overcome in any way other than becoming really good at scrolling the time.

The time input is too fine grained.

2. Match between system and the real world:

There's an "update" button below the time chooser, but it isn't clear what is being updated. The users expect that the schedule is automatically updated with a choice of time, and this expectation is violated. Rating: 2. The problem happens frequently, but users can overcome it since they habituate to hitting the update button before the schedule is displayed.

I'm not sure what "Update" does.

2. Match between system ahd the real world:

The title "riding the train" misleading: page is not about riding the train, but choosing the right train to board. Rating: 1, users may only be confused once, and it does not affect their use of the app.

The page is about train schedules and not about how to ride the train.

9. Help user recognize errors

The train scheduling page is filled with default origin/destination, and can be reached without the user selecting start/destination input. Rating: 2: a one time problem that is overcome when users learn the page flow.

I didn't input this.

4. Consistency and standards

The "Things to do at" button exits application - this is misleading. Buttons around it all stay within application, but this one points to a browser. Rating: 1, once users learn that the button moves them out of the application, they will be aware of it on future occasions.

Suddenly i'm in the web browser.

4. Consistency and standards:

There is a button labeled "new search", but it is not clear what we are searching for. It's directly below the "Things to do at" button, so users may suspect it is to search for things to do. In fact, it is to search for a new train schedule. Rating: 2, users overcome it once they learn the meaning of the button.

This button is called "New Search" (it's also not visible here without interacting/bouncing back).

6. Recognition rather than recall:

The user's input origin/destination are in paragraphs of text, and not displayed in a tabular manner. Thus, the user must either remember where they were leaving or going to, or dig through the paragraphs of text. source/destination hidden in text. need to remember what stations you put in beforehand. Rating: 2, it is a frequent problem and users cannot get their information at a glimpse, but users can habituate to looking at the right place for the origin/ destination stations.

The origin/destination is hard to find in text.

1. Visibility of system status:

The button for "New search" is obscured by tab bar. Users who want to search for another route have trouble hitting the button. Rating: 3, the button can be accessed by "sweeping" the page up and then clicking immediately: it's a frequently needed task, so this is frustrating and hard to overcome.

The New Search button is obscured.

[add comment]
Personal tools