Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Screenshots

          Figure 1                 Figure 2                    Figure 3                  Figure 4                    Figure 5                   Figure 6                  Figure 7

...

           Figure 8                  Figure 9                  Figure 10                Figure 11                 Figure 12                Figure 13   

Design

The final design is composed of 3 main tasks:

...

  • The spinner is implemented using Android's drawing APIs to draw wedges of a circle on a canvas, and draw text on top. The backend keeps track of the amount of rotation applied so far, and drawing is done relative to that amount of rotation. The spin animation is achieved by increasing or decreasing the degree rotation at timed intervals, and redrawing the wheel. A swipe gesture is detected by dividing the screen into quadrants and waiting for a finger-swipe that starts and ends in adjacent quadrants.
  • The victor is determined by precomputing the final wheel spin once the user starts spinning the wheel, and computing which wedge is under the pointer drawn on the screen when the wheel is in its final location. The winner is predetermined so that a user can't game the system by trying to stop the wheel in a particular position.

Restaurant Details

  • Use dice to show rating We use a die (instead of the generic star representation) to show the restaurant ratings and location, which are widely liked like by users (“It’s so cute!”).
  • Use the classical color We use the standard style and style of a hyperlink to suggest that the texts for phone number and address is are tappable.
  • Use We use standard dial activity of Android to place phone calls and Google map Android API

...

  • to pinpoint locations.

Evaluation

We briefed our users with a short description of the application and its purpose, and left it to them to figure out how to use the application. Our users started by looking at the “how to play” screen. After reading the instructions, our first user went to the preference-setting screen, and commented declaratively that that was for setting her (individual) preferences. We did point out that the preference-setting screen was intended for the whole group, but that point may still have been lost; another user (playing the game with the first) never saw the preference screen, and was not aware that there were other options for cuisine and location beyond the three that were presented in the betting screen. We realized that the main “how to play” screen did not indicate that the preference-setting screen was for the whole group; we could add that fact in the text on the “how to play” screen, and/or provide a screen similar to those for transitions between players indicating that this screen is for groups.

...