I am writing a game for Android. My graphical interface has the following main screens (i.e. Information and interactions necessary for each of them occupy the entire screen):
- Main menu (let you start a new game, enter the settings, see the results, view the screen)
- The screen of the game in which the game is playing.
- Settings
- Screen of high marks.
- About the screen (i.e. captions and back button)
- Game behind the screen (arrived when the game ends)
- Pause the screen (pauses the game and can access the settings)
The following are some examples of transitions that the user can make between these screens:
1-> 2-> 7-> 2-> 6 (starts a new game, pauses the game, returns to the game, finishes the game) 1-> 5-> 1-> 4-> 1 (view the screen, return to the main screen, viewing the results screen, returning to the main value)
I'm really confused when you only need one action that switches layouts and when you need to create new activity classes. For example, when my game loads, I have a “main” action that loads the layout of the main menu. When you click the settings button, I launch the “settings” action (which uses the graphical interface of the standard Android settings). At the moment, when you start the game, I switch the layout of the "main" to the layout of the game screen (which simply contains one large view on the surface). I'm not quite sure what the best way to integrate the game through the screen, top-rated screen, screen, etc.
. . , , . , . , .
- ?