Live data from Hacker News

Android Design

developer.android.com

21–30 of 143 posts

Re: Android Design

#21
post #19

I like the date picker http://developer.android.com/design/building-blocks/pickers....

Fun fact: the up and down arrows work exactly opposite how you expect them to.

Hilarious because i've been flip flopping on how they worked. The arrows seem to be a paradigm from mouse-based computing, can you scroll these lists like on ios?

Re: Android Design

#22
post #19

Earlier quoted context omitted.

Fun fact: the up and down arrows work exactly opposite how you expect them to.

Hilarious because i've been flip flopping on how they worked. The arrows seem to be a paradigm from mouse-based computing, can you scroll these lists like on ios?

If you scroll them they actually remove the arrows and make a lot more sense.

Before you drag: http://i.imgur.com/4MUXO.png

After you press to drag: http://i.imgur.com/BqXMY.png

To be fair, it's a huge improvement over: http://i.imgur.com/2exF7.png

Re: Android Design

#23

This is a long overdue but very well put-together UI and Usability Guide for Android Developers. My only qualm from reading it thus far is the very last section under Navigation [1] regarding System-to-app navigation: "For the Back key, you should make navigation more predictably [sic] by inserting into the task's back stack the complete upward navigation path to the app's topmost screen." No. This piece of advice is…

Google Voice follows (or used to, at least) your advice, which led to endless frustration. You'd tap a notification to read a text, then have no way at all to get to the main screen of the Google Voice app. In Android 4.0, Google Voice has an app-specific back button that helps, but I think Google's advice on this is correct.

Re: Android Design

#25
Am I missing something? I'd like to get my hands on the templates, mocks, wirefames, etc. Let me play with those (as a designer) and I'll be able to better follow the specs and guidelines.

Note: Microsoft (for once) actually one-up Big G. here. They provide the PSD and fonts for Windows Phone 7 on MSDN + the UX Guidelines.

Also, for Apple, 3rd party made all the PSD and templates for them...

Re: Android Design

#26

This is a long overdue but very well put-together UI and Usability Guide for Android Developers. My only qualm from reading it thus far is the very last section under Navigation [1] regarding System-to-app navigation: "For the Back key, you should make navigation more predictably [sic] by inserting into the task's back stack the complete upward navigation path to the app's topmost screen." No. This piece of advice is…

This was a huge frustration for me on 2.x. I'm glad they're suggesting that people insert fake activities to fix it.

Here's an example -- from the homescreen, click a Music widget. The Music app opens and shows the song I was listening to. I want to go back to the playlist I was playing from so I hit back. Instead, I'm dumped back to my home screen. you have to hit the Google Music icon in the top-left to go back within the Music app. I don't mind having to hit back a couple of times because I've learned that you can just keep hitting back and you'll eventually get where you were.

Re: Android Design

#27

I like the date picker http://developer.android.com/design/building-blocks/pickers....

Looks a lot less intuitive than the UIDatePicker in iOS, which is styled like a slot machine [1].

Does anyone know whether you can manipulate the controls by dragging, or do you really have to use those little up and down buttons?

[1] http://blog.blackwhale.at/wp-content/uploads/2011/05/UIDateP...

Re: Android Design

#28

I like the date picker http://developer.android.com/design/building-blocks/pickers....

It is quite annoying, if you say want to move a meeting to next Tuesday you have to work out the date, as you get no day of week indicator. And changing date and also time involves two pickers. Every time I use it I wonder if it could be improved...

Re: Android Design

#29
post #26

This is a long overdue but very well put-together UI and Usability Guide for Android Developers. My only qualm from reading it thus far is the very last section under Navigation [1] regarding System-to-app navigation: "For the Back key, you should make navigation more predictably [sic] by inserting into the task's back stack the complete upward navigation path to the app's topmost screen." No. This piece of advice is…

This was a huge frustration for me on 2.x. I'm glad they're suggesting that people insert fake activities to fix it. Here's an example -- from the homescreen, click a Music widget. The Music app opens and shows the song I was listening to. I want to go back to the playlist I was playing from so I hit back. Instead, I'm dumped back to my home screen. you have to hit the Google Music icon in the top-left to go back wit…

I've only used an Android phone once for 5 min (my Mom got one for Christmas), but that was enough to run into Back button confusion.

My assumption was that it would take me up the stack, since when I entered the Mail program and navigated down, Back took me back up. But when I entered from some other place (like the settings app) then back wouldn't take me up to inboxes.

I'm sure it would have made more sense if I realized it was a system-wide Back and not an app-only Back.

Re: Android Design

#30

I like the date picker http://developer.android.com/design/building-blocks/pickers....

Looks a lot less intuitive than the UIDatePicker in iOS, which is styled like a slot machine [1]. Does anyone know whether you can manipulate the controls by dragging, or do you really have to use those little up and down buttons? [1] http://blog.blackwhale.at/wp-content/uploads/2011/05/UIDateP...

You can drag them.

See my other comment here: http://news.ycombinator.com/item?id=3458159

Post reply on HN