usability – Multi-draggable drop zone – User experience stack swap

I am looking to create a dynamic query builder, where a user can drag a field into a "values" section. When the user has dragged the field and wants to place it in the Values ​​section, I would like to create multiple drop zones so that they can choose with the type of aggregation calculation they would like to do. For example:

enter the image description here

Is there a JavaScript library or demo that can do this or show a demo example of a similar feature (or even a site reference that does something similar to this?)

usability: the best way to show the frequency

Do you know of any other way to represent a list of items that have their own frequency options (weekly, monthly, daily) from which to choose.
I was thinking maybe creating as a table and adding 3 checkboxes in each option or creating something similar to the segmented control. Example

I was also thinking of adding a dropdown menu where you can choose between these three options.
What do you think is the best option in my situation?

usability test: is this column view for answers feasible in a Survey type format?

I have a query about a question type I am working on for a survey design. What I wanted to find out was whether or not this question type (shown in the image below) was valid in UX terms. How difficult is it for a user to understand this type of format and what could be a better way to display this information?

enter the image description here

Here we have an example of the type of question where we want a user to rate the lighting of their workspace in the office and at home by selecting one of the options. When you select an option, it lights up. Once you have finished selecting the options in both columns (as shown below), you will automatically proceed to the next question.

enter the image description here

Can I get some advice or advice on whether this approach works or should be done differently?

I would really appreciate any help you can give me.

usability: need help with toolbar design

I have a toolbar that needs 4 controls and a company icon. I can't find the best location for controls and I can't find the best look for search controls and I need advice.

This toolbar has to have a
1. Menu button to open side navigation
2. A date and entry search box
3. An automatic update dropdown (similar to NZBGET) autorefresh
4. The company icon should go somewhere on the toolbar.

Here is the image of the current design layout that needs help.

User research: is it okay to run usability tests with non-customers?

I'm a designer for an orthopedic health technology startup that makes apps for orthopedic providers, and a recurring problem I have is extremely limited access to users for research and testing. Due in part to the incredibly busy work schedules, protective account managers, and fatigue from interviews, opportunities for valuable user time are scarce. This is especially relevant now because I am focused on optimizing the existing service within the platform that is geared towards an esoteric (albeit critical) provider role type, with only about 40 existing users. But given the challenges mentioned above, I'll be lucky if I can catch 8 for interviews and tests; But even those users will not be a reliable dataset, as many of these providers belong to different healthcare systems and therefore use this existing tool for very different workflows.

One solution I am considering is communicating with suppliers in this role who are not clients of my company, who do not use our application. I could see that this is fine for interviews, But I wonder if this will be problematic for usability testing as I would essentially be evaluating the effectiveness of my designs based on the performance of people who are not the end users.

Has anyone here experienced a similar problem? Whether you have it or not, I would love to hear your thoughts. Thank you!

usability: how to manage many levels of navigation before the main operation

I am designing a web application that needs 4 levels to manage the flowcharts, which is the main purpose of the application.
The structure goes something like this:

Company names – folder

Component names – subfolder

Group name – sub – sub – folder

List of flow charts

The problem is that the user must make 4 clicks to achieve his main task, how should the levels be grouped or restructured so that the process is efficient?

Drop-down menu that performs instant actions in a web application: is this an accessibility or usability issue?

Drop-down menus that take action on websites were frowned upon years ago because screen reader users didn't necessarily want to activate an item in a drop-down menu while browsing the drop-down menu to read all the different options. A "Go" button was recommended to actually activate the chosen selection. Is it still a problem for screen readers?

Today it seems that drop-down menus on websites and web apps that set values ​​instantly are a bit more common (although online editing may be more useful since the user has taken an explicit action, for example pressing "enter" or click outside the field to save it). ) However, I'm not sure how common drop-down menus are that set values, but also to take action in are.

In our system (which will be used almost exclusively on a desktop), it is assumed that the orders in this table will be processed one by one. Changing the value in the row-level drop-down menu would move the order to the next "State" and perform background processing. Although it's an expert system, it seems unconventional to me that the dropdown takes snapshots of the item in that row. Depending on the filter used, the row may disappear from the list. We could potentially add a "Are you sure you want to change the status?" dialog, but we want it to be as efficient as possible for our users, who will generally make many quick changes.

Is there a better way?


I designed a batch version of this, but this was rejected as an option while I was away, I was told because the managers of this team don't want to support batch processing.


usability – How a "Still not what you're looking for?" item should be seen?

I am creating a customizable work product page. Each job can be customized by the user according to what the provider specifies. However, if there is something you want that cannot be customized, you can order directly from the supplier asking for something different.

I am thinking of using medium size item "Still not what you are looking for? [Place an order]" after the "Personalization" section as user will first check if there is something customizable and then realize that Order is needed. The main problem here is coordinating the weight of this item versus the customization section. It is not a warning, but it should not go away. My current options for this item are:

  • As text: "Still not what you are looking for? [Link] Place an order -> [/ link]"
    as text
  • Box: [inside the box] Still not what you're looking for? Place an order [button] Order [/ button] [/ box]

Are there guidelines for this?

Usability: Is there any guide on canceling forms in iOS 13?

iOS 13 added the "swipe to discard" feature to form sheets. I'm trying to find the most practical way possible to manage saving and canceling my forms.

Screenshot of the calendar application form

In native applications

I took a look at the native iOS apps, but they are not consistent:

  • In Contacts, the form opens in full screen and has a "Cancel" button that asks the user if they really want to cancel their changes;
  • In Reminders, the form opens in a form sheet, it doesn't have a Cancel button, but it will show a question if you swipe down.
  • In Agenda, the form opens in a form sheet, but it has a "Cancel" button, and it will show a confirmation action sheet for the swipe and the … button.

Agenda action sheet when discarding or touching the cancel button

What I want to do

I think both the swipe down gesture and the cancel button can live together (like in the Calendar app).

If there is no change I don't think I have to ask the user for anything (just discard the form). This is common in native iOS apps.

If there is any change, I was thinking of showing different questions:

  • if the user touched the Cancel button, just ask for a confirmation (the button is quite difficult to reach);
  • If the user slid down, ask them what they prefer to do: save their changes or discard them.

The swipe action is new and fairly easy to activate when trying to scroll the form; It can also be a way for the user to cancel or save the form without having to reach for the buttons at the top of the screen (which bothers me a lot).

Do you have any ideas or information to improve this solution?

usability – Form: How to clarify multiple search paths in the user interface?

Background information:
I am working on an acute care healthcare application.
In this application, you can request personal data from the national government if you meet the following criteria:

1) If you have the patient's citizen service number


2) If you have the patient's date of birth, gender and last name


3) If you have the date of birth, gender and address of the patient


4) If you have a combination of 1), 2), 3)

All this information is displayed on a screen. Unfortunately, I can't load a screenshot, but I'll try to explain my problem:

  • This screen contains a total of around 25 entries that are related to the patient's personal data.
  • All of those entries are displayed at once (including citizen service number, date of birth, gender, and address)
  • You can only continue to the next screen if you have requested the personal data from the national government (A) and when the 8 required entries are completed (B)
  • To request the national government data, you must complete the data for one of the search routes 1), 2), 3), 4). So of those 8 required inputs, only 5 inputs can be used to request the remaining patient data from the national government.

The problem: Many of our end users think that all required entries (8) should be completed to request the remaining personal data from the national government. Other users don't know that there are multiple search paths as I explained before.

Question: How can I clarify that there are 3 (or 4) search paths in the user interface? And how can I make it clear that not all the required information is necessary to request the remaining data from the national government?