On Thu, Apr 14, 2011 at 10:21 PM, B Lyon <[email protected]> wrote:

> and I think most folks wouldn't know how to interpret a "refresh" thing,
> which is what I was also initially considering.
> Again - I'm thinking of the most blatant thing that is as unambiguous as
> possible when someone is first seeing the screen


I think you're over thinking this. Not every action has a clear, obvious
visual representation. And you cannot predict what any given individual's
personal experience will lead to associate with a given icon. You might see
"refresh", I might see "back", someone else might see "undo", or whatever.

Ultimately, it doesn't matter. There is always some learning going on with a
new app and learning what an icon does is usually fairly straightforward.

I don't know the details of your app, but assuming you don't do "refreshing"
anywhere else or use the same icon if you do use "refresh" somewhere else,
it's very easy for the user to figure out that your icon is for reseting. It
might help if it's initially disabled then becomes enabled on first action.

1 - Start activity, all defaults, reset disabled
2 - I do something, reset button with "refresh" icon is enabled
3 - Out of curiosity I press the button - the screen resets and the button
is disabled again.
3b - Optionally post a toast that says "Reset to Defaults"
4 - I just learned that this icon is for reseting the things on this screen.
5 - I will now associate that icon with reset. The need for the icon to be
the "most blatant and unambiguous" has evaporated just like that.

-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
transit tracking app for Android-powered devices

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to