Hot answers tagged actions
10
The major mobile touch screen operating systems (iOS, Windows Phone 7, Android) don't trouble the user with "closing" applications in the way that desktop applications do. This simplifies the experience, making applications appear seamlessly built into the operating system.
Typically, applications on these operating systems will "pause" when the user ...
9
I would use different visual indicators, and a secondary, like so:
download bmml source – Wireframes created with Balsamiq Mockups
The important thing is how often users will be selecting the actions... if they will 'Accept' 90% of the time, Reject 9%, and cancel 1%, then it's likely Accept should be larger/easier to hit than Reject, as shown ...
6
The last thing you want when you have a lot of tables/lists of records is to make the data less readable by having more noise and clutter from permanent buttons, links or drop down arrows, so I favour the hover approach in this instance.
Change the cursor on hover, to aid visual feedback. Align edited text with cell content where relevant so that it doesn't ...
6
It's quite an age old question in UX/Universal Design. But, with time I feel the importance diminishing. Some reasons maybe true globalization of products/brands/english language/etc. I know companies still have to rebrand their products based on the country the are launching in, but those cases are getting fewer. Once again, just a personal observation.
...
5
It can be confusing to put something that is (that is the status) in a button that represents something that could be, (that is the action).
Try to separate the Status and the Action (or button) into two clearly different elements, for example a text label and a button:
download bmml source – Wireframes created with Balsamiq Mockups
Then apply ...
5
You can use two actions in a row, Apple does support that with its standard UI elements. Its called the Detail Disclosure button.
*
*
Users tap a detail disclosure button to reveal additional information
or functionality related to a specific item. The additional details or
functionality are revealed in a separate view.
*
From IOS Human Interface ...
4
Personally, if I were to develop an Android app I wouldn't include a close button either. As others previously mentioned, it's too easy to accidentally hit the close button inadvertently.
What I would do, is include a close/quit command as an option that comes up when the user hits the Menu button. It just feels like it should be a menu option instead of a ...
4
You could proceed as follows:
Try to reduce the width of the particular columns. This way you gain space.
Move the contextmenu completely to the right, such that all actions are under one hood.
Reconsider your actions. Prioritize and group them and correct the layout correspondingly.
And in detail:
Regarding 1.: For example, the column description ...
4
Neither options seem ideal since the user cannot provide login information right aways and I think that's what users expect when presented with login. If several login options are supported it could default to the most frequently used option and also remember what the user picked previous time allowing users to log in with a single click.
If you have to ...
4
In western culture, red has a negative connotation (however for Japan this is the opposite). It is used as a warning or error, so using it as the primary option is a violation of the consistency principle (at least for most users).
While cultural meaning might not be as important as it used to be, having consistent user interfaces is. Since most ...
3
I like Myrddin's suggestion a lot and think the concept works. Another option, to get away from red/green (which can look the same to some color blind users]) and use a green check icon in conjunction with "Accept" and a red x icon in conjunction with "Reject". If the icons are different colors that's a good visual cue to those that can see it, but the ...
3
If you mean to track all the user actions like: how many people downloaded a file, how many readed a document, how many visited a page; you can use Google Analytics.
Obviously you need to set it up in order to track everything.
Take a look at the features that GA offer: http://www.google.com/analytics/features/content.html
There is also a real time ...
3
I'd say that for the mobile environment, your first scenario would be preferred in my opinion. Limiting unnecessary actions is always best for on the go browsing that is done on mobile devices.
The only downfall, I suppose, would be in the event of a misclick it might be inconvenient that the event has already triggered - depending on what that event is...
...
3
As a designer, red is considered to provoke the most response amongst users. However depending on how the color is used it can have positive or negative effects.
Within my workplace the use of a navy blue color as a primary action button and a light grey color as a secondary button are practiced. These colors provide a balance to forms located throughout ...
2
With tiny little touchscreens and fingers typically bigger than the touch points and touch points normally too close together for said fingers, it would probably be far too easy to accidentally tap the close button when you intended to do something else.
The only way that would work would be to have enough space around the close button where there isn't ...
2
Closing iPhone applications from within the app itself goes against Apple guidelines, so most developers would not take this route for fear of the app being rejected from the App store. Quitting from within the app "looks like a crash to the user." (Apple's words, not mine).
There's a question on StackOverflow about this issue.
2
At least with Facbok app there is no HOME button. The only way to get to HOME is go to main screen, open another app, double click the iPad home button, hold the icon until it wiggles, click the minus sign. Now when you open the Facebook app it puts you on your HOME page, and that is different than your wall.
2
It's because of the way Android is designed.
The operating system manages the memory in a very different way to the way it's done on a desktop computer. The same goes for CPU.
When you don't have an application on the screen (in the foreground) it no longer takes up any CPU. That is because unlike with desktop applications the OS knows that you can't be ...
2
Honestly, I don't think the answer to this is UX related. It certainly can't be related to the size of the 'close' button being too small-- tablets are plenty big and don't have close buttons either.
I think the answer is just system resources. Mobile devices are slow, and it's a lot easier to switch between apps if they stay open in memory.
If you're a ...
2
It could be really confusing if the distinction between what is command link and what is navigation link is not really clear. Action Links or Command Links are best if they do not look like links, eg by font & styling, physical separation from other links, labeling, terminology, adjacent icon, etc. But they do have their place if not overused, are kept ...
2
If a properly setup Google Analytics isn't telling you what you need, you may have a hard time integrating action tracking into an existing application.
Just like exception logging, the onus is on you to integrate the tracking of a user into the application itself. Every action should be recorded and logged as part of the application, giving you granular ...
2
In option 1 I can see there is the bulk update action - but I can also see that there are other actions because the 'or' word tells me so, so I'm compelled to see what those other actions are, even if I think I just want to do Bulk Update anyway.
So for this reason I favour the option that shows me all the actions available most clearly and quickly, and ...
2
This question made me think about source code management software, where there is an important difference between changes made to the local code (on a developer's computer) and changes that are committed and pushed back to the repository where other developers (and sometimes the shipped product) will be affected by the changes.
An explicit commit or 'take ...
2
I think you can, regardless of the phone OS. If you take a look at Windpws Phone Call History, you have two different actions on the same row. The first item is an icon of a phone, and on key press you will call that person. The second item is the name, which on key press will lead to that persons contact information:
But to make this work you'll need a ...
2
Regarding the 4 popular actions you have in the "Options" column:
If you have more than 4 actions, you can change the fourth action to "More..." and when clicked, show the complete context menu for this row. This is much harder for a user to miss.
You may need to move the context menu completely to the right as well, like Anna Prenzel's suggestion, if you ...
2
It makes no sense to consider a single color. You have to consider the color in its context. No one was ever stopped from drinking Coca-Cola because of the red in the logo.
So long as the context and the surroundings are unknown, it is impossible to give an informed opinion on a choice of color.
2
There is no right color for your primary and secondary buttons. What does matter is how much contrast there is between the two.
I believe that the color does have a huge significance in what you are trying to display to the user, however I do not believe that the exact hue or shade has an enormous significance as long as your UI is consistent throughout ...
2
Nice question, but I think they actually are completely different cases.
While the state of the checkbox may be remembered for your next login the value is only valid for this login. When you log out, you should be logged out and this should not affect the remembered value for your next login. As such the checkbox isn't an indication of some permanent state ...
1
Regarding the row actions (Edit/Check/PDF/Notes), I suggest the following approach:
The menu you are showing on right-click (on the row background) is great in my eyes. We should focus our efforts and make sure this is what users do.
Instead of showing this menu only on right click on the background of the first cell, I would show this menu on any right ...
1
A partial suggestion - when the user selects a particular row, expand that row into something much taller - say, 5x the height, that shows more detail about that item.
You then have more room to display available actions, and maybe even do away with showing actions on non-selected rows.
Update
While this does introduce some behaviour that doesn't have a ...
Only top voted, non community-wiki answers of a minimum length are eligible
