The two themes should have appropriate (different if applicable) values for base Android and appcompat theme attributes, e.g. Unfortunately, since our two themes extend two different base themes, we cannot share any common attributes (the same way a class in Java cannot extend two or more classes). Here we add a new dark theme called AppTheme.Dark, and for style and color consistency, we extend from appcompat’s theme Theme.AppCompat (a dark theme). Materialistic also employs a similar approach. So how should we specify resources for multiple themes? If we look at how resources are organized in appcompat, we will have a rough idea of how the Android team organize their theme specific resources. Unfortunately, this is not yet an option at the time of this post. values-dark for dark theme resources and values-light for light theme resources. Ideally, if we treat theme as a configuration, we should be able to specify theme-specific resources under a ‘theme-qualifier’ resources directory, e.g.

In this blog post, we will continue that effort, creating another theme and allowing dynamic switching of themes during runtime. In the first part of this post, we have created a light theme and made initial preparation to support multiple themes.

User change theme android studio