Tag Info

New answers tagged

0

Depending on what the actual table represent and what the purpose of the page is. If there is possibility of presenting data in non-tabelar way you can implement "lazy loading" or "load more" button. If data is sortable then you can limit number of entries per table and add pagination.


2

The most important factor in your decision should be "don't make the user think." The ellipsis is standard for truncating, but if you also intend to use it for a link, you'll want to use some sort of visual link convention (an underline, a link colour that you're using throughout, or something to that effect.), but it must be both obvious to the user that ...


0

The language in your wireframes doesn't seem to match how you're explaining things. It sounds like the thing a user needs to do to get from the full table to the "most interesting" view, is hide future dates. download bmml source – Wireframes created with Balsamiq Mockups Regarding the communication of future items, rather than mark every item, ...


0

Depending on the nature of the business of your application this can be decided. For instance, if your are looking at a financial report sort of application you may want your filters visible at all times. Probably one wants to quickly track down a transaction in a stack by just the amount or some other meta data. Most financial applications have a lot of ...


0

Gestures are fairly undiscoverable—not obvious at first glance. With gestures on iPhone: Provide another way to do the same action. For example, in the Mail app, users can swipe to delete or can use the Edit button to reach the Delete command. Assign the gesture to functions that aren't critical. For example, it's possible users will try to navigate with ...


1

In terms of order, the primary (in terms of user association) identifier for the data row should always be on the left in a left to right language localization. Note that if you have a unique ID for each item, this may not be appropriate if it's not what a user themselves would primarily associate with that item, or the main feature they would generally ...


1

I propose you do this like on YouTube (and the same solution is proposed in the accepted answer of the question you link to) when there is a table with videos you uploaded. There are some actions, like "Delete", "Publish", "Edit" etc. for each video. The Table has one more column allowing selecting a video (this is typical checkbox). You can select multiple ...


7

3 small action buttons on the left-hand side of each row With a LTR languages, one can assume users will first inspect the row (starting from the left) and only then decide to take action. So placing the buttons on the left side is somewhat counter-flow. 3 small action buttons on the right-hand side of each row Pros: Buttons are easily ...


1

I think it depends on the main purpose of that table; if Update/Delete, put it first else put it last. In most cases though, you probably first want to identify what you want to edit/delete; in that case putting it at the left side forms clutter and is better to replace it with a checkbox and to than put the inline controls at the right side instead. Also ...


2

This reminds me a problem I work on last year: User wanted to pick a set of records from a paginated list, and apply bulk operation on them. The pagination (a sort of filter if you wish) meant that once moving to another page, previous selection was no longer seen. There was also a search field which allowed filtering of records. First choose then do The ...


1

you need a different approach here. The user is probably only interested in exceptions (red, orange, blue?) so you should render the display differently. I would advocate having a simple traffic light screen with each colour having a number beside it green (14), orange (3), red (2), blue (1). On click user goes to listing of all the issues of that ...


1

One thing I like to always do, is looking at if from the other way around and simply go mobile-first, so it definitly makes sense to try and do this exercise. The limitation of mobile phones lets you focus on the really important parts. When going to a tablet or desktop you'll notice that adding stuff is much easier than removing stuff. For the tables, I'd ...


3

I'd recommend getting rid of zebra striping. It's often considered chart junk more than it's considered helpful. If you need to group rows, do it with a visual divider line: --------------- apples 12 bananas 47 oranges 16 --------------- sausage 3 hamburger 72 --------------- ketchup 7 mustard 9 --------------- ...


1

You could add a simple border to the bottom of the last row in any given grouping. That way, even if the colors match between groups, there will still be a definitive marker between them.


1

My recommendation, if possible (it is generally technically possible) is to have a copy to clipboard button that will do this for the user, so they need only paste it. If you're interested in the implementation details, more info is on this StackOverflow question Here is an example of what it often looks like. Bear in mind that although the example is ...


0

Along the lines of the first answer -- the link to Order Details points to the product detail page, which has a full description, reviews, specs, etc., AND a button to Buy/Download. Your table is sort of like an order-confirmation, or wish list. See example below The table serves as a record of items ordered or purchased. As for the Review link, is ...


1

I would link the Order ID to the Order Details page. Just seems logical to me. I think I would want the link to act the way you describe item 8 - Access. I'm not sure why you would need to go to a product description page after you have purchased the item. In theory, you know what you have purchased. However, I would also assume that from the page that ...


1

Edited answer: You're almost there I see you edited your question to show that the times appear in a grid. This is perfect, since a grid does exactly what the rest of this answer suggests. Even if the grid is "transparent" it is apparent. Your table follows a convention. It is clear. It could be a bit clearer, still. Why don't you experiment with: Remove ...



Top 50 recent answers are included