As you are well into the latter half of this book, you have already been exposed to many techniques for designing and building activities. You have a firm grasp of the activity lifecycle and the callbacks triggered at various points as an activity starts, waits, pauses, and ultimately ends. Most of the example applications shared to this point have consisted of but one, single activity. How does that align with the comments I made at the start of the book that activities are cheap to create, use, and dispose of and that you should be prolific in your use of them?
I’m glad ...
