Lance,
we clearly don't have coverage for
memory management, power consumption of apps, storage, permissions
However programming for tablets mean programming using
Fragments
ActionBars
Fragment Dialogs
and more facilities revolving around fragments.
Currently tablet programming is all about programming with fragments. we cover this well.
The fragments are designed in such a way that you can place one or more fragments based on orientation or device size. Fragments also manage state. They manage back button well. Along with actionbar they emulate a browser like usage
pattern for your application. These aspects are covered in the book.
Fragments are expected to become available on phone API as well. But until that happens you are developing in two different worlds. You can have the same service API but you end up with two UIs.
Once the fragments are available uniformly for both APIs (phone and tablet) then you probably have more options. Even then it will be continuing challenge with signficant differences in screen sizes.
The resources mechanism in android (we cover resources well) allows for different layout configurations.
However we don't have a chapter that specifically says how to write one application that works on both tablets and phones.
If you write a phone application it will run on tablets but not the otherway around as those apis are not available in phone right now.