We hope you found this chapter to be challenging yet rewarding. You have learned how to take a simple app and make it more intermediate by adding more complex features and code. Each feature, scoring, fling capability, and level requires a lot of thought on how each would work and interact with each other. As you experienced, enabling scoring and leveling mechanisms required us to alter code in a variety of block locations. Similarly, we had to reexamine how our buttons functioned and reprogram the buttons. You will discover that this is a typical process in coding. Changing or adding one thing requires reevaluating how other things would work and interact. Also, this chapter demonstrates how much thought needs to go into planning an app. Earlier in this chapter we decided to update our Label from Score to Score_Level_label to reflect that it would be displaying the Score, Level and Game Over. If you don't take sufficient time to map out your app design on paper initially, then you will most likely end up having to do more re-working than you may have anticipated. Most programming efforts require coders to do some troubleshooting along the way, so don't be discouraged if you find that your app building includes many rewrites. But, you can avoid grand overhauls by really thinking through each aspect of your app's features ahead of time.

In the next chapter, we will begin working on an intermediate app, an event app to plan events, parties, or meetings.