3 ms·
The link at the bottom to the core developer site shows you how to implement most, if not all, of what they discuss here. Though it would be nice if they had li
by Pewpewarrows 15y ago
The link at the bottom to the core developer site shows you how to implement most, if not all, of what they discuss here. Though it would be nice if they had links interspersed throughout the design text to their tutorials and API guides about the UI features.
http://developer.android.com/index.html http://developer.android.com/index.html
- jc4p 15y agoThat's definitely true, I don't know why they didn't put a "click here for more technical info!" next to each point. The things that really bother me are: 1. If I implement one of the new themes they're discussing on the linked page, it only works in 3.9% of Android phones on the market, so if I want my apps to look like Google's on older phones I'm left to implement my own version of the themes. This is the same thing that happened when they announced "Homepages with square buttons for activities are the new way you should do everything!" and didn't release source code for how to do it for years afterwards with the Google I/O app, so every app that tried it did it a different way. 2. How am I supposed to use the action bar if Google's own applications can't decide on how to use it? Look at the "What's up with the bar" section of this blogpost: http://minming.posterous.com/google-currents-yet-another-contribution-to-t http://minming.posterous.com/google-currents-yet-another-con...
- cuu508 15y agoAs for 1st point, check out section "Pure Android". It says you shouldn't copy UI style from other platforms. I think this could be extended to major versions of single platform too. App with Holo theme on Froyo phone would look very out of the place, I think.