We should depend on an abstraction defined in this library, and then provide an implementation for ViewPager.

This is the same issue that the TabLayout from Material Design library faces - it depends directly on ViewPager.

ViewPager 2 is in EAP - and neither TabLayout nor Landing-Strip supports it.

Either:

1. wait for VP2 and add direct support for it
2. expose and depend on an abstraction for ViewPager (e.g. page scroll listener), so that it's easy for new implementations
3. deprecate landing-strip in favour of TabLayout, which will eventually have support for VP2 also

I think 2/3 are legit.

Should README have screenshots?

Can we update the readme to be more explicit about how the simplest example works?

Currently, padding can be added only to the whole landing strip, and not to individual tabs. This padding (more like a margin actually) should work in such a way that the indicator is underlining only the tab text, as in the screenshot below:

https://code.google.com/p/android/issues/detail?id=175086

Users of the lib will have to add this as a file for temporary workaround:

package android.support.v4.app;

public @interface DialogFragment$DialogStyle {
}

Would be nice to have Release notes, how to migrate from V1 to V2 and how to use V2 💃

I was reading this blog post the other day on Android view states and it was talking about how selected is more like a fallback for when focused cannot be used, and the correct state to use to designate the tab representing the current viewpager pager is activated.

Activated has been a state since honeycomb, and has the same affordances as selected so it's just a semantics thing.

We just use it for some animations, lets grab those and drop the deps

#11 (comment)