Well, it doesn’t help that Google’s support libraries for developers are at best... bad looking. At worst, they are crashing with no way to find out what caused it.<p>1. AppCompat used to crash on device rotation with no clear error message on KitKat.<p>2. There are many third-party libraries that expand on what Google provides to allow devs to actually provide good-looking Material apps, from MaterialDialogs to MaterialDrawer to MaterialTabs.<p>- <a href="https:&#x2F;&#x2F;github.com&#x2F;afollestad&#x2F;material-dialogs" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;afollestad&#x2F;material-dialogs</a><p>- <a href="https:&#x2F;&#x2F;github.com&#x2F;mikepenz&#x2F;MaterialDrawer" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;mikepenz&#x2F;MaterialDrawer</a><p>- <a href="https:&#x2F;&#x2F;github.com&#x2F;florent37&#x2F;MaterialViewPager" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;florent37&#x2F;MaterialViewPager</a><p>Many things, like a multi-pane preferences activity with AppBar, are not possible without hacks, reflection or access to internal com.android APIs either.<p>And when Google provides support for something, it’s often lacking features, for example: <a href="https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;androiddev&#x2F;comments&#x2F;3vwpna&#x2F;im_incensed_i_just_dont_understand_why_some&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;androiddev&#x2F;comments&#x2F;3vwpna&#x2F;im_incen...</a> or full of bugs <a href="http:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;30537413&#x2F;textinputlayout-not-showing-edittext-hint-before-user-focus-on-it#answer-30608974" rel="nofollow">http:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;30537413&#x2F;textinputlayout-...</a>