yes it's partly clear :)
When a coherent database exists, the task is easier in the implementation context.
If we navigate the main interface (list function),
easily creating or adding a new list of candidates from any interface will add to the same database.
I understand that the problem in this context is switching between contexts / interfaces to ...
This is a very wide user case, so the answer will be DEPENDS.
First, if it has a dominant brand color, it would be advisable to have all the important elements (such as CTA) so that they are of a different color. This is called accent color.
However, in small decorative elements (such as the color bar in your sample forms), using the same dominant shade ...
Like Word collaboration documents you could include a side panel that automatically shows who the last person who updated is, what updates he did, this combined with a badge color. Then use the badge color to create flicker or something over the data that was just changed.
This is a standard design exercise that you can use to experiment and test ideas against your user group.
The basic ways to indicate changes and relate it to a specific user, number of users or just the latest user to change the information can be one of the following (or combinations thereof):
Visual: using the user's profile image in the proximity of the ...
If long text buttons is not an option for you then your can opt for other options.
Instead of button you can go with plain hyper link or an alternative to text can be an Icon image, but at times icons does not looks self explanatory, to tackle that problem you can add a tool-tip to the icon.
One thing that jumps out immediately is minor but makes transitioning a bit jarring: the row height changes. It might be better to the first column wide enough to accommodate content for all and leave the row height alone. Also, a decent palette can go a long way. The yellow on blue should at least harmonize, but unless those two colors are thematics for ...
I wouldn't recommend the 'x' icon, because it breaks with conventions. An 'x' typically closes a window or container (e.g. makes it vanish), so user might get the impression that the whole dropdown would be removed when clicking on that 'x'.
However, up and downward pointing chevrons are associated with expanding/collapsing content in the given direction, ...
What I understand from your observation is that, as any other design element, we have to look at them as a whole.
As @sanjai is saying, it is used to emphasis some content, but if you were using the same card design in all the page it wouldn't emphasis anything.
So, answering you question:
I would use the card design as if they were bullets:
To list ...
Card UI element is used to emphasis the content and also useful for grouping it together. Eg ; picture, content, CTA, Timestamp.
It also promotes to make the user click to view more details about it.
We can also use this style to align it flexibly. Eg : Pinterest.
Another thing to consider that the content / description / Title characters should be fixed. ...
I'm so glad, somebody raises that question. It's Microsoft's fault that you have to write such a long question, because they created that inconsistent mess.
Everything started with Microsoft making cross platform + touch input the top priority for Windows 8 and future Windows releases. That brang us
a Windows experience that was consistent with Windows ...
You've got a really nice reference on google forms (mobile and web).
I would not recommend at all making a unique long page. Users needs to flow, and if they think the task is gonna be long and boring they could drop off.
Here are some tips:
4_Always locate the user on the progress of the survey. Maybe with %, maybe with pagination.
2_If you are gonna ...
Try don't redo the wheel. Use global patterns of icons, names and functions.
See some tasks to define the best controls to use:
Have a look at what your competitors and similar tools are doing. Don't do too different because could increase the learning time.
Define what type of control do you need and analyse each one individually. List them and writes ...
Your objective is to have as many users completing the form as possible. It should be no longer than necessary.
I would put it to you that the reasons for completing the form and the advantages of doing so by the user can be achieved by copy outside the form and thereafter the bare minimum of fields: contact details (email/tel) > reason for contacting (...
There’s an “absolute” and a “relative” length of forms.
You are referring to the absolute length here - the number of form fields. As long as the fields are necessary and help the user in a significant way, there isn’t a form that’s too short.
The “relative” length of forms is subjective and based on what user perceives.
The shortest form (e.g. 2 fields) ...
The way you have designed and defined the use case for 'cards' seem to indicate that they are purely navigational components that don't provide any additional information to the user.
The best way to move away from detailed design upfront and take into consideration the overall information architecture of your site/application is to understand the ...