Empathy is your friend here, and empathy in UX is critical. The ability to put yourself in the customers shoes should be intrinsic to anyone wanted to practise UX.
With that in mind, think how you would feel if you suddenly lost access to a service on which you, perhaps, rely heavily. Especially if the reason for non-payment is due to personal ...
I think it depends on the button:
If the button is too obvious as the button to close a modal window I
don't think it's necessary.
If the button is to clarify an immediate operation it can be
useful. In fact this page has tooltips on all its buttons:
When you have too much content and little space, you should categorize your content and make a separate page for each content category. Besides, you need knowledge of an information architect. you can start card sorting or alternative options and categorize your content based on users minds.
Trust has multiple dimensions and can be built through familiar interaction patterns, effective writing, and branding. Frameworks are only one dimension.
What interaction frameworks (and patterns) are your users more likely to be exposed to?
An interaction framework is used both to save development resources, but from the users point of view, ...
How to name a page? Here's a technique to try:
Ask yourself two questions: (1) Why are we making users do these things? (2) Why are they all on the same screen?
Answer the questions aloud. Talk to one of your colleagues about it. Ask them the same questions. Get conversational. Say a lot about it. Jot down the significant words you use in your answers. ...
Consider marking only the files that need user attention.
Having icons for the good, bad, and indifferent can clutter up the report and make it hard for the user to find the information that is important to them.
If files that are good or not required do not need any user action, they may not need an icon. That would draw more attention to the bad files (...
My suggestion would be to place the button underneath the list of variants and add the variants downwards. For indication i placed a small label on the new variant to make it easy to differentiate but keep the list scan-able. I also placed a "delete"-icon on the variant because the user might want to remove an variant, you could also add an "edit" or "move"-...
If the website may be used in mobile, tooltips may not be a good solution since most are initiated by some kind of hover.
If the information can be conveyed after the button is clicked, perhaps a toast notification could help. This provides an immediate notification upon interaction which will likely satisfy the user, but be passive enough to ignore if so ...