Learning Android [ペーパーバック]

Learning Android is a very nice tour through developing Android applications. It's aimed at programmers who are comfortable with Java already, and doesn't waste any time getting into what's different about Android programming. If you're looking for a guide to save you a lot of time getting from "absolute Android beginner" to "comfortable consulting the API documentation on your own", I think Learning Android is quite a good choice.

Most of the book is devoted to incrementally developing a simple Twitter app. Whether you like or dislike this style of exposition is something of a personal preference, but I will say the chapters are chosen pretty well, and aside from the obvious fact that later chapters assume the code from the previous ones, I never found myself needed to flip backwards a lot, which can sometimes be a problem with books that try to develop a single application over a few hundred pages.

I think I'm probably representative of the target audience for this book. I have quite a bit of experience programming in various languages, and I'm an experienced iOS developer, but with no real prior exposure to Android programming. For me, the book was nearly ideal. I was able to breeze through it pretty easily while getting a very good basic overview. It's certainly targets Eclipse and the associated Android tools that go with it, but the book was generally careful to also at least show the actual files that were generated. As an emacs user who was going through the book using only the Android SDK tools, this was a helpful touch. One minor disappointment is that while the book does a nice job of explaining what Eclipse is doing so that you may do it yourself, it doesn't always provide much coverage of the Android SDK tools or how you would use them to accomplish the same tasks. You can generally find that information elsewhere, but going only by the book, you might sometimes think, "OK, so I need to create this XML file. I guess I can just type it in, but is there an SDK tool that generates the skeleton or do I just do it all by hand?"

In terms of formatting, all the code samples and other text resources such as XML files were presented very nicely. The samples are annotated with footnote overlays that point you to a fuller description of important lines or content that has just been introduced. I noticed very few errors, either in code or in the text, and those I did see were typically minor annoyances rather than issues which change the meaning of a passage.

My overall impression of the book is that if you have a reasonable amount of experience with Java, you can quickly get up to speed with quite a bit of what you need to start targeting Android devices using this book, which for my purposes, made it nearly ideal.

Developing Android based application is like any other development. You have to get tools, learn basics and explore the details of the API. Learning Android covers first two topics.

First of all, you can get the overview of Android, what it does, who develops it and so forth. You can call it an overview from 9K feet height. After that you are explained how Android is organized and how all the system layers are organized. This is quite useful part because you can get the feeling what to expect when it comes to the API. Then you will be guided through the initial setup that allows you to develop Android based applications. This part is quite useful, because it allows you to get all the information required for preparing development environment. You will be, literally, lead step by step how to configure everything (at this point you can tell that Marko has some experience when it comes to providing people with tutorials - you are simply not able to go wrong here). One remark here. Marko doesn't mention that you have to set-up Android's SDK location before you proceed with "Hello world" example. In order to do this, you have to go to: Eclipse -> Preferences -> Android -> SDL Location and set proper SDK location. He also forgets to mention that after setting up ADT you have to go to: and install all the packages that are required for Android development.

After you are ready to go with coding, there is a place for getting familiar with Android's API. Here, Marko provides you with information related to Various aspects of Android related development. In general, it's fine, but there is one drawback. Marko tries to provide you with the knowledge related to Android by conducting you basing on hypothetical application (Yamba). It means, that through out the book you will be hooked to this application and you will try to approach it from various perspectives: UI, database, services, etc. This kind of approach ha it's pros and cons. Pros are that you can get the feeling of real application being developed using technology you are interested in. Cons are: you are stick to example project through out whole book, you can't jump between topics without the overview of the example of application. I generally prefer "Cookbook" series where you are presented a solution for particular issue.

What I have missed most in this book are: HTTP communication within Android apps, Web Service calls within Android based applications, description of Android Market.

In general, this book is OK, but definitely not perfect. I missed lots of topics to be covered here. On the other hand, it has quite well prepared introduction to Android, initial set up and Android's basics. This way, you are provided everything that allows you to start developing Android applications.

Stay tuned, I will update this post as soon as I read some other books on Android. I'll tell you then, whether this book can compete with others or not.

Learning Android by Marco Gargenta is what I would consider a high level introductory book for those well grounded in Java or have a strong OO development background and don't mind coming up to speed in order to learn Android. If you like to learn by building out non-trivial applications in a style that mimic's real world development then consider this book.

I have been writing Java code on and off since Java was considered one of those fringe languages for those a bit off kilter OO types. I also have a style of learning that is not book oriented. I seem to prefer the ad hoc "random walk in the woods" approach. Good for discovering a lot of interesting stuff, not so good at getting a well oriented systematic approach to developing in new areas. When Learning Android by Marco Gargenta was release I decided to have a go at a more direct approach. Since I had been developing in Android for several years this was not my traditional behavior.

The book is well suited to those with a solid Java background. Needless to say if you have a strong OO background and have developed in OO languages you will not have a problem, but I recommend you have a strong Java book at your side and a willingness to spend time in the Java references to get the most out of the book. The book covers a lot of ground and is defiantly not a "now push this button" style book.

The preface mentions that the book evolved from years of the authors teaching Android in Bootcamp style classes. This shines through in the book with little snippets of knowledge that pop up at the right moment, almost anticipating reader questions and not relying on the reader to research the issue. This is obviously the byproduct of teaching many classes and occasionally watching students flail.

The theme of the book is to incrementally evolve a "twitter like" application. Not my favorite domain but very enjoyable and an excellent vehicle for covering a lot of Android functional ground. Each chapter covers a broad Android functional area such as UI, Services, Broadcast Receivers, Content Providers, file and DB systems, etc. With each chapter new functionality is introduced based on these core functions, the application is refactored and in the process the reader incrementally understands the relationship of the components. While the incremental enhancement approach can be a risky approach for a book, as opposed to books that develop limited demo capability on a per chapter basis, it works well and keeps the reader engaged. Going through the book has the feeling of developing a real world application with all the success and failures one would anticipate.

The book does a good job of introducing the Android stack, Libraries, and the general concepts required for Android development. There is good treatment of the development environment setup, Eclipse, DDMS, appropriate API's, etc. and along the way introducing the reader to debugging techniques and tricks. The author provides a "twitter like" site with the appropriate API for development purposes. This gives the developer a real world site to experiment with and provides great feedback as the project evolves.

I enjoyed how the book incrementally evolved core functions that was not simply adding on to existing code, but required refactoring of large chunks of code. This juggling of the allocation of core functions helped with the learning process of how to really "wire up" a non trivial application. While I learn by banging in code and flailing with the debug process (as opposed to cut-and-paste), the provided sample code, segmented by chapter, was nearly flawless and provided a fantastic backup.

As a side note, in the first week of work with the book there were some minor issues with the "twitter site" used for development. The author was incredibly helpful and responsive in resolving the issues. I liked this, having experienced books where promised code or documentation never materializes. The errata site on O'Reilly was active but the majority of the issues discovered by the first couple readers through the book were minor and would in no way stall a new reader.

I very much enjoyed working through this book. If you have a good grounding in Java you will really appreciate the pace of the books and its focus on Android specific functions. If you are new to Java but are comfortable with other OO languages and want to get up to speed with Android fear not, I think you will be OK with a little slogging. The book served my purpose by filling in little holes in my knowledge that I may have missed over the years and understanding new patterns and approaches.