usability – How should our app provide feedback on background jobs?

usability – How should our app provide feedback on background jobs? – User Experience Stack Exchange

usability – How to feedback app users on background jobs?

usability – How to feedback app users on background jobs? – User Experience Stack Exchange

usability – How to handle filtering on table columns?

I am currently working on a pretty complex (and convoluted, I’ll admit) table in terms of filtering. One of the options for filtering allows the user to filter on an item that is displayed as a column and I’m trying to figure out the least confusing / jarring way to update the table for it.

This is hard to describe in words, I’ll be honest so here’s a GIF showing the functionality.

enter image description here

I added blocks to hide some data so pay no mind to the floating grey boxes :).


Currently, only the selected items for that filter are shown in the table and the rest are removed. This has the benefits that the user doesn’t have to see or think about information that they don’t care about, but then they have to re-adjust to what is effectively a “new” table. The other option is to gray out the unselected columns so the information is still there but taken out of focus.

What method from the above, or some other if you have ideas, do you think would confuse the user the least?

usability testing – What new ux research tools do you use (ex: uservoice, user report) and what do you like the most?

Done the common ways of ux research like surveys, in person interviews,
beta testing, and affinity maps. I’ve noticed different tools online that are supposed to make it easier to capture feedback and understand needs.

Researching to try something that may be helpful for 30 users (phase1 ) to eventually hundreds

What are all the usability evaluation methods?

So I was reading several articles about usability evaluation methods and when I discovered that methods like cardsorting or treetesting ARE usability evaluation methods I got super confused. Specially because some articles mentioned all this methods as part of a group called “usability evaluations” and some called it “usability testing” methods. But if these are ALL usability testing methods, then: how do you call the usability testing that is done in labs or remote?

So I started creating a list of what I understood would be all the methods and I decided to follow a NNgroup name for the group since in an article they mention these as “usability evalutions” (not usability testings).

And I wanted to check if my understanding is correct. I will add below the list I came up from my research.

“Usability evaluation” methods list:

  1. Usability testings (moderated/unmoderated,remote/virtual)
  2. First-click test
  3. Tree testing
  4. 5 second test
  5. Form analysis
  6. card sorting
  7. Content evaluations (such as “online feedback pop-up window”, “Comprehension survey” or “highlighter test”)
  8. Eye tracking

So if my understanding is correct, “usability evaluations” are something different from “usability testings” since the usability evaluations are all type of evaluation made with representative users to discover usability problems BUT “usability testings” is one method of many others of usability evaluations. Is my thinking correct?

Is it correct to call the group of all this methods “usability evaluation methods” and inside it contains “usability testing”? or how would you call the group that involves all the methods in order to differentiate it from “usability testings”?

And finally, is my list of methods correct? Am I missing any method? is there a method that is NOT a usability evalution?

Thank you in advance,

usability – Putting “About us” context in Footer , is it valid from UX prospective?

I am making a web page for a local client, and he advised me to put an about us paragraph below to the company logo in the footer section. like this bellow image
enter image description here

I have seen these kinds of things on many pages, but the reality is, it already present on the landing page and a dedicated about us page, do we still need it in the footer?

before writing this question I came through the NNgroup blog. and
there is no mention of the about us section in the footer.

Google – mobile usability – Text too small to read – while it doesn’t show the real presentation of my menu items on mobile

Sometimes I receive the error Google Search Console Error “mobile usability – Text too small to read” when I click on “test live page” I notice that google shows my menu items as if it is on desktop and not on mobile phone. I use Enfold theme and my fonts are all in Persian Language and seems very nice on mobile phone screens
Each time this happen I click on “validate fix” and google validate it successfully.
But this time google says that the problem still exist, therefore can start validation process.
But why Google report it every so often? Should I do any action?

Screenshot of presentation by google and screen of real presentation on a mobile device attached here:

Real Presentation for Mobile Devices on my Google Chrome Browser
Real Presentation for Mobile Devices on my Google Chrome Browser

Google Claimed Presentation of my page
Google Claimed Presentation of my page

usability – When Should an Auto Logout Popup Warning Message Appear?

My application is required by our security team to log users out after 20 minutes of inactivity. We don’t currently have a message warning users that this will happen, leading to confusion/frustration for users. Is there an industry for how soon a message should appear? The last 10% of the timer? I.E. 2 minutes in my scenario.

usability – Continuing setup on another page and/or modal a bad practice?


I’m working on a project involving configuring live video feeds (contrast, brightness, focus, etc).
This is a very rough sketch of how the layout of the UI looks like:

enter image description here

Each grey box represents a category of settings. This is a view of one live feed. The UI can show an indefinite amount of live feed that the user can “open”. Think of it like tabs or profiles. The above picture represents the view of one such feed, and the user can go “back” and select another feed to view and configure. Basically:

<Feed overview page>
  <Feed 1 page>
  <Feed 2 page>
<Settings page>

I am now working on a new feature, which I cannot disclose the name or type of (sorry about that), but I can generalize a few things about it. I’ll just call it foo bar hence forth:

  1. It needs to be configurable in the Settings page and then “applied” to one or multiple feeds. In other words, you configure foo bar once and can then reuse it in any feed.
  2. As above, but the user should also be able to configure the same setting from within a feed page. Setting the feature here will apply it to the open feed, but will be available for other feeds to use too.
  3. The nature of the setting requires the video to be fairly big in size. Not necessarily fullscreen, but a thumbnail or anything small or medium sized will not suffice.
  4. The user should be able to select, edit and delete an existing foo bar or create a new one.

My proposal so-far

A feed without any applied foo bar setting:

enter image description here

Clicking it allows the user to select a previously created foo bar, or create a new one. (The video here is small because it serves the purpose as a preview – creating a new foo bar would require a much larger video area):

enter image description here

How selecting an existing foo bar looks like:

enter image description here

enter image description here

My issue

And here’s where I am stuck. In the case where the user wants to create a new foo bar – and taking into account that we need to give the user a much larger video area to work on – what is the best flow from here? Again, the video area here, in black, is just for preview – it cannot be used for the config itself.

Do I transition from here to a window/modal where the video is much larger? Do I redirect to the Settings page instead, and then back again once finished?

enter image description here

Any ideas or suggestions? Thanks.

usability – Why does the title attribute have a delay?

Without a delay just moving your mouse around would accidentally make popups appear and flicker across your screen.

That’d draw users’ attention away from what they’re doing if they didn’t expect it, and probably annoy them because flickering stuff provides no value to them: it’s unlikely they wanted to read the title and unlikely they even have the time to do it.

DreamProxies - Cheapest USA Elite Private Proxies 100 Private Proxies 200 Private Proxies 400 Private Proxies 1000 Private Proxies 2000 Private Proxies - Buy Cheap Private Proxies Buy 50 Private Proxies Buy 100 Private Proxies Buy 200 Private Proxies Buy 500 Private Proxies Buy 1000 Private Proxies Buy 2000 Private Proxies ProxiesLive New Proxy Lists Every Day Proxies123