What made you think it was about money?
You wrote: “I’m being honest if I say that I feel cheated, first by Google and then by this book.” Hence, I refunded your purchase.
Sadly, trails have left me with unanswered questions.
Android is vast. My books do not cover everything in Android itself, let alone everything in the broader Android ecosystem (e.g., everything in the support libraries, everything in third-party libraries). I apologize if somehow I gave you the impression that they did. I feel confident that I have written about more Android topics than has any other person on the planet, but I cannot write about everything.
The point of the trails is to shine the light into various corners of Android, not to document every last bit about those corners.
In particular, with respect to FAMs, Android does not have an implementation, and the Support Library does not have an implementation. Even the new Material Components for Android does not appear to have an implementation. So, while this is covered in the Material Design documentation, Google has not supplied an official Android implementation, AFAIK. I happened to mention a third-party library that did, but I did not notice that this library had been discontinued after I wrote that material, and for that I apologize. The only reason why I covered FAMs in the first place was that I had already-existing code for it, so it was a “cheap win” in terms of additional book coverage. But the book does not cover every last item from the Material Design spec, even in cases where we do have components, as I cannot write about everything.
So, don’t the readers have a right to criticize?
You certainly have a right to criticize. I have a right to refund purchases.
how can a refund be your best answer here?
Frankly, it makes me feel better.
Please understand that I have a lot of work in front of me with respect to these books. In particular, as of this week, I have little choice but to deal with:
- Android Jetpack
- the AndroidX repackaging of all of Google’s official libraries
The combination of those means that I have to revisit everything from my ~5,000 pages of material. Plus, I will still wind up writing about new universal topics (e.g., Android P, new Android Studio stuff) and new stuff that Google heavily promotes (e.g., slices), along with writing an introductory Kotlin book.
That will take a minimum of two years, probably longer. And the result will be less overall coverage, as I drop topics that I am no longer in position to cover. Media playback would be a good example, as that has gotten a lot more complicated and specialized, and so I will have some decisions to make as to how I want to deal with that. Along the way, I expect that I will wind up repackaging the material, so I can better emphasize what I do cover, and not lead you and others astray into thinking that I cover all things.
So, by refunding your purchase, I can feel better about focusing on what is best for my business and what I believe is best for my overall set of subscribers, both current ones and future ones. Plus, you now have 20 USD to invest in another book that perhaps better meets your expectations.