Recommended for "android development essentials"

The book, written by hand, has been officially published for more than two years. In the meantime, due to work pressure, there was no word added in a year, and many chapters were constantly easy to sort and add new content. After a few twists and turns, they were able to see people.

More than two years ago, Android development was still a fresh field, and it was hard to find a good book. Any complicated framework mechanism and implementation mode needed to be explored. Therefore, I decided to write a book to summarize some of my experiences in Android development and learn and understand the source code. The first time I gave this book a nameBlogArticleThe same name is called "an in-depth understanding of Android". The goal is to clearly understand the implementation of some core Android mechanisms and common problems in development. This not only makes the underlying implementation transparent, more importantly, it can be more closely associated with actual development.

I don't want this book to have a complete example when explaining a function, but to provide a practical example.CodeFragment, because I think the complete example is like a well-decorated house. It will limit some models and scenarios too rigid and constrain the thinking during reading, code snippets are similar to the well-designed Lego blocks, and there are more possibilities. I do not want to directly paste code into large sections when writing the underlying logic, but to organize the logic into clearer text and charts, in this way, the slightly boring content becomes more lively and easy to understand. In addition, I don't want to make this book a comprehensive manual. I just want to present the core mechanism that I think is important and what I have actually encountered, this is because the content is the best and most profound that I understand and can help others.

However, as my writing goes deeper, I found that my understanding of "books" is still too simple and stuck on the "blog" layer. As a book introducing mechanisms and implementations, integrity is still very important, because the readers of the book are not like the readers of blog posts, but read by searching for a small problem, instead, we need a more holistic learning. Therefore, during my writing, I continue to learn and practice some areas that I didn't know clearly, I have dug up some details that I originally thought were not very important for comprehensive purposes. In terms of text, I also skipped all the fancy and fancy sections, and tried to be simple, clear, and occasionally interesting. These jobs have consumed more energy and time, so that the publishing date is continuously jumping, but it is still very happy to make the entire book more complete and easy to read.

Before publishing, the title of the book was eventually changed to "android development essentials" mainly because the book did not look so deep in comparison to the traditional "deep understanding of XXX" book, there is no explanation of specific code details, and no analysis of some particularly underlying content. The essence is the core mechanism of Android, such as process hosting and component model. On the other hand, it refers to the key points ", that is, some practical experience, such as interface construction, large memory control, and cloud. Although I think the title is very uncommon, it also makes the book closer to its readers, because I want to write something for general Android app developers.

Today, Android development has become one of the most popular jobs, with many books covering a wide range of fields. This book is not very compatible with my earliest expectations. Due to work pressure, the time, energy, and ability are very limited. There is really no way to perfect it. There are still many places in the book, I don't think it is well written. Even so, I believe this book can help many people. This self-confidence comes from ordinary work, because when some people encounter problems, I can say: "I have written this question in my book. You can check it out in a specific chapter ".