Tag Info

New answers tagged

0

On the one hand server name/ip is the ID of the server and on the other it looks like the most important property is the server status. Not a clear answer here I think but just note you can combine both attributes to a single column. This is usually done by putting the primary information on top and the secondary below it, with smaller font and lighter ...


1

Here's a rule of thumb on data tables. For people who read from left to right, you assign priority from left to right because that's how they read. (Note: it'll be reverse for right to left languages e.g. Arabic) Columns used for ID & scanning gets higher priority Because we read and scan information using the "F-pattern", you want the identifying ...


0

This problem has many parallels with database administration interfaces, where there are often many columns and rows. Both php myadmin and navicat solve this conundrum simply by allowing the user to configure column order to suit their own particular use case. Your domain is similar, you have technically adept users; detailed and complex technical data; ...


0

It depends on the weight you want each to have. The ones you put further to the left, the more likely and easily people will see them as we read left to right. In your particular case, I'd likely do status and then the server name because if a server is down I want the admin to immediately notice. I'd likely have it color coded as well, green or black for ...


1

Where should the delete option be? I see many examples placing the delete icon or text on the far-right of the row. Is this best practice? Is it always advisable to swap row delete to checkbox selection/batch delete? I believe the far right location is because you don't want user to accidentally click on delete. It depends. For a really long (tall) ...


4

You can simple use "actions" button which opens on click all available action for specific row. Example:


4

Great question! This is a very common design pattern and it's one that sites screw up all the time (IMO!). Usually the objective is: Ensure the user sees the notification. Allow the user to get on with using the site smoothly after that. Don't p*ss off your users. This seems simple, but implementations often break the objectives! For example: Model ...


0

As DA01 suggests, Apple and Amazon have probably done most of the research for you. "Be the first to review this!" adds a little cachet that is likely to appeal to some users. If your users are also signed in with a social network to the level where you can monitor their connections you might also be able to use "Be the first among your friends to review ...


0

What you are describing is a very UX pattern, which is a policy editor. Generally, this entails selecting and editing a policy, and visualizing/editing the scope of the policy. Usually this results in an interface similar to what you sketched out, but with some adjustments: For the left hand column, it's unclear whether the checkboxes are controls or just ...


0

I understand your problem. I started as the only UX guy in the team and every project was just a fight and argument. Sometimes it becomes difficult to convince them why some things are right and wrong. Dev team is happy with the optimal performance so they don't see any need in adding any extra efforts. There is no hard a fast rule for everything. Propose ...


0

To me seems easier to understand if you group them more Authenticate: Nexus 5 with Android 5.0 iPhone 5s with iOS8 Nexus 6 with Android 6.0 If this are the only authentication options, it is obvious that if it's not in the list, it is not allowed (i.e. Android 4.0). But if needed you could add it as a footnote. Adding the disallowed as a footnote has ...


1

It does sound like a tree. The most obvious form will probably look like the following (option 1): It can be optimized a bit (option 2): Or simplified (option 3): Does any of these options look suitable?


1

Tabs indicate that there are different views of related information that can be swapped between at any time. Showing tabs and not allowing them to be used adds cognitive friction. I wouldn't show the tabs at all until after a selection is made on the first screen. Be sure to keep the first screen as simple as possible and only ask for the minimum amount ...


0

Can be one page with all of the inputs needed to create one plan and an ADD PLAN button that for example collapses the first plan and expands UI for creating another plan. Or a hybrid of both. Would suggest you doing a very rough paper prototype of one page and a wizard with all the information you want your users to give you and all the information you ...



Top 50 recent answers are included