Never tell people how to do things.
Tell them what to do and they will surprise you with their ingenuity.
– George S. Patton, Jr., War As I Knew
In this lab, you’ll continue work on Android and meet with your
Managing the Android Activity Lifecycle
Download and run the Android application specified in this tutorial.
Managing the Activity Lifecycle
Note the following as you work through this tutorial.
- The code provided on Google’s tutorial site doesn’t work
immediately on Studio, so clone our modifed version from this
- You won’t be submitting a modified
version of this code, so there’s no reason to do a fork or to commit/push anything back to Github.
- Make sure that you understand the lifecycle activity diagram and can
find all the code discussed in the tutorial. Answer the following
- Why doesn’t an Android application have a main()
- What does it mean for a state to be static? What static
states are there?
- Does starting the dialog box change the status of the
current foreground activity? If so, how? If not, why not?
- Change the message on the dialog box to demonstrate that you’ve
downloaded the application and are in control.
Save your answers to the questions and collect a screen capture of the dialog
box from the running application.
Working with your Team
Meeting with Your Stakeholders
Following each sprint, your team will meet with it’s peer stakeholders
to discuss your progress. The stakeholders include us and selected members
from other teams. In this meeting, we focus primarily on your project
Participate in the following two meetings:
- as a team member in your team’s meeting with its
- as a stakeholder in your monitored team’s meeting
- 50% — Android
- 50% — Teamwork