Skip to content

UI/UX

What Is an Interface? Meaning, Types and Examples

What an interface is: the point of contact between people and systems. See its meaning, 7 types with examples and how it differs from UX and UI.

Published on March 19, 2026. Updated on November 17, 2026. 10 min read

An interface is the point of contact between two parties that need to exchange information: a person and a system, or two systems. In digital products, it is everything that lets you see, tap, type, speak and get a response, such as screens, buttons, voice commands and APIs. A good interface gets people where they want to go without making them think about the path.

This guide covers what interface means, the main types with everyday examples, the difference between interface, UX and UI, and how an interface is built in a digital product, from mapping to code.

What interface means

The word comes from the idea of a "face between": the surface where two sides meet. That is why it shows up in different contexts. In computing, the interface is the layer that translates what a system does for the person using it. In electronics, it is the physical connector between two devices. Between programs, it is the contract that defines how one piece of software talks to another.

In every case the job is the same: hide complexity on one side and give the other side a simple, predictable way to interact. When you tap "pay" in your banking app, you do not see the validation, the server call or the transaction record. You see a button, a confirmation and a receipt. That is the interface.

Types of interface, with examples

Seven types of interface
  1. Graphical (GUI): Windows, icons, menus and buttons. Websites, apps and systems.
  2. Command line (CLI): Text commands in a terminal. Developer tools and servers.
  3. Touch: Gestures on a screen: tap, drag, pinch. Phones, tablets and kiosks.
  4. Voice: Speech as input and output. Voice assistants and phone support.
  5. Conversational: Text dialogue. Support chats and in-app assistants.
  6. API: The interface between systems. Payments, login, maps and integrations.
  7. Physical: Keys, buttons, controls and sensors. ATMs and control panels.

Graphical user interface (GUI)

The best known: windows, icons, menus, fields and buttons used with a mouse, keyboard or touch. Websites, mobile apps and business systems all use graphical interfaces. The challenge is clarity: every screen must make the next step obvious. For Itaú Mulher Empreendedora, the learning platform was designed with accessibility and simple navigation so that entrepreneurs with different levels of digital familiarity could find content effortlessly.

Command-line interface (CLI)

The person types text commands and the system answers in text. It looks old, but it remains essential for developers and infrastructure teams because it is fast, precise and easy to automate. Examples: the computer terminal, code versioning tools and server administration.

Touch interface

Direct gestures on a screen: tap, swipe, drag, pinch to zoom. Phones, tablets, self-service kiosks and car dashboards use this model. Touch target size, placing elements within thumb reach and instant feedback on every gesture make all the difference.

Voice interface

Speech replaces the click. Voice assistants, automated phone support and in-car commands are examples. Since there is no screen to show options, the interface must guide people with short questions, confirm what it understood and offer a way out when it does not.

Conversational interface

Text dialogue becomes the path to the task: support chats, in-app assistants and bots in messaging apps. It works well for tasks people can describe and worse for exploring options. In most products it complements the graphical interface instead of replacing it.

API: the interface between systems

Not every interface is made for people. An API (application programming interface) defines how one system requests and receives data from another. When an app shows a map, processes a payment or lets you sign in with an existing account, it is using APIs. A well-designed API has clear rules, documentation and predictable responses, just like a good screen.

Physical interface

Keys, buttons, levers, controls and sensors. The ATM keypad, the elevator panel and the remote control are physical interfaces. More and more they combine with screens, as in kiosks and car dashboards, and the design has to consider both parts together.

Interface, UX and UI: what is the difference

The three terms go together, but they are not synonyms.

  • Interface is the point of contact itself: the screen, the command, the API.
  • UI (user interface) is the design of that surface: layout, typography, colors, components and visual states.
  • UX (user experience) is the whole experience: whether people understood, completed the task and left satisfied, including flows, content, speed and even support.
UI and UX
  • UI
    • What the screen looks like: Layout, typography, colors and components.
    • Visual consistency
  • UX
    • How the experience flows: Flows, content, speed and outcome.
    • Task completed without effort

The interface is where both meet.

A beautiful interface with a confusing flow fails at UX. A logical flow on a cluttered screen fails at UI. Both have to be designed together from the start, and the user journey is the map that connects them.

What makes a good interface

  • Clarity: each screen has one main goal and makes the next action evident.
  • Consistency: the same button does the same thing everywhere, with the same names and patterns.
  • Immediate feedback: every action has a visible response, such as loading, confirmation or an explained error.
  • Error prevention: validation at the right moment and confirmation before irreversible actions.
  • Accessibility: contrast, font size, keyboard navigation and screen readers.
  • Speed: a slow interface is a bad interface, however good it looks.

How an interface is built in digital products

From need to a live interface
  1. Requirements and journey: Who uses it, for what and in which context.
  2. Wireframes: Screen structure and flows, without styling.
  3. Prototype and validation: Tests with real people before code.
  4. Visual design and design system: Reusable components, states and rules.
  5. Development: Front end connected to the back end and APIs.
  6. Measurement and evolution: Funnels and real usage guide the next release.

With metrics, the cycle restarts at every release.

1. Understand who uses it and why

Before drawing any screen, we map who will use it, in which context and what task needs to get done. That becomes requirements and a journey map. In the GTS project, organizing the sales operation before designing the site cut time spent on requirements by up to 80%.

2. Wireframes and flows

Wireframes are sketches of screen structure, without colors or images. They let the team discuss hierarchy and flow without aesthetic distraction. At Bom Controle, we started with prototyped wireframes to validate interactions and flows before the creative concept, which ensured high fidelity between design and the final product.

3. Prototype and validation

A clickable prototype simulates the product. Putting it in front of real people reveals where they get stuck, what they do not understand and what is unnecessary. Fixing things here costs a fraction of fixing them after code.

4. Visual design and design system

Once the flow is validated, typography, colors, icons and components come in. A design system gathers these elements and their states (default, focus, error, loading, empty) so the product can grow without losing consistency. That care for the brand guided the new Magazord website, built to reflect the size of one of Brazil's largest e-commerce platforms.

5. Development

The front end turns the design into code, connected to the back end and APIs. This is where the interface gets real behavior: live data, validations, error messages and performance. Design and development working together avoid a gap between what was approved and what ships.

6. Measurement and evolution

A live interface is a hypothesis under test. Funnels show where people give up, and usage per feature shows what really matters. In the products UEEK hosts, these metrics are in place from day one. See metrics from day zero.

Frequently asked questions

What is an interface in a few words?

It is the point of contact that lets a person use a system, or lets two systems exchange information. Screens, buttons, voice commands and APIs are all interfaces.

What is the difference between interface and user interface?

Interface is the broad concept and includes communication between systems, such as APIs. User interface (UI) is specifically the part people interact with, and its design.

What is a graphical interface?

An interface based on visual elements, such as windows, icons, menus and buttons, used with a mouse, keyboard or touch. Websites and apps are the most common examples.

Is an API an interface?

Yes. API stands for application programming interface. It defines how one piece of software requests and receives data from another, without a person interacting directly.

Who creates the interface of a digital product?

Usually a team with UX and UI designers, who design flows and screens, and front-end developers, who turn the design into code. Requirements and user testing feed the process.

How do you know if an interface is good?

By how people behave: whether they complete the task, how long it takes and where they give up. Funnel metrics and user testing answer better than opinion.

Does your company need a system? Take the AI Map

Many hard-to-use interfaces come from a system designed without looking at the process: screens that copy the old spreadsheet, steps nobody uses, the same data typed in two places. Before designing the first screen, it helps to know which processes in the company need a system and where AI can already handle part of the work, such as reading documents, filling in records or answering recurring questions.

The AI Map is a free assessment: you answer a few questions about your operation and get the opportunities ranked by effort and impact. With that in hand, UEEK, with 14 years in the market, 200+ clients and 500+ projects across 6 countries, designs the interface through Design and UX and builds the system with custom development.

Take the AI Map

Topics

  • what is an interface
  • interface meaning
  • types of interface
  • graphical user interface

Want this in production?

UEEK does this kind of work in Design and UX.

See the solution