In software and interface design, look and feel is the overall impression a product makes on the people who use it. The “look” is the visual layer: colors, typography, graphics, logos, and branding. The “feel” is the experience of interacting with the product: how controls respond, how information is arranged, and how animation, transitions, and interface wording shape use. The phrase is a convenient label rather than a precisely standardized technical term, so the most useful definition is one that states which parts of the product a team means.
What the phrase means
The Cambridge Dictionary gives a computing sense of the phrase: the way that something, typically software or a website, appears to a user or customer, and how attractive or easy to use it is. That definition joins two questions that are often separated in design work, namely how the product appears and how pleasant or workable it is to operate.
As an Amazon Associate I earn from qualifying purchases.
Microsoft’s MSDN Magazine article “Usability in Practice: More Than Skin Deep” (December 2009), published alongside Microsoft Learn, frames the term as the product’s overall impression or personality. It makes a practical distinction: “look” points to visual characteristics, while “feel” describes the quality of interacting with the product. The same article cautions that the phrase is not especially well defined, so writers should explain which aspects they mean rather than assume every team uses it the same way. The article is credited to the publication rather than to a named individual author.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →The look: the visual layer
The look is what a user sees before touching anything. In most interface discussions it includes:
- Color palette, including the accent colors used for calls to action and status messages.
- Typography, meaning typeface choices, sizes, and hierarchy.
- Graphics and iconography, such as illustration style and icon set.
- Logos and branding, and how consistently they appear across screens.
- Layout, the spacing and arrangement of elements on the page.
The feel: the interaction layer
The feel emerges from use over time. It is shaped by:
- Interaction behavior: how controls behave, and what feedback a user gets when they click, type, or drag.
- Animation and transitions: how screens and elements move between states.
- Information architecture: how content is grouped, labeled, and reached.
- Interface language: the wording of labels, prompts, and messages, and the tone it conveys.
Look and feel are separate enough to discuss on their own, but in a finished product they combine into one impression. A bright, friendly palette paired with slow, unresponsive controls produces a different overall impression than the same palette with immediate feedback.
How look and feel differ from user experience
The phrase is narrower than “user experience.” It describes an interface’s overall character and experiential qualities, while user experience can refer to the wider experience of a product, including support, onboarding, and the context of use. The table below shows where each term fits.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors| Term | What it covers | Typical examples |
|---|---|---|
| Look | Visual characteristics of the interface | Palette, typography, graphics, logo, layout |
| Feel | Quality of interacting with the interface | Control behavior, feedback, animation, information structure, interface language |
| Look and feel | The combined overall impression of the interface | A product that appears formal and responds quickly, or appears friendly and moves slowly |
| User experience | The broader experience of using the product | All of the above plus onboarding, documentation, support, and context of use |
Describing a look and feel in practice
When a team needs to describe the look and feel of a product, a practical description names the intended qualities and then points to the design choices and behaviors that produce them. Adjectives such as formal or friendly are a common way to discuss the feel, and Microsoft’s article uses adjectives and metaphors in this way. Treat any adjective list as a working vocabulary for a team, not as a formal standard.
A workable process looks like this:
- Name the intended qualities. Choose two to four adjectives that describe the impression you want, such as calm, precise, or playful.
- Map them to visual choices. Specify the palette, type scale, iconography, and layout that support each quality.
- Map them to behaviors. Specify feedback timing, transition style, and how controls respond, since these shape the feel.
- Define the interface language. Set guidance for tone in labels, errors, and confirmations.
- Check fit against experience goals. Confirm that the visual and behavioral decisions support the product’s goals and brand keywords.
Documenting look and feel in a brief or style guide
A style guide can be a starting point, but it does not translate automatically into an interactive product. The interaction-design book About Face 3: The Essentials of Interaction Design (third edition excerpt) notes that turning marketing collateral guidance into an interactive product’s look and feel can require substantial work. Its discussion links visual-language studies with experience goals and brand keywords, which is why a brief should cover behavior and language as well as color and type.
One current example of recording the idea in structured form is Google Labs’ design.md specification. It includes a Brand & Style section that describes a product’s look and feel holistically and places color palettes among its structured design guidance. This is an example of one documentation format, not a universal requirement, so teams can use whatever structure fits their tools.
Quick Recap
Limits of the term
- There is no single industry definition. Dictionary usage and Microsoft’s 2009 article describe the phrase in similar but not identical ways, so define it in each project document.
- Attractive design is not automatically effective design. The sources discussed here do not establish a measured causal effect of visual appeal on usability or business results. Treat claims of that kind with caution unless they come from a study you can check.
- Sources are definitional and practical. They explain how the term is used and how teams can describe it. They do not supply benchmarks or measurements.
Sources
- Cambridge Dictionary, entry for “look and feel,” computing usage.
- Microsoft Learn and MSDN Magazine, “Usability in Practice: More Than Skin Deep,” December 2009.
- About Face 3: The Essentials of Interaction Design, third edition excerpt.
- Google Labs, design.md specification.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
