Home  /  Blog  /  Blog Articles About UX, UI, Research and Development
Blog Articles About UX, UI, Research and Development

UI Design: Did you know this 7 tips formula for success?

March 13, 2019Blog Articles About UX, UI, Research and Development2 min read
Table of contents
  1. Key takeaways
  2. The 7 tips

A UI project fails for predictable reasons: overconfidence, no time, no process. These seven tips give you the foundation that keeps designs on track.

Quick answer

The seven UI design tips are: start with research (benchmarking, personas, wireframes); build in accessibility; use color theory deliberately; work on a grid; design for different devices; create a design system; and finish with a checklist. There is no UI without UX, and no UX without research, so research is where every UI project starts.

Key takeaways

  • There is no UI without UX, and no UX without research.
  • Accessibility is not optional; nearly 20% of people have some accessibility need.
  • Grids help both the look and the developer who has to build your design.
  • Design systems bring consistency and cut development time.
  • A final checklist (spelling, alignment, interactions, standards, assets) catches costly misses.

The 7 tips

1. Research

No UI without UX, no UX without research. Even a little goes far: competitor benchmarking, personas or proto-personas, wireframes, a simple user test, and formulas like Fitts’s Law to check whether an element works.

2. Accessibility

It is the law in most countries and, more importantly, it is the right thing. Around 20% of people have some partial or total, permanent or situational accessibility need. See the 9 visual accessibility principles.

3. Color theory

Color psychology is not exact, but certain colors reliably shift how users feel. Use it deliberately to calm or excite, to signal safety or warning. Color is an ally when it fits the purpose.

4. Use grids

Your interface has to be coded eventually. Grids make it look ordered and make the build easier, especially responsive. Ask the developer if they need a specific grid (Bootstrap, Foundation, an 8pt grid) before you design.

5. Design for different devices

How does it look on desktop, mobile, tablet, 4K? Are CTAs still visible? Which platform and standards apply (iOS and Android HIG, Material Design)? Ask these at the start, not the end.

6. Create design systems

A design system keeps screens consistent, helps users scan and understand affordances, and shortens development because there is no doubt about which element to use.

7. Create a checklist

Before delivery, review everything. There is no one-size-fits-all checklist, but a good one includes:

  • Did you apply the tips above?
  • Check spelling.
  • Check vertical and horizontal alignment, consistently.
  • Review interactive elements; a pretty interface that does not work is useless.
  • Respect standards (ISO 9241, usability, accessibility); use real labels, not just placeholders.
  • Confirm and deliver the required assets.
What are the key UI design tips?

Research first, build in accessibility, use color theory, work on a grid, design for multiple devices, create a design system, and finish with a checklist.

Do you need research for UI design?

Yes. There is no UI without UX and no UX without research. Even lightweight research (benchmarking, proto-personas, wireframes) transforms the result.

Why use a grid in UI design?

Grids make the interface look ordered and make development easier, especially for responsive layouts. Ask the developer which grid they need.

What should a UI design checklist include?

Spelling, consistent alignment, working interactive elements, adherence to standards and accessibility, and delivery of the required assets.

Why is accessibility part of UI design?

It is legally required in most countries and roughly 20% of people have some accessibility need, so it directly affects usability and reach.

Want UI built on research, grids and a real design system? Talk to Dorve.

Start a project

Want a team that knows the theory?

We research, design and build with people who can tell when an answer is wrong. Tell us what you are working on.

Start a project