Key Rules of UI Design


Agile Product Development

Close Banner

Free Template & Financial Spreadsheet

Create your SaaS business plan

Sign Up

Your user interface is a critical component of your software product. It's the tool that your users use to access the application. If your UI is effective and efficient, your users won’t notice it, which is why most UI designers follow some fundamental principles.

In this article, we’d like to share a few key UI design principles. These are based on Jakob Nielsen’s 10 Usability Heuristics for UI Design, Ben Shneiderman’s The Eight Golden Rules of Interface Design, and Bruce Tognazzini’s Principles of Interaction Design, as well as some of our own thoughts.

1. Use aesthetic and minimalist design

Keep your UI to a minimum. Don’t clutter it with unnecessary visual elements. Eliminate any information that doesn’t help the user in their immediate task. Reduce your display to only the necessary components without sacrificing the information they do need at the time. Anything that doesn’t belong won’t just get in the way - it will actually confuse your users.

Additionally, use language that is easy to read and understand. The system should speak the user’s language. You shouldn’t force the user to learn new system-oriented terms just to use the product.

Finally, it’s important to design your UIs for people of all ability levels, including those with low vision, hearing impairments, color challenges, or motor impairments. Great UIs are accessible to all groups.

2. Strive for consistency

A consistent interface is one where the same design patterns and action sequences are used for similar situations. This includes layout, typography, color, language, screen flow, commands, menu items, and other elements.

For example, buttons that confirm actions should be styled similarly so users know they are committing to something. If you use a check mark icon to indicate that an action is complete, you should use that icon for all completed actions. But don’t use that icon for anything else!

3. Give users shortcuts

Frequent users who grow comfortable with your product want tools to use it faster. Provide them with abbreviations, macros, functions, or other shortcuts to help them personalize their experience and complete tasks quickly. Note how this menu offers shortcuts for functions you might repeat often.

user shortcuts example

That said, it’s important to keep the traditional methods of taking action available. You shouldn’t, for instance, remove your action menu from a screen because you assume the user will just use a shortcut.

4. Provide clear system feedback

It’s important to keep your users informed about what’s happening during each stage or screen of your application, especially if they just took some kind of action. This type of feedback should be relevant, clear, and meaningful.

The loading bar is the clearest example of this. A simple percentage indicator is often enough to make users feel comfortable that things are moving along, if they don’t understand what’s happening.

system feedback example

5. Make it easy to “undo”

Have you ever clicked the wrong button or made a mistake and panicked a little because you thought you did something irrevocable? We all have, which is why it’s so important to give users an opportunity to reverse. Plus, simply knowing they won’t be held accountable for their mistakes makes users much more comfortable with your product.

How you give users this power will depend on the nature of your product. In some cases, a simple “undo” button is all they need. In other cases, you may want to give them access to an entire log of action or a history of versions.

6. Provide help documentation

If a user requires help, ensure that there’s somewhere to learn more about the problem and solve their issues. You might store your documentation on a knowledge base site or include within the application using tooltips. Make sure that the content of your help documentation is relevant and useful.

Notice how Photoshop makes their help documentation accessible directly within the app. Users can open the help window in numerous ways so it’s always right there when they need it.

help documentation example

7. Reduce short-term memory load

Our attention span is limited. We can only maintain around five items in our short-term memory at one time, so we shouldn’t expect users to remember much. It’s more effective, therefore, to ask them to recognize information rather than recall it.

For instance, an ecommerce app might remind users what they recently viewed or purchased instead of expecting them to remember. Even a simple prompt such as “Are you sure you want to delete photo.jpg?” prevents the user from having to remember what they selected to delete.

Furthermore, you can reduce their cognitive load by limiting the number of actions required to complete a task. Long sequences are tedious and frustrating, so any task should be achievable in three clicks or less.

8. Give plenty of closure

Each sequence of action should have a beginning and end (and sometimes a middle). The purpose here is to close the gap so users aren’t left confused.

The beginning is the user’s action, such as clicking a button. The middle would be the information feedback that the action is happening (such as a loading icon). The end would be a message or indication that the action is complete or an error message that explains why it wasn’t completed.

Oh, and speaking of errors…

9. Make error handling simple

Ideally your app won’t have any errors, but that’s not really possible. When an error occurs, your application should clearly explain what happened and how the user can solve it. Often this is as simple as adding an in-app message that explains the problem so the user can fix it.

sign up flow example

In other cases, an in-app solution may not be possible. It’s important to make your error text unique so users can look it up in your documentation. You can also pair it with an error code.

10. Match your system to the real world

Aligning your app with the real world is key. Wherever possible, you should match the language and concepts users find in the real world to the same language and concepts in your application. This makes your app intuitive and helps users understand and operate it quickly.

For instance, most menus in the world use a logical flow where parent items represent broad categories and child items represent smaller categories. This hierarchical design is everywhere - restaurant menus, road signs, newspaper articles, etc. If you deviate from this style, you will most likely confuse your users.

The recycling bin on your desktop is another common example. It’s not a real recycling bin, obviously, but its visual representation helps users understand the concept.

11. Gives users a locus of control

Locus of control refers to the degree in which people believe they have control over an outcome. It’s important for your users to feel like they have freedom and agency within your system. This means you can’t hijack them with interruptions, forced or locked sequences, and other surprises.

Aim to let your users be the initiators of every action. Does this mean you should never prompt them? No, but if you do interrupt them, make sure it’s for a good reason.

12. Ensure accessibility

Your SaaS product should be accessible and understandable by every user, regardless of their literacy level and visual acuity. Sadly, about 20% of the U.S. population is illiterate, while 8% of Americans have visual impairments. Help people in these groups access your software and experience value by keeping your UI as easy to understand and navigate as possible.

For example, people with poor vision will have an easier time navigating your SaaS product if you use colors to distinguish buttons. What if a user is color blind? Such users are why accurately labeling buttons is crucial. Less-learned users will also benefit from using colors and distinct symbols to distinguish buttons. For instance, using a red X mark for the “No” or “Stop” buttons and a green checkmark for “Yes” or “Continue” buttons will ensure easier understanding of each button’s function.

13. Implement function prioritization

Most users visit your SaaS app to perform one or two primary functions. It doesn’t make sense to hide the buttons for executing these commonly performed functions. Instead, prioritize the buttons for these essential functions by making them easy to find and access. The buttons for less frequently used functions can be in a cascading menu or lower placement on lists.

Alternatively, make essential functions easier to see by putting them first and using bigger buttons and bolder text to showcase them. A good example you see frequently is in Gmail accounts. “Compose” and “Inbox”, the two most frequently used functions, come first with clearly differentiated text.

function prioritization example

14. Keep it clean

While differentiating essential functions from non-essential ones is crucial, avoid going overboard with different colors and styles. For example, if you have five functions, the text for each function doesn’t have to be a different color.

Unnecessary colors and visual styles make your UI busy and distracting, increasing the likelihood of cognitive overload. Prevent such an outcome by avoiding unnecessary lines, colors, backgrounds, font variations, and animations. Instead, aim for a minimalistic design that keeps things simple and uses colors purposefully.

A SaaS platform that does this effectively is the Grammarly typing assistant. As you can see in the screenshot below, the Grammarly page uses the same font type and color for most texts and bolds the crucial messages. It also purposefully applies color by using its brand color for CTAs and other colors to distinguish issues identified in the user’s writing.

grammarly clean ui design example

15. Iterate continuously  

Another key rule of UI design we adhere to is continuous iteration. Continuously iterating requires not viewing the design process as a short, one-time flight. Instead, see it as a repeated roundtrip that keeps getting better, bringing you closer to your goal – building the perfect SaaS product.

Continuous iteration involves creating a version of your product, testing it, and implementing user and stakeholder feedback to improve the next version. Improving your product based on user feedback doesn’t have to require overhauling your whole software. Just a small change can be enough to make your SaaS product more attractive and engaging. For example, little changes to the checkout page’s text, process, or design can help boost conversion rates and sales.

You can also get insights to improve each iteration by analyzing your pages to identify the ones with high bounce rates or poor conversion rates. You can then run A/B tests to identify versions of these pages that deliver better results. In summary, with continuous iteration, your SaaS product can keep getting more beautiful, user-friendly, and profitable.

4 core pillars of user interface design

You’ve seen the key rules of UI design we follow to deliver engaging, responsive, and attractive SaaS products that help businesses achieve their goals. All the rules we discussed rest on four cardinal pillars of UI design. Regardless of your niche in the SaaS industry, your app or web design shouldn’t stray from these four core principles, which are:

4 pillars of ui design

1. Consistency throughout your SaaS software

Your user interface should have a consistent look and feel across all pages. For example, you can’t have a homepage with a blue background and other pages with a different color scheme. Maintain consistency across your software by ensuring elements like colors, fonts, buttons, interactions, and tone match on all pages.

Aesthetic consistency prevents distraction, confusion, and disjointedness that can make your SaaS product look unprofessional and poorly put together. Consistency also gives users a sense of familiarity that makes your website predictable and familiar, regardless of the pages users visit. This leads to clarity, which in turn leads to intuitive navigation that ensures a seamless user experience.

2. Hassle-free access for users

Your SaaS product should be as intuitive and user-friendly as possible. Otherwise, users will have a frustrating experience that increases bounce and churn rates. A user-friendly and intuitive software ensures users can navigate, find what they want, and complete actions without assistance.

You can ensure a hassle-free user experience by making buttons visible and providing clear information. The information will guide users as they journey through your software to complete tasks. All links, images, text, and other content should have a definitive purpose on a page and be in a structure that makes sense. Also, eliminate unnecessary steps and optimize interactions to boost user productivity.

An inefficient and poorly put-together UI will cause friction and delay the user's journey to experiencing value. For example, having to visit multiple pages to complete a single task or trouble finding the button to proceed to the next step can frustrate users. Keep users happy and productive on your SaaS app by ensuring users understand the purpose of each UI element at a glance. 

3. Give users control

A well-developed UI puts a user in charge of their user journey through your software. Even if you have a complex product, users should be able to find their way around it and complete tasks without assistance. Giving users control benefits customers because they can get more done faster and benefits your business because you can spend less on customer support.

However, it’s not enough for users to be in control of their journey. Users should also know their progress as they journey through your system. For example, after performing an action, users should see notifications that indicate if the task was successful or not. 

order progress exampleAnother example is the indicator that reveals if a user’s new password is strong or weak while a user sets up a new password. new password example

4. Feedback at the core

Building a SaaS product without user feedback is one of the most effective ways to waste money and time. You are building your product because you want people to like and use it. So, ask the people what they want and use their feedback to tailor your product to match the needs and preferences of your target audience. This uncomplicated concept is what makes feedback a core pillar of UI design.

You can get user feedback through interviews, surveys, and social listening. However, collecting user feedback shouldn’t stop after the product launch. After your product goes live, continue collecting feedback to discover new ways to improve your product and keep it relevant and valuable to your target audience.

Key takeaways

We’ve given you a set of UI design best practices that will push you in the right direction. They are applicable to most interfaces, but they are only the beginning. These design rules can only take you so far. Use them as a starting place, then run your own experiments to determine what works best for your application and users.

Close Banner

Building a product?

Discover the DevSquad Difference

Learn More