Tag Info

New answers tagged

0

first of all, I have no idea how you get that data, and this means A LOT. It's not the same to display data from a search or pre-filter than to display all data by default (specially if we're talking of anything above 100 results) Personally, I think what you have now is probably the best option. However, you may want to take a look to more table UI ...


4

I know from experience that it's better to add a default sort indicator. For example, many of our users didn't realised the table columns are sortable and didn't even tried to sort them if there was no indicator. So we were receiving constant questions/suggestions to make the columns sortable. Our solution was to add default sort indicators like this: ...


0

If clicking a second time would reverse the order, the user still recieves visual feedback when he wants to sort on the default column. Wouldn't this combine both advantages?


1

You don't necessarily have to go with a button but as a user, I'd definitely like a click target that's bigger than a single number. You could make the whole cell clickable. If you want buttons you could make your header "Sessions/Calls" and then use a single cell and make a button group with sessions on one side and calls on the other. The "right" answer ...


0

Disrupt the flow as little as possible I agree with you that inline editing is the way to go since it provides context to what the user is currently looking at. I don't like the idea of automatically changing modes when selecting a row since just this can disrupt the user's flow and is more prone to accidental edits. I would combine your first and last ...


0

I second Sherwin's answer. Leaving as an answer instead of a comment so I can include an example.


0

I'd agree with most of the answers here and use a background colour and text colour change to indicate read only cells but from a web accessibility point of view you should also add additional non-colour based indicators such as an icon or text decoration to indicate which rows are read only.


1

I'd recommend the opposite: mark the editable cells as that is the unusual behaviour for tables. You could easily do this by adding a darker internal border to the top and right to make those editable cells look more like text input fields (an accepted pattern for editable text areas). However, if you are stuck on marking the field the user cannot interact ...


0

If you are using zebra striping for your rows having yet another bg colour row for disabled might be a might too much on the eye. In this instance you could change the font colour to be greyed out or a hightlight colour for the disabled rows. You can also change the cursor to not allowed:


2

I think 3 is the best option here. 1 & 2 show the form fields and have them disabled, this could indicate to a user that they could become editable - and they may wonder if they need to perform an action to make them editable. Because they will never be editable, no form controls are needed. The data should be printed. Another thing they may help this ...


-1

If I'm interpreting you correctly, you can do this with jQuery. Once you've installed it, add a click event to each row that toggles a "selected" class: $(document).on('click', 'tr', function(event){$(event.target).toggleClass('selected');}) If you have different "odd" and "even" classes for every other row, you CSS should look like this: .odd{ ...


1

I like the idea. Another option might be to group the data when you click the table row and display it directly. The reason I suggest this is once a user clicked something, I guess it is the plus (+) in your diagram, do they want to click further to drill down to the application? This all depends on the amount of data you need to show of course. Or ...


0

Have you thought about a simple border for selection? Here is a simple example: jsfiddle


0

I am not a big fan of alternating background colors between rows. White space and visual grouping should do the trick in most cases. In your case, I would use a lower contrast between the background colors. Use just enough so that the eye notices the change. As far as selection, I don't see anything wrong with using a different background color, a stronger ...


0

The standard iOS interaction that users have come to expect: when you "swipe to delete" an individual cell, the delete button is indeed on the right-hand side of the cell. So in that case your boss' boss is correct. This functionality is built in to UITableView back to at least iOS5, so you don't have to change any code. However, per Apple's UITableView ...


2

A green "Record was added successfully" message at the top after the user has clicked "Add Author". This will give the user peace of mind. Something like this. It would be best to refresh the table as this happens. Otherwise the user may attempt to add the same record again, causing duplicates. You can use something like the Yellow Fade Technique which ...


1

If the element is clickable, make it noticeable and get rid of any uncertainty about the affordance of the given element. In order to achieve this, you can try different options: use a floating button action as trigger: this is the Google Material approach, so it's meant for Android, and it visually helps the user to clearly understand what is a header ...


0

Always start by asking what users need to do with the data Do they need to go into a specific record to look up info or make edits or bulk edits? Put in easy search & filtering. Determine what are the general context users start with when it comes to finding data. Do they do a specific search (e.g. name, email, phone #) or by ranges? (e.g. by city, ...


1

I would not use icons for this purpose because they are difficult to understand without labels. If you're worried about scannability, adding bars to ease visual comparison can help. Here is a palette of options that use bars with different scales, and also different text representations of the frequency: You will have to decide whether you want to ...


0

Basic requirements I'd second everything scunliffe said. Sort and filter are critical. Pagination is once you get past 100 or 1000, depending on the data and speed of your service. You mentioned supporting search and query-building, but it deserves repeating that simple search is a given. On the point of pagination, it might help to think of it in database ...


2

Managing a list of anything... that is over ~50 items is tricky unless you have (or in this case provide) the right tools. Paginate the results - seeing more than ~100 of something on a screen is not very usable (If the user needs to see a larger set/all at once, provide an export option where they can manipulate the data externally) Sorting - provide ...


2

Seems like you might be over-complicating things, and not even for the right reasons : / First, because "not really sure why, I guess I think it's ugly" is a poor reason to go re-inventing the wheel. If you do some testing, or get some feedback, that suggests users have issues with these words, then change it up. Applying your experience as a designer is ...


4

Two ideas: You could display the number of times per year the event takes place. Monthly ----------→ 12 Quarterly ----------→ 4 Twice per year ----------→ 2 Yearly ----------→ 1 If the important thing is when the next event will take place, you could hide the frequency in the UI and display the date of the next occurrence.


4

If the user has that large number of entries, I think is a better idea to sit the final user and get the requirements of the task that he is actually trying to do. I don't have all the context but what is he trying to achieve: If the user has to review all entries one by one (for example an accountant needs to review all the balances to see what is not ...


0

Do not use adverb but use every. Monthly ------------→ every month Quarterly ----------→ every 3 months Twice per year ---→ every 6 months Yearly --------------→ every year You may want to add "once" Once every 3 month



Top 50 recent answers are included