Michael can you discuss with design which customization is important?
I do not think "android-compat" is a good enough motivation for implementing certain features. If you can add a few use cases, that would help in prioritizing the features and deciding on an API to add them (for example, for a fixed header color per-app we may recommend to use theming, or add a property to the MainView. However, if it is a common use case to change the header-color per Page in an app, we may need to add a property to the page. It is also important to get feedback from design on this to find out which settings we like to promote and for which we will recommend the app developers to use the defaults to make the applications consistent).
Michael can you discuss with design which customization is important?
I do not think "android-compat" is a good enough motivation for implementing certain features. If you can add a few use cases, that would help in prioritizing the features and deciding on an API to add them (for example, for a fixed header color per-app we may recommend to use theming, or add a property to the MainView. However, if it is a common use case to change the header-color per Page in an app, we may need to add a property to the page. It is also important to get feedback from design on this to find out which settings we like to promote and for which we will recommend the app developers to use the defaults to make the applications consistent).