User experience Study Guide

📖 Core Concepts User Experience (UX) – The total perception a person has of a product, system, or service, including utility, ease of use, efficiency, emotions, beliefs, and outcomes before, during, and after use. Usability – The pragmatic, task‑focused part of UX (can you get the job done?). Hedonic vs. Pragmatic – Hedonic aspects are feelings of pleasure, value, and delight; pragmatic aspects are functional performance. Dark Patterns – Design tactics that deliberately mislead or coerce users into actions they wouldn’t otherwise take (e.g., opt‑out checkboxes, hidden cancel links). Inclusive/Accessible Design – Practices that ensure products work for people with disabilities, older adults, and diverse cultural/linguistic backgrounds. Developer Experience (DX) – The UX of the tools, documentation, and processes a developer interacts with while building software. --- 📌 Must Remember UX = Usability + Feelings – Good UX requires both task success and positive emotional response. Three UX factors (ISO) – System, User, Context of use. Temporal Levels – Momentary (single interaction), Episodic (session), Long‑term (brand reputation, habits). Dark‑Pattern Red Flags – Opt‑out defaults, hidden fees, “confirm” buttons that actually purchase, confusing cancellation. Accessibility Standards – Follow WCAG (Web Content Accessibility Guidelines) and run accessibility audits. DX Success Drivers – Clear docs, smooth onboarding, consistent APIs, continuous developer feedback. --- 🔄 Key Processes Evaluating UX Define research goals (e.g., satisfaction, task time). Choose method(s): questionnaires, focus groups, usability testing, journey mapping. Recruit representative users (include diverse abilities). Collect data → analyze for pragmatic vs. hedonic outcomes. Report findings with actionable recommendations. Identifying Dark Patterns Review UI elements for default bias (opt‑out vs. opt‑in). Trace the click path to see if intended action is hidden or requires extra steps. Check wording for ambiguity or misleading language. Classify pattern (e.g., “Sneak into basket”, “Hidden cost”). Improving Developer Experience Audit documentation for completeness & clarity. Streamline setup (one‑click install, containerized dev env). Provide runnable examples & API consistency. Establish feedback loops (surveys, issue trackers) throughout the dev lifecycle. --- 🔍 Key Comparisons UX vs. Usability → UX = Usability + Emotional response. Dark Pattern vs. Legitimate Persuasion → Dark pattern: misleads/coerces; Persuasion: transparent, user‑centered. Profit‑Driven Design vs. Ethical UX → Profit‑driven: may sacrifice user well‑being for growth; Ethical UX: balances business goals with user rights. Developer Experience vs. End‑User Experience → DX focuses on tools & APIs for creators; End‑User UX focuses on final product interaction. --- ⚠️ Common Misunderstandings “UX is just UI design.” – UI is a visual layer; UX encompasses the whole user journey. “If a task is easy, UX is good.” – UX also requires positive feelings and alignment with user values. “Dark patterns are just clever tricks.” – They are unethical manipulations that can breach regulations. “Accessibility is optional.” – It’s a core component of inclusive UX and often a legal requirement. “DX only matters for SaaS.” – Any product with a developer‑facing component benefits from good DX. --- 🧠 Mental Models / Intuition “UX as a Story” – Each interaction is a scene; the overall experience is the narrative arc shaped by memorable scenes and external chapters (brand, price, word‑of‑mouth). “Hedonic‑Pragmatic Balance” – Imagine a scale: task success on one side, pleasure on the other; the best UX keeps both sides balanced. “Dark Pattern Funnel” – Visualize a funnel that narrows user choice deliberately; spotting the funnel helps flag manipulation. --- 🚩 Exceptions & Edge Cases External Influences – Strong brand reputation can offset a poor momentary interaction, and vice‑versa. Temporal Weighting – A single salient failure (e.g., a crash) can dominate long‑term perception despite many smooth interactions. Legal vs. Ethical – Some dark patterns may not violate law but still breach ethical UX standards. DX in Closed‑Source – Even internal developer tools need DX focus; otherwise productivity suffers. --- 📍 When to Use Which Choose Evaluation Method Questionnaires: when you need large‑scale, quantitative sentiment data. Usability Tests: when you need detailed behavioral insights on task flow. Journey Mapping: when analyzing end‑to‑end experience across multiple touchpoints. Apply Dark‑Pattern Checklist – Use whenever reviewing new UI flows, especially for checkout, sign‑up, or subscription steps. Prioritize Accessibility – Apply WCAG checks for any public‑facing product; treat as baseline, not optional. Invest in DX – When your product’s success depends on third‑party developers adopting your API or SDK. --- 👀 Patterns to Recognize Opt‑Out Defaults – Checkboxes pre‑checked for newsletters, data sharing. Hidden Costs – Extra fees revealed only at final checkout. Sneaky Navigation – “Cancel” button styled like a link, placed near “Confirm”. Deep Information Architecture – More than three clicks to reach core content. Fragmented Docs – API references scattered, missing quick‑start guides. --- 🗂️ Exam Traps Confusing Usability with UX – Remember the hedonic component; a usable product isn’t automatically a good UX. Assuming All Dark Patterns Are Illegal – Some are legal but still unethical; the key is intent and user impact. Overlooking External Factors – Brand, price, and social proof can outweigh a single interaction; don’t ignore them on exams. Mixing Up DX and UI UX – DX concerns developer tools, not the visual UI of the end product. Mis‑labeling Inclusive Design as “Extra” – Accessibility is a core UX requirement, not a bonus.