Back to top

Top 10 User Interface Design Principles

10 User Interface Design Principles

A website is considerably more than a gathering of pages associated by joins. It’s an interface, space where various things — for this situation, an individual and an organization’s or person’s web nearness — meet, impart, and influence one another. That communication makes an encounter for the guest, and as a web designer, you must guarantee that experience is in the same class as it can be.

Furthermore, the way into that is to consider your user first, preeminent, and consistently.

Fortunately, while web design is a generally new order, it owes a ton to the logical investigation of human-PC cooperation (HCI). Also, these 9 convenient rules directly from HCI examination will assist you with concentrating on your users when designing websites and applications.

Interface design, which centres around the format of the usefulness of interfaces, is a subset of user experience design, which centres around the master plan: that is, the entire experience, not simply the interface.

1. Know your users

To the exclusion of everything else, you need to know who your users are—all around. That implies knowing all the segment information your investigation app(s) can pull, yes. In any case, more critically, it implies comprehending what they need, and what disrupts the general flow of them accomplishing their objectives.

Getting to that degree of compassion requires more than a cautious investigation of details. It requires becoming acquainted with the individuals who utilize your website. It implies talking with them up close and personal, watching them utilize your item (and possibly others), and asking them inquiries that go further than, “What’s your opinion of this design?”

What are its objectives? What disrupts the general flow of them accomplishing those objectives? In what capacity can a website assist them with surviving or work around those difficulties?

Try not to stop at comprehending what your users need. Uncover further and find what they need. All things considered, wants are only outgrowths of requirements. On the off chance that you can address a user’s profound situated need, you’ll address their needs while additionally satisfying progressively central prerequisites.

The experiences you’ll reveal from investigating information and talking with users will educate each choice you make, from how individuals utilize your interface to what in particular sorts of the substance you’ll feature inside that interface.

2. Characterize how individuals utilize your interface

Before you design your interface, you have to characterize how individuals will utilize it. With the expanding commonness of touch-based gadgets, it’s a more significant worry than you may suspect. Simply take a gander at

Kindling: the application’s user experience is truly characterized by the straightforwardness and impulsivity of a basic swipe.

Individuals use websites and applications in two different ways: legitimately (by cooperating with the interface components of the item) and in a roundabout way (by communicating with UI components outside to the item).

Instances of direct communications

  • ‍Tapping a catch
  • Swiping a card
  • Moving a thing with a fingertip

Instances of roundabout communications

  • Pointing and clicking with a mouse
  • Utilizing key orders/alternate routes
  • Composing into a structure field
  • Drawing on a Wacom tablet


‍Sometimes, communication is simply excessively simple.
Who your users are and what gadgets they use ought to profoundly educate your choices here. In case you’re designing for seniors or others with constrained manual ability, you wouldn’t have any desire to incline toward swiping. In case you’re designing for journalists or coders, who essentially communicate with applications using the console, you’ll need to help all the regular console easy routes to limit time working with the mouse.

3. Set desires

Numerous communications with a webpage or application have results: clicking a catch can mean going through cash, deleting a website, or offering a belittling remark about grandmother’s birthday cake. What’s more, whenever there are outcomes, there’s additionally nervousness.

So make certain to tell users what will occur after they click that button before they do it. You can do this through design and additionally duplicate.

Setting desires with design

  • Featuring the catch that compares to the ideal activity
  • Utilizing a broadly gotten image, (for example, refuse can for an erase button, an or more sign to include something or an amplifying glass for search) in the mix with duplicate
  • Picking a colour with significant importance (green for a “go” button, red for “stop”)

Setting desires with duplicate

  • Composing clear catch duplicate
  • Giving directional/empowering duplicate in void states
  • Conveying alerts and requesting affirmation

For activities with irreversible outcomes, as for all time erasing something, it bodes well to inquire as to whether they’re certain.


‍In InVision, tapping the trashcan symbol doesn’t quickly erase a screen. Rather, it inquires as to whether you’re certain and tells you it can’t be fixed.

4. Foresee botches

> To blunder is human; to pardon, divine.

Alexander Pope, “An Essay on Criticism”

Individuals commit errors, yet they shouldn’t (generally) need to endure the results. There are two different ways to help diminish the effect of human mistake:

  1. Forestall botches before they occur
  2. Give approaches to fix them after they occur

You see a ton of slip-up counteraction procedures in internet business and structure design. Catches stay idle until you round out all fields. Structures recognize that an email address hasn’t been entered appropriately. Pop-ups inquire as to whether you truly need to surrender your shopping basket (indeed, I do, Amazon—regardless of the amount it might scar the helpless thing).

Foreseeing botches is frequently less baffling than attempting to fix them sometime later. That is because they occur before the delightful feeling of finishing that accompanies tapping the “Following” or “Submit” catch can set in.

All things considered, now and then you simply need to allow mishaps to occur. That is when point by point mistake messages truly make their mark.

At the point when you’re composing mistake messages, ensure they complete two things:

  1. Clarify the issue. E.g., “You said you were conceived on Mars, which people haven’t colonized. However.”
  2. Disclose how to fix it. E.g., “If you don’t mind enter an origination here on Earth.”

Note that you can take a page from that equivalent book for non-blunder circumstances. For example, on the off chance that I erase something, however, it’s conceivable to reestablish it, let me realize that with a line of duplicate like “You can generally reestablish erased things by setting off to your Trash and clicking Restore.”

The guideline of foreseeing user blunder is known as the poka-burden standard. Poka-burden is a Japanese expression that means “botch sealing.”

5. Give input—quick

In reality, the earth gives us input. We talk, and others react (for the most part). We scratch a feline, and it murmurs or murmurs (contingent upon its irritability and the amount we suck at feline scratching).

Very frequently, computerized interfaces neglect to give much back, leaving us pondering whether we ought to reload the page, restart the PC, or simply throw it out the closest accessible window.

So give me that stacking liveliness. Make that catch pop and snap back when I tap it—yet not all that much. What’s more, give me a virtual high-five when I accomplish something you and I concur is amazing. (Much appreciated, MailChimp.)


‍‍MailChimp offers both criticism and support when you plan or send an email.
Simply ensure everything happens quickly. characterizes any postponement more than 1 second as an interference. More than 10 seconds, an interruption. Furthermore, the last’s liberal: for about a large portion of the U.S. populace, 3 seconds is sufficient to cause a bob.

On the off chance that a page will stack in less than 5 seconds, don’t show an advancement bar, as it’ll make the stacking time appear to be longer. Rather, utilize a perception that doesn’t suggest progress, similar to Mac’s notorious “pinwheel of death.” But not that. If you do utilize progress bars on your site, consider attempting some visual stunts to cause the heap to appear to be quicker.

6. Ponder component arrangement and size

Fitts’ Law, an essential rule of human-PC connection (HCI), states that:

An opportunity to gain an objective is an element of the separation to and size of the objective.

At the end of the day: the closer and additionally greater something is, the quicker you can put your cursor (or finger) on it. This has a wide range of suggestions for connection and user interface design methods, yet three of the most significant are:

Make catches and other “click targets” (like symbols and text joins) sufficiently large to effectively observe and click. This is particularly significant with typography, menus, and other connection records, as lacking space will leave individuals tapping inappropriate connections over and over.

Make the catches for the most widely recognized activities bigger and increasingly conspicuous.

Spot route (and other basic interactive visual components, similar to look through bars) on the edges or corners of the screen. This last may appear to be unreasonable, yet it works since it decreases the requirement for precision: a user doesn’t have to stress over overshooting their snap target.

While you’re pondering component putting and size, consistently remember your connection model. On the off chance that your site requires flat looking over as opposed to vertical looking over, you’ll have to consider where and how to signal users to this strange connection type.

7. Try not to disregard norms

Being profoundly imaginative sorts, designers will in general love to reevaluate things—yet it’s not generally the best thought.

Why? Since a patched up form of a recognizable connection or interface includes “psychological burden”: it makes individuals reconsider a procedure they’ve just learned. You can rehash an already solved problem all you need—however just on the off chance that it improves the design.

This dependable guideline clarifies why Google Docs’ menu bar includes practically no different alternatives as Microsoft Word’s before Vista:


‍Microsoft Word’s menu bar before Vista.


‍Google Docs’ menu bar, 2015
‍It additionally discloses why Pocket needed to change the arrangement of the file button in their Android application a couple of years back.

‍‍Changing a solitary catch to be progressively steady with Android’s design designs made new users 23% bound to continue utilizing Pocket.

Up till fall 2013, the document button was at the upper left of the screen—right, where Android design specs said the “Up” catch, ought to be. Pocket needed to concentrate individuals on the understanding experience, and not copy a current equipment control, yet the conflicting arrangement made new users coincidentally close and file the article they were perusing, as opposed to just coming back to their perusing list true to form.

That small change “improved the probability [new users] would keep utilizing Pocket starting here onwards by 23%.”

8. Make your interfaces simple to learn

With regards to effortlessness, individuals frequently refer to a paper by Harvard analyst George Miller called, “The Magical Number Seven, Plus or Minus Two: Some Limits on our Capacity for Processing Information.” The article recommends that individuals can just hold 5 to 9 things in their transient memory with any unwavering quality. Mill operator himself called this a happenstance, however, that doesn’t appear to keep anybody away from referring to him.

All things considered, it’s just sensible that the less complex something is, the simpler it is to recall temporarily. Along these lines, at whatever point conceivable, limit the number of things an individual needs to make sure to utilize your interface proficiently and viably. You can encourage this by lumping data, i.e., breaking it into little, absorbable pieces.

This thought dovetails with Tesler’s Law of Conservation of Complexity, which expresses that UI designers should make their interfaces as basic as could reasonably be expected. That can mean concealing the multifaceted nature of an application behind a streamlined interface at whatever point conceivable. A famous case of an item neglecting to adhere to this law is Microsoft Word.

A great many people just do a couple of things in Word—e.g., composing—while others can utilize it to do a wide range of ground-breaking things. Yet, around the globe, everyone opens a similar form of Word, with the equivalent UI, leaving your regular person—who’s not a force user—overpowered by the assortment of choices they’ll likely never use.

This prompted an idea called dynamic revelation, where best in class highlights are concealed on auxiliary interfaces. You’ll frequently observe this on websites’ home pages, where short pieces of duplicate present an item or highlight, at that point connect off to a page where users can find out additional. (This likewise happens to be a best practice for versatile design, where the powerful route is consistently a test.)

Genius tip: Avoid utilizing “find out additional” and also vague content in connections and catches. Why? Since it doesn’t mention to users what they’ll “find out progressively” about. Regularly, individuals examine a page searching for a connection that takes them where they need to go, and “find out increasingly,” rehashed multiple times, doesn’t help. This is particularly valid for users of screen perusers.

9. Settle on dynamic straightforward

A lot of the web shouts at us: “Flags” out of nowhere grow to turn out to be full-screen advertisements. Modals spring up, entreating us to buy into websites we haven’t got an opportunity to, you know, read at this point. Video interstitials leave us speechless, compelling us to observe valuable seconds tick goodness so-gradually by. Furthermore, don’t kick me off on the gadgets, flyouts, tooltips …

Here and there I long for a more settled web—and Hicks’ Law gives all of us motivation to fabricate one. The thought’s as basic as its final product: the more UI choices you present a user, the harder it becomes for them to settle on a choice.

This effects nearly all that we fabricate:

  • By and large designs
  • Route menus
  • Valuing pages
  • Blog records
  • Content feeds

The rundown goes on. In any case, the aftereffect is: the more straightforward we make our designs, the quicker and simpler it is for users to settle on the choices we need them to make. That is actually why points of arrival and non-pamphlet messages should just have one source of inspiration.

Genius tip: Sometimes, you need users to back off and think about their alternatives. That is the reason the tiled designs of Pinterest, Dribbble, and numerous online journals function admirably. All things considered, the more alternatives you need to settle on, the more probable it is you’ll see one that works for you.

10. Tune in to the information

While we as a whole would wish our designs were assessed simply on their masterful legitimacy, actually enhancing your design to meet its goal is similarly as significant.

While we as a whole would wish our designs were assessed absolutely on their creative legitimacy, actually advancing your design to meet its goal is similarly as significant.

While user examination and testing can be inconceivably useful in controlling your design choices toward satisfaction of your site’s objective, information accumulated after dispatch stays significant.

So set up the investigation for your site, and break down them routinely. There’s a lot of various investigation apparatuses out there, yet I suggest Google Analytics or potentially Mixpanel, contingent upon the task type.

Mixpanel centres around occasions, so it gathers information dependent on moves a guest makes on your site, while Google Analytics is increasingly social, giving you meeting times, traffic sources, and so on. While the two apparatuses can give the two types of information, they truly sparkle in their central regions, so pick whichever best meets your requirements.

Alright, you’ve nailed the fundamentals

Presently go forward and make some dazzling, usable interfaces. What’s more, don’t hesitate to share the best—and most noticeably terrible—instances of UI design you’ve found in the overall wilds of the web in the remarks.