Determining Activity Requirements

Each screen of the Been There, Done That! application will have its own Activity class. Figure 6.1 shows the six activities required, one for each screen.

A good design practice is to implement a base Activity class with shared components, which we'll simply call QuizActivity. You will employ this practice as you define the activities needed by the Been There, Done That! game:

► QuizActivity—Derived from android.app.Activity, this is the base class. Here, you will define application preferences and other application-wide settings and features.

► QuizSplashActivity—Derived from QuizActivity, this class represents the splash screen.

QuizMenuActivity—Derived from QuizActivity, this class represents the main menu screen.

QuizHelpActivity—Derived from QuizActivity, this class represents the help screen.

QuizScoresActivity—Derived from QuizActivity, this class represents the scores screen.

QuizSettingsActivity—Derived from QuizActivity, this class represents the settings screen.

QuizGameActivity—Derived from QuizActivity, this class represents the game screen.

Scores Activity

Splash Activity

Main Menu Activity

Scores Activity

Game Activity

Game Activity

Settings Activity

Settings Activity

Help Activity

Help Activity

FIGURE 6.1

A rough design of the activity workflows in the Been There, Done That! application.

0 0

Post a comment