Hacker News new | past | comments | ask | show | jobs | submit login

As an Android developer for many years I was excited when I read the blog post about the site. When I went to the site, I was very disappointed. I've spent the better part of 10 minutes on the site so far and haven't seen anything other than marketing text and screenshots of what my phone looks like.

How do I make these "beautiful designs" work across all Android phones? How do I use an Actionbar on a non 3.0+ device without external libraries? How can I supply a consistent look and behavior for my application when some android OEM keyboards don't even offer the same modules as other ones?

How am I supposed to follow these guidelines when every Google application has a different implementation of the Actionbar itself?




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


That'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-con...


As 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.


Guidelines are not tutorials. This might not be what you wanted, but this is what a design guidelines document looks like.


Agreed. Very frustrating for "building blocks" to show things like "scrollable tabs" that I'd quite like to use, where in fact no such standard implementation seems to exist! It's all well and good to display UI best practices, but give us the actual widgets you're talking about, otherwise the whole thing is pointless.



The ViewPager doesn't include any sort of tab bar. You have to integrate them with tabs yourself or use a 3rd party library like ViewPagerIndicator.


The announcement for and docs of the Action Bar specifically point to libraries that can be imported pre-3.0 to provide the Action Bar.


You mean the ActionBarCompat example which is so minimal that only the simplest apps can use it? It's lacking almost every feature of the action bar.


No, that's not what I meant.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: