Android Design Patterns and Best Practice Paperback – 29 Dec. 2016

This book is mysterious: why does a book have no customer reviews after being on the market for 2 years (2018 at the time of this review), and why is Amazon promoting it at the top of the list?The author may well be a very good programmer and even a good writer, but the book is not good. It reads like a good idea with a rushed execution. Errata fill page after page (yet the publisher's website doesn't seem to have an errata page for this volume - in fact, I couldn't find this volume at all when I went to the page listed in the book and searched for the title.) Code examples are often half-finished with blatant gaps and missing code; or code just doesn't match the text describing it, or vital details are left out.I was hoping the core premise of the book would be a straightforward "here is a list of common Android projects; here are the Industry Standard steps you can follow to narrow down which Design Patterns are best for a given problem." Instead it just lists design pattern concepts and chucks in some (broken) code for you to clumsily follow along, and sometimes explains why you're doing X instead of Y ... but not usually.A whole team of proofreaders and editors is listed inside the cover (Safis Editing?) but I find it hard to believe that anyone proofread this book at all. Honestly, if I had to guess, I'd say the author was 3/4 of the way through his first rough draft and the publisher told him it was due and sent it out the door, sight unseen.

very nice book with complex concepts explain in easy way

Did not take any care in writing and editing. Explanation is awkward.