This book suffers from one major flaw: it slings code at you without bothering to explain what the code does. A good example of this is the main layout screen for sudoko in chapter 2. The author tells you that there are a few different layout containers that determine how user interface elements are laid out, and even goes so far as to give a basic run down of how each container places objects contained within them, which is nice, but then just slings a section of code at you that represents your main screen layout, without any further explanation as to what any of things you're typing actually mean. Another example is the settings menu example. It gets to the point where everything is just here type this and this is what happens.



The nice thing about the book is that you go from a to z in the creation of a complete game, but you're really going to need to keep the api docs and dev guide from [...] open so that you can use them to decipher what the author has you doing.



Don't go near this book unless you are comfortable reading api docs.