[TIMOB-17963] Android 5.0: Adopt Material Guidelines in default Android application
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | High |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2018-12-10T23:17:47.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Android |
| Labels | n/a |
| Reporter | Ingo Muschenetz |
| Assignee | Joshua Quick |
| Created | 2014-11-05T18:36:36.000+0000 |
| Updated | 2018-12-10T23:17:47.000+0000 |
Description
Google has now given specific guidance on how to make Applications play nicely with Material Guidelines. We should adopt these changes in either our Android code, or our default theme.
http://android-developers.blogspot.com/2014/10/material-design-on-android-checklist.html
This is actually quite a big change: lots of modifications to ActionBar API (e.g. icons and background images deprecated, branding with typography and colors instead), looks like modifications will be needed for tab navigation, etc. The Toolbar is in some ways simpler than ActionBar, it's actually yet another view, but this changes the model quite a bit.
Beside the Toolbar and other new UI components, there are some things in this Material Design Guide that needs to be adopted, e.g. * [elevation and shadows](https://www.google.com/design/spec/what-is-material/elevation-shadows.html#) (for Titanium.UI.View and its subclasses) * [Activity transitions](http://developer.android.com/training/material/animations.html#Transitions) * [Ripple](http://developer.android.com/training/material/animations.html#Touch) and [Reveal](http://developer.android.com/training/material/animations.html#Reveal) effects
PR for elevation support: https://github.com/appcelerator/titanium_mobile/pull/6931
Thank you [~manuellehner]! Do you think we should break this Jira ticket into sub tasks?
Yes [~msamah], that could be helpful (maybe also renaming this issue to "support Material Design" ?).
This is being moved across sprints since years. Can this either be removed from the sprint or be completed via it's sub-tickets?
Yeah, this ticket isn't all that useful. We need to implement material design based features/widgets via separate tickets. Especially since it's a never-ending task and Google will continue to evolve it, such as their new bottom toolbar with centered floating action-button, etc.