Unit 1: Introduction [4 Hours]

User Experience (UX) and User Interface (UI) design are two closely related disciplines that together determine how people interact with and feel about digital products. UX is concerned with the overall quality of a person's interaction with a system, while UI is the visual and interactive layer through which that interaction happens. This unit covers the foundational concepts, roles, principles, and tools of both disciplines so you can understand how design decisions shape the usability and success of any digital product.

Tested Topics

1. Accessibility — 4x (2026 × 2, Model Q × 2)
2. Information Architecture — 4x (2026 × 2, Model Q × 2)
3. Accessible interface practices — 2x (2026, Model Q)
4. Card sorting, content organization, labeling, navigation and sitemaps — 2x (2026, Model Q)
5. Consistency, simplicity and feedback — 2x (2026, Model Q)
6. Impact of poor UI/UX on usability and product success — 2x (2026, Model Q)
7. UI vs UX — 2x (2026, Model Q)
8. Usability principles — 2x (2026, Model Q)
9. Usability vs user experience (UX) — 2x (2026, Model Q)

1.1 Fundamentals of UX and UI

Definition

User Experience (UX) is the overall feeling, perception, and satisfaction a person has when interacting with a product, system, or service from start to finish. User Interface (UI) is the visual and interactive layer of a product — the screens, buttons, forms, icons, and controls a person directly sees and touches.

UX is the full journey: how easy the product is to learn, how efficient it is to use, whether it frustrates or delights the user. UI is what the user physically looks at and clicks. A restaurant analogy works well here: the UI is the menu design, the table layout, the plating — everything you see. The UX is the whole dining experience: how long you waited, whether the waiter understood you, how satisfied you felt leaving.

Detailed Explanation

UX design focuses on understanding what users want to accomplish, removing friction from their path, and making the interaction feel natural and satisfying. It is rooted in psychology, human factors, and research methods.

UI design focuses on translating UX decisions into visual form: selecting colors, typography, spacing, layout, and interactive states so the interface communicates clearly and works beautifully.

The two disciplines overlap but address different questions:

Both must work together. A beautifully designed UI on a poorly structured UX creates a product that looks good but frustrates users. A well-researched UX with a poorly executed UI creates a product that is logically sound but unusable in practice.

1.2 UX vs UI

Definition

UX (User Experience) is concerned with whether a product is useful, usable, and enjoyable across the entire interaction lifecycle. UI (User Interface) is concerned with how the interactive elements of a product are visually presented and how they respond to user input.

UX is the feeling of moving through a product efficiently with no confusion. UI is what you see and touch to make that movement happen. A well-designed door handle is good UI; the fact that the door opens into the right room without requiring a map to find it is good UX.

Detailed Explanation

The confusion between UX and UI persists because they are genuinely intertwined. Every UI decision has a UX consequence. Choosing a small font (UI) makes text hard to read (UX). Placing a checkout button off-screen (UI) causes users to abandon their cart (UX). Understanding the distinction clearly is essential for any designer.

Core Differences

A Concrete Example

Consider a mobile banking app's money transfer feature.

• UX decisions: In how many steps should the transfer complete? Where does a user confirm the recipient before sending? What happens if the account number is wrong? What confirmation message reassures the user the transfer succeeded?
• UI decisions: What color is the "Send Money" button? How large is the input field? What font is used for the account balance? What animation plays on transfer success?

Good UX without good UI: the transfer flow is logical and error-free but the text is too small, the color contrast is poor, and the button states are unclear. Users can technically complete the task but feel uncertain throughout.

Good UI without good UX: the app looks polished but the transfer flow requires seven steps, buries the confirmation screen, and gives no clear error message when the account number fails. Users abandon the task despite the attractive design.

1.3 Tasks of UX Designer and UI Designer

Definition

A UX designer is responsible for understanding user needs, defining how a product should work, and validating those decisions through research and testing. A UI designer is responsible for crafting the visual and interactive details of a product so that it communicates clearly and is pleasant to use.

The UX designer builds the map: what screens exist, how they connect, and what the user can do. The UI designer decorates and populates that map with typography, color, spacing, icons, and component states that make it readable, accessible, and visually coherent.

Detailed Explanation

Tasks of a UX Designer

• User research: conduct interviews, surveys, and usability tests to understand who the users are, what they want, and where they struggle.
• Persona creation: build representative user profiles that keep design decisions anchored to real human needs rather than assumptions.
• Information architecture (IA): decide how content and features are organized, categorized, and labeled so users can find what they need.
• User flow mapping: diagram the sequence of screens and decisions a user moves through to complete a task.
• Wireframing: produce low-fidelity structural sketches of each screen showing content placement, navigation, and interactions without visual styling.
• Prototyping: create interactive mockups that simulate the product so it can be tested before development begins.
• Usability testing: observe real users attempting tasks with the prototype to identify friction points, confusion, and failure modes.
• Iteration: refine flows and structures based on test findings and stakeholder feedback.

Tasks of a UI Designer

• Visual design: define the look of the product, including color palettes, typography scales, iconography, and spacing systems.
• Component design: design reusable UI elements, including buttons, forms, cards, navigation bars, modals, and dropdowns, in all their states (default, hover, active, disabled, error).
• Responsive layout design: ensure the interface adapts correctly to different screen sizes from mobile to desktop.
• Design system creation: document the visual rules and reusable components in a style guide or design system so developers and other designers work consistently.
• Interaction design: specify animations, transitions, and micro-interactions that provide feedback and make the interface feel responsive and alive.
• Developer handoff: provide annotated, production-ready designs with measurements, assets, and behavior notes so engineers can implement the design accurately.
• Accessibility compliance: ensure contrast ratios meet standards, font sizes are readable, and interactive elements are keyboard-navigable.

1.4 UX Principles: Usability, Accessibility, Simplicity

Definition

Usability is the degree to which a product allows specified users to achieve specified goals with effectiveness, efficiency, and satisfaction. Accessibility is the design practice of making products usable by people with the widest possible range of abilities and disabilities. Simplicity is the principle of eliminating unnecessary complexity so users can focus entirely on their goals.

Usability asks "can this particular user do this particular task?". Accessibility asks "can users with disabilities, impairments, or different devices do it too?". Simplicity asks "is everything in this design pulling its weight, or is some of it just getting in the way?"

Detailed Explanation

Usability

Usability is typically measured across five dimensions, first formalized by Jakob Nielsen:

• Learnability: how quickly can a new user accomplish basic tasks on first encounter? A learnable interface requires little instruction to get started.
• Efficiency: once familiar, how fast can an experienced user complete tasks? A highly efficient interface minimizes steps, clicks, and keystrokes.
• Memorability: when a user returns after a period of absence, how quickly can they re-establish proficiency? Good memorability means users are not back at zero after time away.
• Errors: how many errors do users make, how severe are those errors, and how easily can they recover? A usable interface prevents errors and makes recovery obvious.
• Satisfaction: how pleasant is the experience? Does the user feel confident and in control, or frustrated and confused?

Accessibility

Accessibility expands usability to users with permanent, temporary, or situational disabilities. The Web Content Accessibility Guidelines (WCAG) provide the international standard for accessible digital products, organized around four principles commonly abbreviated as POUR:

• Perceivable: information must be presentable to users in ways they can perceive, including through vision, hearing, or touch. Example: providing text alternatives for images.
• Operable: interface components must be operable by keyboard, not only by mouse. Example: all interactive elements reachable by pressing Tab.
• Understandable: information and operation of the UI must be understandable. Example: clear error messages that explain what went wrong and how to fix it.
• Robust: content must be interpreted reliably by current and future assistive technologies. Example: using proper semantic HTML elements so screen readers function correctly.

Practical accessibility practices include:

• Maintaining a minimum color contrast ratio of 4.5:1 for normal text and 3:1 for large text (WCAG AA standard).
• Providing alternative text (alt text) for every meaningful image so screen readers can describe images to visually impaired users.
• Ensuring all interactive elements (links, buttons, forms) are keyboard-accessible and show a visible focus indicator.
• Using descriptive, meaningful labels for form fields rather than placeholder text alone (placeholder text disappears on input, leaving users who forget what the field was for).
• Avoiding conveying information by color alone (a red error border means nothing to a colorblind user unless it is accompanied by a text message or icon).

Simplicity

Simplicity does not mean minimal features. It means that every element present has a clear reason for being there. The cognitive load imposed on a user should be the minimum required to accomplish their goal.

Hick's Law provides a useful framework: the time it takes a user to make a decision increases as the number of choices increases. More options create more mental work. A product that offers twelve navigation items creates more cognitive load than one that offers five well-organized categories.

Achieving simplicity in practice involves:

• Progressive disclosure: show only the information and controls needed for the current task. Advanced options are available but not constantly visible.
• Reducing visual noise: whitespace is not wasted space. It gives elements room to breathe and allows users to parse the interface without strain.
• Clear hierarchy: the most important action on any screen should be the most visually prominent. Secondary actions should recede.
• Consistent patterns: when similar things look and behave the same way, users learn the interface once and apply that knowledge everywhere.

1.5 Core Disciplines of UX: User Research, Content Strategy, Information Architecture, Interaction Design, Visual Design, Usability Evaluation

Definition

The core disciplines of UX are the six interconnected fields that together constitute professional User Experience (UX) design. Each discipline addresses a specific dimension of the user's relationship with a product, from understanding user needs through research to evaluating whether the final product actually works.

UX design is not one skill; it is a combination of six specialized areas that feed into each other. Understanding all six gives you the full map of what professional UX design actually involves.

Detailed Explanation

1. User Research

User research is the practice of systematically studying the behavior, needs, motivations, and mental models of the target users before and during design.

Without research, design is guesswork. User research replaces assumptions with evidence.

Key research methods:

• Interviews: one-on-one conversations with target users to understand their goals, pain points, and current behaviors in depth.
• Surveys: structured questionnaires sent to larger groups to gather quantitative data about user preferences and behaviors at scale.
• Contextual inquiry: observing users in their real environment while they use the product or perform related tasks, revealing behaviors users would not self-report.
• Usability testing: structured sessions where users attempt specific tasks with a prototype or live product while a researcher observes and records errors and confusion.
• Card sorting: a technique where users group and label content items to reveal their mental model for how information should be organized (closely tied to Information Architecture).

Research outputs typically include personas (fictional but evidence-based user profiles) and user journey maps (diagrams tracing the user's experience from first awareness through task completion, including emotions, touchpoints, and pain points).

2. Content Strategy

Content strategy is the discipline of planning, creating, organizing, and governing the words, images, and media within a product so they serve user needs and business goals simultaneously.

Content is not an afterthought to fill in after the interface is designed. It is a core design material. A button labeled "Submit" is less clear than "Place Order." A form heading that says "Personal Information" communicates less than "Tell us where to send your order."

Content strategy in UX involves:

• Defining the voice and tone of the product: formal or conversational, technical or plain, serious or playful.
• Writing clear, scannable interface copy (labels, error messages, empty states, onboarding text) that guides users without overwhelming them.
• Ensuring content is logically structured so users can find what they need quickly.
• Planning how content will be created, maintained, and updated over time so the product does not degrade into outdated or inconsistent information.

3. Information Architecture (IA)

Information Architecture (IA) is the structural design of content within a product: how information is organized, categorized, labeled, and connected so users can find what they need without confusion.

IA is the skeleton of the product. Before any visual design begins, IA determines what the navigation structure looks like, how many levels of hierarchy exist, and which content belongs in which section.

Core components of IA:

• Organization systems: how content is grouped. Categories can be hierarchical (main category with subcategories), sequential (step-by-step processes), or matrix (users choose their own path).
• Labeling systems: the words used to represent categories and links. Labels must match users' vocabulary, not the internal terminology of the organization. A label called "Resources" means different things to different users; "Student Guides" is unambiguous.
• Navigation systems: how users move through the structure. Navigation patterns include global navigation (consistent across all pages), local navigation (specific to a section), breadcrumbs (showing current location within the hierarchy), and contextual links.
• Search systems: how users find content directly when they know what they want. An effective search system handles typos, synonyms, and filters.
• Sitemaps: visual representations of the full content structure, showing all pages or sections and how they connect. Sitemaps are planning tools for designers and structural guides for developers.

Card Sorting in IA

Card sorting is a method used to build or validate IA. Participants are given cards, each labeled with one piece of content, and asked to group them in a way that feels natural to them. Two types exist:

• Open card sort: participants group cards and name the groups themselves, revealing how users naturally categorize content.
• Closed card sort: participants sort cards into predefined categories, testing whether existing category labels make sense to users.

The results directly inform how the navigation structure and labeling system should be designed.

4. Interaction Design

Interaction Design (IxD) is the discipline of defining how a product behaves in response to user input: what happens when a user taps a button, submits a form, drags an element, or makes an error.

Where UI design defines what an element looks like, interaction design defines what it does. The difference between a button that provides instant visual feedback and one that takes a moment to respond before anything changes is an interaction design decision that directly affects the user's sense of control and confidence.

Key concerns of interaction design:

• Feedback: the system must acknowledge every user action. A loading spinner confirms a request was received. A success message confirms a task completed. Silence after an action creates uncertainty.
• Affordances: visual or physical cues that indicate how an element can be used. A raised button looks pressable. An underlined word looks clickable. Affordances should be consistent with user expectations.
• Constraints: limiting available actions to prevent errors. A date picker that disables past dates prevents an impossible selection. A form that disables the submit button until all required fields are filled prevents incomplete submissions.
• Error prevention and recovery: design the system to prevent errors in the first place; when errors still occur, make them easy to identify and correct.

5. Visual Design

Visual design in UX is the discipline of using visual elements — color, typography, layout, imagery, spacing, and contrast — to communicate information clearly, establish brand identity, and guide user attention toward the most important elements of an interface.

Visual design operates through established principles:

• Visual hierarchy: arranging elements so the most important information is perceived first. Size, contrast, color weight, and placement all contribute to hierarchy.
• Contrast: difference in visual properties (color, size, weight) that makes elements stand out from each other or from the background. Contrast is how users spot headings, calls-to-action, and warnings.
• Alignment: elements aligned on a consistent grid create visual order and reduce cognitive effort required to parse the layout.
• Proximity: elements placed near each other are perceived as related. Grouping form fields by their logical relationship (personal details together, payment details together) aids comprehension.
• Repetition/Consistency: repeating visual patterns (same button style, same icon size, same spacing unit) builds a recognizable system users learn once and apply everywhere.

6. Usability Evaluation

Usability evaluation is the process of assessing whether a product meets usability standards and actually works for real users, using both expert review and testing with participants.

Design and evaluation form a loop: design → test → identify problems → redesign → test again. Skipping evaluation means problems are discovered only after launch, when they are far more expensive to fix.

Main evaluation methods:

• Heuristic evaluation: a usability expert reviews the interface against a set of established usability principles (heuristics), typically the ten principles defined by Jakob Nielsen. No user recruitment is required, making it fast and low-cost.
• Cognitive walkthrough: evaluators simulate a new user's thought process as they attempt specific tasks, step by step, identifying where users might fail to understand what to do next.
• Usability testing with users: real members of the target audience attempt predefined tasks with the interface while a researcher observes, measures time on task, records errors, and notes verbal confusion.
• A/B testing: two versions of a design are shown to different user groups simultaneously and performance data (click-through rate, conversion rate, error rate) determines which version works better.

1.6 User Interfaces: CLI, GUI, VUI, Menu-driven, NLP based

Definition

A User Interface (UI) is the means by which a user interacts with a computer system. The type of interface defines the input method (how the user gives commands) and the output method (how the system responds). Different interface types emerged historically as computing power and human factors research evolved.

The same underlying task, such as searching for a file, works completely differently depending on the interface type. A power user might type a terminal command. A typical user might click through a graphical file explorer. A voice assistant user might say "find my presentation from last Tuesday." Each is a different interface type for the same system function.

Detailed Explanation

1. Command Line Interface (CLI)

A Command Line Interface (CLI) is a text-based interface where users type commands directly and the system returns text-based output. No visual elements, graphics, or mouse interaction are involved.

2. Graphical User Interface (GUI)

A Graphical User Interface (GUI) is a visual interface where users interact with graphical elements: windows, icons, menus, buttons, and checkboxes, typically controlled by a mouse or touchscreen.

3. Voice User Interface (VUI)

A Voice User Interface (VUI) is an interface where users interact with a system using spoken natural language. The system uses speech recognition to convert voice input into commands and typically responds with synthesized speech.

4. Menu-Driven Interface

A menu-driven interface is an interface where users navigate by selecting from a predefined list of options presented at each step. No commands need to be memorized; the available choices are always displayed.

5. Natural Language Processing (NLP) Based Interface

A Natural Language Processing (NLP) based interface allows users to interact with a system using natural human language, either typed or spoken, and the system understands the intent behind the phrasing rather than matching exact commands.

Where a VUI primarily converts speech to commands, an NLP interface interprets the meaning and context of language to determine user intent, handle ambiguity, and respond intelligently even when phrasing varies.

Comparison Summary

1.7 Properties of Good UX/UI Design

Definition

The properties of good UX/UI design are the measurable and observable characteristics that distinguish an effective, satisfying design from one that frustrates, confuses, or excludes users.

Good design rarely announces itself. Users notice poor design immediately because it stops them. Good design removes itself from the user's awareness so the user can focus entirely on their goal. The properties below describe what makes that invisibility possible.

Detailed Explanation

1. Clarity

Every element should communicate its purpose without explanation. Labels must use plain language. Instructions should be as short as possible while still being complete. Icons should be universally recognized or accompanied by text labels.

A form field labeled "Date" is unclear. Is it a date of birth, enrollment date, or event date? "Date of birth (DD/MM/YYYY)" is clear.

2. Consistency

Similar elements should look and behave the same way throughout the product. If a primary button is blue and rounded on the login screen, it should be blue and rounded everywhere. If clicking the logo always returns to the homepage, that pattern must never break.

Consistency reduces the cognitive load of learning the interface. Once a user understands how one button works, they understand how all buttons work. Breaking consistency forces users to relearn behavior and creates distrust.

Two levels of consistency matter:

• Internal consistency: elements are consistent within the product itself.
• External consistency: the product follows platform conventions users already know (back button in mobile apps, hamburger menu for navigation, magnifying glass for search).

3. Feedback

The system must communicate the result of every user action immediately and unambiguously. Without feedback, users do not know whether their action was registered, whether it succeeded, or whether something went wrong.

Types of feedback in UI design:

• Visual feedback: button changes state on click (hover → active → loading).
• Status feedback: a progress bar or loading spinner shows the system is working.
• Confirmation feedback: a success message confirms a form was submitted, a file was saved, or a payment was processed.
• Error feedback: a clearly worded error message explains what went wrong and, where possible, how to fix it.

4. Efficiency

Good design minimizes the time and steps required to complete any task. Every unnecessary screen, click, or form field is friction. Friction causes users to abandon tasks.

Efficiency is improved by: pre-filling fields with known data, allowing keyboard shortcuts for frequent actions, remembering user preferences, and placing primary actions in predictable prominent locations.

5. Error Prevention

Good design prevents errors before they happen rather than only handling them after. A calendar that disables past dates for a future booking prevents an impossible selection. A form that shows password requirements before submission prevents a failed attempt.

When errors do occur, the system should:

• Identify the error precisely (not "invalid input" but "phone number must be 10 digits, numbers only").
• Preserve any valid data the user already entered so they do not have to start over.
• Provide a clear path to recovery.

6. Hierarchy and Focus

Every screen should have one primary action that is the most visually prominent element. Secondary actions should visually recede. Users who see a cluttered screen with five equally prominent buttons have to spend mental energy deciding where to look first.

7. Flexibility and Efficiency of Use (for Different Users)

Good design serves both novice and expert users. Novice users need clear guidance and simple paths. Expert users need shortcuts, keyboard controls, and the ability to bypass steps they have already mastered. Designs that only serve one type of user fail the other.

1.8 UX/UI Tools: Figma, Adobe XD, Sketch

Definition

UX/UI design tools are software applications that enable designers to create wireframes, prototypes, high-fidelity mockups, and collaborative design systems without writing code. The three most widely used professional tools are Figma, Adobe XD, and Sketch.

Before these tools existed, designers worked in general-purpose graphic design software not built for interactive products, then handed files to developers who had to guess at spacing, behavior, and states. Modern UX/UI tools provide design-specific features: component systems, auto-layout for responsive design, interactive prototyping, and direct developer handoff capabilities.

Detailed Explanation

Figma

Figma is a browser-based collaborative design tool that has become the dominant industry standard. It runs entirely in the web browser, with no installation required, making it platform-independent (works on Windows, macOS, Linux).

Key features:

• Real-time collaboration: multiple designers and stakeholders can work on the same file simultaneously, similar to Google Docs. This eliminates version-control problems common with file-based tools.
• Components and variants: reusable design elements with multiple states (e.g., a button component with default, hover, active, and disabled variants) that update everywhere when edited in one place.
• Auto Layout: frames that automatically adjust their size when content changes, enabling responsive design behavior within the design tool itself.
• Prototyping: connect frames with interactive triggers and transitions to create clickable prototypes that simulate real navigation without code.
• Dev Mode: a developer-facing view that shows exact measurements, CSS properties, and exportable assets so engineers can implement designs accurately.
• Community and plugins: an extensive library of community-shared components, icon sets, templates, and plugins for tasks like accessibility checking, content population, and design handoff.

Adobe XD

Adobe XD (Experience Design) is Adobe's dedicated UX/UI design and prototyping tool, integrated with the Adobe Creative Cloud suite. It is a desktop application available for Windows and macOS.

Key features:

• Adobe ecosystem integration: seamlessly imports assets from Photoshop, Illustrator, and After Effects, making it a natural choice for teams already working in Adobe software.
• Repeat Grid: a productivity feature that duplicates UI elements (like product cards or list items) in a grid automatically, with content that can be populated by dragging in text or image files.
• Voice prototyping: allows designers to add voice commands and speech playback to prototypes, useful for designing VUI interactions.
• Co-editing: real-time collaboration added after Figma popularized it, though Figma's implementation is generally regarded as more robust.
• Share for review: generates a shareable link for stakeholders to leave comments on a prototype without needing an Adobe account.

Note: Adobe announced in 2023 that it would sunset Adobe XD. While the product still works, the industry has largely migrated to Figma, which Adobe acquired. New projects are generally started in Figma.

Sketch

Sketch is a macOS-only design application that was the dominant tool before Figma's rise. It established many of the design workflows now standard across all tools, including symbols (reusable components) and artboard-based layouts.

Key features:

• Symbols: Sketch pioneered the concept of reusable design components across the industry. A symbol is a master element that updates every instance when modified.
• Plugins and integrations: a large plugin ecosystem extends Sketch with version control (Abstract), handoff (Zeplin), and other tools.
• Offline-first: Sketch files are local, which appeals to teams with strict data privacy requirements. Cloud sync is available but optional.
• macOS only: this is a significant limitation. Sketch does not run on Windows or Linux, which limits team collaboration across mixed-OS environments.

Comparison

Exam Questions

1. Differentiate between usability and user experience (UX) in one sentence. (Model Q / 2026)
2. How does Information Architecture help users find information efficiently? (Model Q / 2026)
3. Differentiate between UI and UX. Explain with suitable examples how poor UI or poor UX can affect the usability and success of a digital product. (Model Q / 2026)
4. Explain the major principles of effective UI/UX design, including usability, accessibility, consistency, simplicity, and feedback. Discuss how ignoring these principles can create problems for users. (Model Q / 2026)
5. Explain the role of Information Architecture in UI/UX design. Discuss how card sorting, content organization, labeling, navigation, and sitemaps contribute to creating an understandable interface. (Model Q / 2026)
6. Explain the importance of accessibility in UI/UX design. Discuss how readable text, sufficient contrast, keyboard accessibility, clear labels, and alternative text can make a digital product usable by people with different abilities. (Model Q / 2026)

Whole Chapter Summary

• Fundamentals of UX and UI: UX covers the full user journey including efficiency, satisfaction, and goal achievement. UI is the visual and interactive layer the user sees and touches. Both are necessary; neither alone is sufficient.
• UX vs UI: UX asks "does it work for the user?"; UI asks "does it look and feel right?" Poor UX produces frustrated users who abandon tasks; poor UI produces confusion even when the underlying flow is sound.
• Tasks of UX and UI Designers: UX designers conduct research, build personas, map flows, wireframe, prototype, and test. UI designers define visual systems, design components, ensure accessibility compliance, and hand off to developers.
• Usability, Accessibility, Simplicity: Usability measures effectiveness, efficiency, and satisfaction across five dimensions. Accessibility ensures products work for users with disabilities following the WCAG POUR framework. Simplicity minimizes cognitive load through progressive disclosure, hierarchy, and consistent patterns.
• Core Disciplines of UX: Six disciplines form a loop: User Research feeds IA and Content Strategy; Interaction Design and Visual Design translate those into a product; Usability Evaluation feeds findings back into the next design iteration.
• User Interface Types: CLI (typed commands, expert users), GUI (graphical elements, general public), VUI (voice, hands-free and accessible), Menu-driven (pre-listed options, kiosk and guided workflows), NLP-based (natural language, AI assistants).
• Properties of Good UX/UI Design: Clarity, consistency, feedback, efficiency, error prevention, visual hierarchy, and flexibility for different user types are the measurable characteristics of a well-designed product.
• UX/UI Tools: Figma is the current industry standard (browser-based, real-time collaboration). Adobe XD (being sunset) and Sketch (macOS-only) are alternatives with narrowing adoption.

Last-Minute Revision Sheet

• UX → whole journey, satisfaction, task success | UI → visual layer, what user sees and clicks
• UX vs UI → UX: does it work? | UI: does it look right?
• Poor UI → confusing interface despite good flow | Poor UX → frustrating journey despite attractive UI
• Usability dimensions → Learnability, Efficiency, Memorability, Errors, Satisfaction (LEMES)
• Accessibility → WCAG POUR: Perceivable, Operable, Understandable, Robust
• Accessibility practices → contrast 4.5:1, alt text, keyboard nav, descriptive labels
• Simplicity → Hick's Law: more choices = slower decisions | use progressive disclosure
• IA components → Organization, Labeling, Navigation, Search, Sitemaps
• Card sorting → Open: users name groups | Closed: users sort into given groups
• 6 UX disciplines → Research, Content Strategy, IA, Interaction Design, Visual Design, Usability Evaluation
• Interface types → CLI (command text) | GUI (graphical) | VUI (voice) | Menu-driven (selection) | NLP (natural language)
• Good design properties → Clarity, Consistency, Feedback, Efficiency, Error prevention, Hierarchy, Flexibility
• Tools → Figma (industry standard, browser-based) | Adobe XD (being sunset) | Sketch (macOS only)
• Feedback types → Visual (button state) | Status (loading spinner) | Confirmation (success message) | Error (clear error text)