External Standards are about making digital products feel natural to use. In UX, this principle focuses on external consistency – keeping design aligned with what people already know. Over time, individuals develop expectations about how a user interface should behave based on familiar patterns from other systems. The external standards in UX principle builds on these expectations by following well-established design conventions found across modern user interfaces, creating predictable interactions that enhance overall user experience.
Instead of chasing novelty, this part of design values familiarity. Every platform – web, iOS, Android – has its own design language and UI standards. Respecting them helps people instantly recognize how things work, keeping interactions consistent and intuitive across products.
Core aspects of External Standards are:
6.1 Use of Common Interface Patterns
6.2 Use of Familiar Names and Descriptions
6.3 Platform Standards Compliance
6.4 Avoiding Unusual or Unexpected Elements
6.1 Use of Common Interface Patterns
Common interface patterns are the shortcuts our brains rely on. They tell users what’s clickable, where to look next, and how to move forward – without a single line of explanation. Navigation bars on top, filters on the left, a magnifying glass for search – these patterns work because people have already learned them elsewhere.
When designers break these expectations, even small changes can interrupt the flow. Users stop to think: “Where did the menu go?” or “Is this even a button?” That brief pause is enough to break concentration and slow the experience.
Tips for Using Common Interface Patterns
- Observe what users already recognize before designing something “new.”
- Keep navigation, search, and shopping flows aligned with what’s standard in your domain – e-commerce, fintech, healthcare, etc.
- Keep the standard look of buttons, links, and checkboxes so they remain recognizable as components.
- Test with people outside your design team; if they hesitate, something isn’t intuitive enough.
- Remember that familiarity isn’t boring – it’s what makes a digital UX feel trustworthy.
- Test with people outside your design team; if they hesitate, something isn’t intuitive enough.
- Remember that familiarity isn’t boring – it’s what makes a digital UX feel trustworthy.
Project: Zara, eCommerce website
Platform: Desktop
❌ Zara’s desktop site used an unusual navigation pattern – the menu occupied only a small vertical section of the screen, forcing users to scroll to access all categories. This unfamiliar setup disrupted scanning and made browsing slower.
Project: Etsy, Walmart, Wayfair, eCommerce websites
Platform: Desktop
✅ These e-commerce platforms follow the same interface logic: a visible search bar, accessible account section, and cart icon at the top. Such predictability allows users to act without hesitation or confusion.
Project: AllRecipes.com
Platform: Desktop
❌ The recipe website hides its main navigation behind a menu icon. However, instead of sliding out from the left as users would typically expect, the menu appears in a modal window. On desktop, modals are usually associated with newsletter sign-ups or promotional offers – so users might instinctively close it, not realizing that this modal actually contains the site’s navigation and is essential for exploring content.
Project: MyFitnessPal
Platform: Mobile app
❌The search bar sat at the bottom of the screen – great for the thumb, but not for the mind. Users simply didn’t expect to find it there and got momentarily lost.
Project: Ticketmaster, event ticketing website
Platform: Desktop
❌The “Find Tickets” button used an arrow icon – something people usually associate with opening a new tab. But instead, it loaded the next page in the same window. That tiny mismatch left users second-guessing whether the button worked correctly.
Project: Habitica, habit-building app
Platform: Mobile
❌ On the first screen, the app’s buttons had such unusual shapes and styling that users weren’t sure they could tap them. What should have been a simple first step – getting started – turned into a small moment of hesitation.
Project: Epicentr, eCommerce website
Platform: Desktop
❌ On Epicentr’s website, the filter panel sits on the right side of the page, even though users usually expect to find filters on the left. The layout feels slightly off and forces people to adjust their scanning pattern before they can start shopping.
6.2 Use of Familiar Names and Descriptions
Language is a part of the user interface – not decoration on top of it. Every label, button, or message is a tiny instruction. When that instruction sounds natural, users act without thinking. When it sounds strange, they hesitate – and hesitation breaks flow.
Familiar words make design feel invisible. They help people predict what will happen before they even tap or click. That’s what makes “Add to cart”, “Edit profile”, or “Continue” feel effortless – users have already seen these phrases a hundred times before. They don’t process them consciously; they just move forward.
The biggest mistakes usually come from overthinking. Teams try to sound more “unique,” playful, or branded – and end up confusing users instead. Clever language might work in marketing but in product design it slows people down. Good microcopy doesn’t shout for attention; it helps users finish what they came to do.
Tips for Using Familiar Names and Descriptions
- Mirror how users actually talk. If your customers say “Cart,” don’t rename it “Bag” just to stand out. Familiarity is faster than creativity.
- Stay consistent. Pick one version – “Sign in” or “Log in” – and use it everywhere. Small wording changes feel bigger than you think.
- Use action-first language. Short, direct verbs like “Save”, “Send”, or “Edit” keep users oriented and confident.
- Avoid jokes, puns, or cultural slang. They age fast and often don’t translate.
- Test wording in real tasks. Watch where people hesitate or reread. If that happens – the copy failed.
Project: KFC Polska, food delivery app
Platform: Mobile (Android)
❌ The KFC Polska app used the tab label “cou(r)pons” – a wordplay mixing “coupons” and the Polish word for chicken, kurczak. While creative, it left many users puzzled. Instead of feeling playful, the navigation looked confusing and inconsistent with standard app language.
6.3. Platform standards compliance
Every platform operates on its own internal logic. It defines interaction patterns, gesture behavior, and layout conventions that users subconsciously rely on. When a design ignores these platform norms, it creates a subtle sense of friction – the user experience feels unfamiliar, even if the visuals are refined.
Adhering to platform standards is less about imitation and more about aligning with established mental models – external standards in UX. Users don’t consciously think about where the back button sits or how alerts should look; they simply expect consistency. Meeting those expectations maintains cognitive flow and builds immediate trust.
The real challenge lies in details. Minor inconsistencies – a navigation gesture that behaves differently between screens, or a custom component that doesn’t respond like a native UI element – can quietly undermine confidence. These small breaks in logic make people notice the interface instead of the task.
Tips for Platform Standards Compliance
- Start with user habits, not visual trends. People carry muscle memory from their devices. Respect that before adding new gestures or layouts.
- Use native patterns whenever possible. Alerts, pickers, and toggles come with built-in logic users already trust. Replacing them adds work without real gain.
- Balance visual identity with native feel. You can follow platform logic while keeping your brand’s look – it’s about interaction, not colors or fonts.
- Avoid blending ecosystems. Copying Android gestures to iOS, or iOS animations to Android, instantly breaks the sense of familiarity.
- Test in the real environment. Use actual devices, not just Figma or emulators. The difference between “it looks right” and “it feels right” only shows up in motion.
Project: Wise, financial app
Platform: Mobile app (iOS)
✅ Wise uses standard iOS, UI elements like alerts, date pickers, and toggle buttons. This approach makes navigation effortless – users instantly recognize how things work because it all feels native to their device.
Project: Revolut, financial app
Platform: Mobile app (Android and iOS)
✅Revolut adapts its interface to each platform’s visual and interaction standards. On Android, it follows Material Design; on iOS, it mirrors Apple’s patterns. This alignment reflects external standards in UX done well.
Project: Medis, healthcare app
Platform: Mobile app (iOS)
✅ Medis uses the built-in iOS “Add to Wallet” button to connect insurance cards. The familiar element instantly tells users what will happen when they tap it – no extra learning needed.
6.4. Avoiding Unusual or Unexpected Elements
Interfaces fail when they surprise users for no reason. A small change a button behaving differently, a familiar icon doing something new can quietly damage trust. Users might not complain; they just move slower or stop using the feature altogether.
Novelty in UX isn’t bad, but it needs purpose. Changing a standard pattern only works when it makes the action faster, clearer, or safer. Anything else feels like noise. Unusual elements often come from the designer’s curiosity, not the user’s need – and that’s where friction starts.
Tips for Avoiding Unusual or Unexpected Elements
- Test intention, not originality. Ask: “Does this interaction solve a problem, or is it just different?” If it’s the second – keep the old one.
Use visual language users already trust. Reinventing icons or gestures breaks rhythm. Even one odd detail can make the product feel unreliable. - Pay attention to context. What works in a mobile game won’t work in a banking app. The same motion can feel playful or risky depending on purpose.
- Be careful with feedback loops. Overreactive animations, false errors, or confusing confirmations make users feel punished for normal actions.
- Fix friction first, innovate second. Clarity should always come before personality.
Project: Bilkom.pl, ticketing app
Platform: Mobile app (iOS)
❌ During sign-up, Bilkom.pl asks users to confirm terms and conditions using controls that look like radio buttons but behave like toggles. The visual mismatch confuses users – they think they’re choosing one option when they’re actually switching between states.
Project: EventyApp, event management app
Platform: Mobile app (iOS)
Source: Smashing Magazine
❌ The app uses a heart icon – typically associated with adding to favorites – to set event reminders instead. The behavior feels unexpected and breaks user trust, since the icon doesn’t do what people intuitively think it should.
Project: Tivoli, corporate website
Platform: Desktop
Source: NN/g
❌ In Tivoli’s sidebar menu, both section titles and arrow icons open different links. Users can’t tell which one leads to the right page, so they end up clicking at random. Predictability disappears, and with it – confidence.
Project: Texas × Texas, government website
Platform: Desktop
❌ On the Texas vehicle registration page, an error appears the moment an empty field loses focus – even before submission. The system blames users for doing nothing wrong, creating frustration and uncertainty about what just happened.
Familiar patterns work best when they’re applied consistently. It keeps the experience steady and easier to follow. Continue with the next CI Usability Principle – Internal Consistency.
