# user testing Published articles for user testing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Prototyping with Framer DevFeed: [Prototyping with Framer]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-10-03T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [Testing](), [coding](), [backends]() Tags: [backends](), [engineering](), [framer](), [news](), [prototype](), [prototyping](), [user-testing](), [web-frontend]() ### AI overview Khan Academy describes how it uses prototypes in user testing to gather feedback on new designs. The article explains the role of low- and high-fidelity prototypes, their limited lifespan, and the choice of Framer for creating and revising prototypes quickly. ### Source excerpt By Nick Breen We strive to make all of Khan Academy's new features & experiences easy to understand ... Read more ## Object-Oriented UI Design: How You Can Collaborate Seamlessly with Developers and Build Better Products DevFeed: [Object-Oriented UI Design: How You Can Collaborate Seamlessly with Developers and Build Better Products]() Original publisher: [Read original article]() Author: William Hudson Published: 2026-09-16T09:07:08Z Content type: tutorial Language: en Sources: [UX Daily - User Experience Daily]() Topics: [User interface design](), [User Experience](), [Code](), [Testing]() Tags: [code](), [design](), [developer](), [ui](), [user-testing]() ### AI overview This video tutorial explains object-oriented UI design as a way for designers and developers to share a conceptual model. It uses familiar objects such as appointments, their attributes, and their operations to clarify collaboration and create more natural interfaces. ### Source excerpt You're at your routine health checkup, sipping an iced coffee on a hot day. Suddenly, you get a sharp pain in your head. The doctor looks up from her notes, a sympathetic expression on her face. "You're experiencing sphenopalatine ganglioneuralgia." Your heart sinks. The coffee cup drops to the floor. Medication? Surgery? How long do you have? "Sorry! Doctor speak," she says, noticing your panic. "You have brain freeze." Two completely different terms for the exact same thing, and one of them nearly gave you a panic attack.Designers and developers do this to each other all the time. You call it an "appointment," the developer calls it an "event," and the database calls it a "record." Everyon... ## Food Delivery & Takeout UX Benchmark: 3,100+ Performance Scores and 1,900+ Best Practice Examples DevFeed: [Food Delivery & Takeout UX Benchmark: 3,100+ Performance Scores and 1,900+ Best Practice Examples]() Original publisher: [Read original article]() Author: Anders Nielsen Published: 2026-08-13T08:01:00Z Content type: article Language: en Sources: [Baymard Institute]() Topics: [Benchmark](), [User experience (UX)](), [App](), [web applications]() Tags: [apps](), [article](), [benchmark](), [case-studies](), [customer](), [ecommerce](), [insights](), [mobile](), [performance](), [research](), [retail](), [user-testing](), [ux]() ### AI overview Baymard presents a Food Delivery & Takeout UX benchmark based on eight mobile sites and apps assessed across more than 390 research-based UX parameters. The benchmark reports over 3,100 weighted performance scores and 1,900 best-practice examples, with overall experiences ranging from poor to mediocre. Key weaknesses include repeat ordering, dietary and customization support, category filters, navigation, fulfillment timing, and tipping details. ### Source excerpt (Note: Unfortunately, e-mail and RSS don't support advanced layouts and features. If the graphics in this article look strange, you may want to read the article in your web browser.) At Baymard, we've just released a new UX benchmark with 8 "Food Delivery & Takeout" UX case studies. This follows our large-scale user testing on Food Delivery & Takeout UX and adds to our existing ecommerce UX benchmark. In this article, we give you a snapshot of the overall UX performance. 8 Food Delivery & Takeout UX Case Studies and the Overall Performance Just Eat mediocre Food Delivery & Takeout 49 page designs: mobile, app KFC mediocre Food Delivery & Takeout 48 page designs: mobile, app Uber Eats mediocre Food Delivery & Takeout 54 page designs: mobile, app Domino's Pizza poor Food Delivery & Takeout 34 page designs: mobile, app DoorDash poor Food Delivery & Takeout 48 page designs: mobile, app McDonald's poor Food Delivery & Takeout 39 page designs: mobile, app Deliveroo poor Food Delivery & Takeout 53 page designs: mobile, app Burger King broken Food Delivery & Takeout 41 page designs: mobile, app YourSite.com? Want to know how your site performs? Get Premium access to review your own site or have it audited by Baymard researchers. These are the 8 in-depth Food Delivery & Takeout UX case studies. The 8 mobile sites and apps have been manually assessed across 390+ research-based UX parameters relevant to Food Delivery & Takeout, resulting in 3,100+ weighted UX performance scores and 1,900+ best practice examples from these mobile sites and apps. Each of the 3,100+ UX performance scores from the 8 case studies is summarized in the interactive scatterplot below -- showing you how they perform collectively and individually: {{ scatterplot-graph: size=big + habitat=public + base-sites=collection:online-food-delivery + view-structure-id=gemini-st_l9jw5tjp }} The overall UX performance of the Food Delivery & Takeout sites and apps ranges from "poor" to "mediocre". What is missing is a ## Dogfooding vs. QA vs. User Research DevFeed: [Dogfooding vs. QA vs. User Research]() Original publisher: [Read original article]() Author: Therese Fessenden Published: 2026-08-07T17:00:00Z Content type: article Language: en Sources: [NN/g latest articles and announcements]() Topics: [dogfooding](), [FIRST]() Tags: [article](), [bugs](), [development](), [dogfooding](), [qa](), [qc](), [quality-assurance](), [quality-control](), [user-research](), [user-testing]() ### AI overview Dogfooding--using a company's own products internally--can reveal bugs, broken flows, crashes, and missing features while building empathy and shared ownership. The article explains that it complements but cannot replace user research, because insiders understand the product too well to represent real users. It also distinguishes genuine dogfooding from performative displays of loyalty. ### Source excerpt Dogfooding, or using your own products internally, helps catch bugs, but it can't replace user research: your team knows too much to represent real users. ## Internet Service Providers UX Benchmark: 1,700+ Performance Scores and 1,100+ Best Practice Examples DevFeed: [Internet Service Providers UX Benchmark: 1,700+ Performance Scores and 1,100+ Best Practice Examples]() Original publisher: [Read original article]() Author: Anders Nielsen Published: 2026-07-28T05:27:00Z Content type: article Language: en Sources: [Baymard Institute]() Topics: [Benchmark](), [User experience (UX)](), [User Experience](), [web applications]() Tags: [article](), [benchmark](), [case-studies](), [ecommerce](), [performance](), [research](), [user-testing](), [ux]() ### AI overview Baymard presents a UX benchmark covering seven Internet Service Provider websites. Based on large-scale user testing, the benchmark reports 1,700+ weighted UX performance scores and 1,100+ best-practice examples. Overall performance is described as mediocre, with recurring problems in plan comparison and application flows, including dense layouts, unclear pricing, weak guidance, and form friction. ### Source excerpt (Note: Unfortunately, e-mail and RSS don't support advanced layouts and features. If the graphics in this article look strange, you may want to read the article in your web browser.) At Baymard, we've just released a new UX benchmark with 7 "Internet Service Providers (ISP)" UX case studies. This follows from our large-scale user testing and adds to our existing ecommerce UX benchmark. In this article, we give you a snapshot of the overall UX performance. 7 Internet Service Providers UX Case Studies and the Overall Performance BT mediocre Internet Service Providers 26 page designs: desktop, mobile Telekom mediocre Internet Service Providers 35 page designs: desktop, mobile Frontier mediocre Internet Service Providers 25 page designs: desktop, mobile COX mediocre Internet Service Providers 24 page designs: desktop, mobile CenturyLink mediocre Internet Service Providers 25 page designs: desktop, mobile Viasat mediocre Internet Service Providers 32 page designs: desktop, mobile Spectrum mediocre Internet Service Providers 15 page designs: desktop, mobile YourSite.com? Want to know how your site performs? Get Premium access to review your own site or have it audited by Baymard researchers. These are the 7 in-depth ISP UX case studies. The 7 ISP sites have been manually assessed across 280+ research-based UX parameters relevant to Internet Service Providers, resulting in 1,700+ weighted UX performance scores and 1,100+ best practice examples from these desktop and mobile sites. Each of the 1,700+ UX performance scores from the 7 ISP case studies is summarized in the interactive scatterplot below -- showing you how they perform collectively and individually: {{ scatterplot-graph: size=big + habitat=public + base-sites=collection:internet-service-providers + view-structure-id=gemini-st_9en1b7zd }} The overall UX performance of the ISP sites is "mediocre," with 1 site just on the border of "poor". ISP sites typically offer a narrow set of services, but these services come wi ## 10 modern UI/UX design tools: Build impactful client sites DevFeed: [10 modern UI/UX design tools: Build impactful client sites]() Original publisher: [Read original article]() Author: Webflow Team Published: 2026-07-02T00:00:00Z Content type: article Language: en Sources: [Webflow Blog]() Topics: [UI/UX Design](), [User interface design](), [User Experience](), [webflow](), [Sketch](), [Figma](), [Content Management System](), [CSS](), [HTML]() Tags: [collaboration](), [css](), [design](), [design-tools](), [figma](), [html](), [prototyping](), [tools](), [ui-ux-design](), [user-testing](), [webflow](), [workflows]() ### AI overview A guide to 10 UI/UX design tools for creating client websites, with use cases spanning visual design, handoffs, remote collaboration, structured experiences, user testing, prototyping, and defined user journeys. It also explains how Webflow supports visual website building, interactions, responsive testing, content management, and launch workflows. ### Source excerpt Explore 10 of the best UI/UX design tools for building different kinds of client websites and improving collaboration on a wide range of project types. ## Ethical UX: How Design Nudges Influence User Behavior DevFeed: [Ethical UX: How Design Nudges Influence User Behavior]() Original publisher: [Read original article]() Author: Tushar Deshmukh Published: 2026-04-28T03:13:31Z Content type: article Language: en Sources: [UX Magazine]() Topics: [User Experience](), [User experience (UX)]() Tags: [design](), [digital-experiences](), [ethics](), [user-testing](), [ux]() ### AI overview This ninth entry in the Ethical UX Series examines how small design elements, or nudges, influence user behavior. It explains mechanisms such as tooltips, guidance bubbles, and pre-selected options, while distinguishing ethical assistance from manipulation. ### Source excerpt Part 9 of the "Ethical UX Series." What is ethical UX, and why does this series exist? At the heart of WorldUXForum, we believe that design is not just about functionality or aesthetics -- it's about responsibility. Every pixel, interaction, and pathway we craft shapes user behavior. The "Ethical UX Series" is our ongoing effort The post The Psychology of Nudges: Why the Smallest Design Element Can Shift the Biggest Outcomes appeared first on UX Magazine. ## How Headspace built an AI companion that fosters trust and transparency DevFeed: [How Headspace built an AI companion that fosters trust and transparency]() Original publisher: [Read original article]() Author: Matt Alagiah Published: 2025-05-05T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Artificial Intelligence](), [Conversational AI](), [User experience (UX)](), [App]() Tags: [ai](), [app](), [building](), [business](), [conversational-ai](), [health](), [mental-health](), [product](), [product-design](), [safety](), [user-testing](), [ux](), [ux-design](), [workshops]() ### AI overview This article describes how Headspace created Ebb, an AI companion for reflective practice and mental health support between therapy sessions. The product and brand teams emphasized safety, transparency, careful positioning, workshops, naming, and user testing to build trust and avoid presenting Ebb as a replacement for human care. ### Source excerpt Creating an AI-powered feature for mental health poses myriad challenges--especially around keeping users safe and supported. Here, the product and brand teams talk through how they built Ebb with care and sensitivity. ## Pablo Sánchez's 7 rules for designing the unexpected DevFeed: [Pablo Sánchez's 7 rules for designing the unexpected]() Original publisher: [Read original article]() Author: Pablo Sánchez Published: 2024-11-26T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [App](), [MIDI]() Tags: [design](), [digital-design](), [digital-experiences](), [music](), [ui](), [user-testing]() ### AI overview Designer Pablo Sánchez presents seven principles for creating unexpected digital experiences, drawing on the development of Ableton's Note app. The article emphasizes personal conviction, direct and tactile interaction, brainstorming without external references, and combining influences into distinctive designs. ### Source excerpt The designer of Ableton's Note app shares unconventional principles for creating unforgettable digital experiences. ## Behind the Flame: Sam Willis DevFeed: [Behind the Flame: Sam Willis]() Original publisher: [Read original article]() Author: Megan Batterbury Published: 2024-10-23T14:35:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident](), [data]() Tags: [business](), [design](), [development](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [post-mortem](), [product-engineering](), [slack-incident](), [user-testing]() ### AI overview A profile of Sam Willis, a Product Designer at incident.io, covering the six-month On-call launch, the company's collaborative design process, and the feedback contributed by founders, colleagues, Customer Success, and customers. Sam also discusses design details, the company logo, workplace culture, and collaboration across Product Engineering, Data, Customer Success, user testing, development, and delivery. ### Source excerpt Meet Sam, Product Designer 🔥 ## Why cultivating a prototyping culture will help you build better products DevFeed: [Why cultivating a prototyping culture will help you build better products]() Original publisher: [Read original article]() Author: Nikolas Klein; Garrett Miller Published: 2023-12-08T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [ide]() Tags: [design](), [development](), [experience-design](), [experimentation](), [figma](), [innovation](), [product-development](), [prototyping](), [user-testing](), [workflow]() ### AI overview The article explains how cultivating a prototyping culture improves product development. Interactive prototypes help teams identify navigation and usability issues early, test and validate ideas rapidly, save engineering time, streamline workflows, and help designers communicate proposals and gain organizational support. ### Source excerpt Prototyping, once an eleventh-hour nice-to-have, has risen to become a critical tool at multiple points in the product development workflow. ## The Figma prototype challenge: 15 tips in 15 days DevFeed: [The Figma prototype challenge: 15 tips in 15 days]() Original publisher: [Read original article]() Author: Ana Boyer Published: 2021-12-14T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [micro-interactions for websites]() Tags: [animation](), [best-practices](), [building](), [components](), [experiment](), [figma](), [how-to](), [learn](), [mobile](), [prototypes](), [prototyping](), [recap](), [reduce](), [smart](), [techniques](), [updates](), [user-testing]() ### AI overview A two-week Figma prototyping challenge presents 15 tips covering advanced prototyping techniques, interactive components, smart animate, nested interactions, and mobile navigation. The article recaps the challenge and points readers to Figma Community files and practical examples. ### Source excerpt One of our Designer Advocates recently kicked off a two-week prototyping challenge to help teach the community about advanced prototyping techniques in Figma. Check out all of Ana's 15 tips here. ## How we conduct user interviews and user tests at Clue: Part Two DevFeed: [How we conduct user interviews and user tests at Clue: Part Two]() Original publisher: [Read original article]() Author: Caro Hardy Published: 2018-05-11T13:26:29Z Content type: article Language: en Sources: [Bleeding Edge - Medium]() Topics: [App](), [data]() Tags: [insights](), [interviews](), [product-design](), [software-development](), [user-interviews](), [user-research](), [user-testing](), [ux]() ### AI overview This article explains how Clue conducts user interviews, including introductory questions, baseline questions about app usage, questions about competing alternatives, and project-specific research questions. ### Source excerpt To learn about our process, read Part One. Illustration by Marta PucciInterview sessions Once we have someone in the office, on the phone or on Google Hangouts, how do we carry out user interviews? Ideally, an interview will teach us one or more of the following things: Teach me something about people. Who are they? What's important to them? What's their story? Teach me something about how and why people use Clue. When do they starting thinking about it? What motivates them to look for something like it? Do they do research? Who do they ask? Teach me something about competing alternatives. What does Clue replace? How is it perceived against what they were doing before? How do people weigh up different options? The typical questions we ask I break the interview questions down into three categories. Introductory questions I'll start off with some super basic questions to get people warmed up. Some people find the experience a little weird at first, so this is an opportunity to get them used to the process. Questions: Tell me about yourself? What do you do for a living? How long have you lived in Berlin? The standards questions After the breaking the ice, I'll move onto some questions to get baseline insights from them. To give examples, they include questions such as: Which device do you use? How long are you using Clue? What do you use Clue for? What categories do you track in Clue? How often do you track? I'll ask questions about how they searched for such solutions: How did you hear about Clue? Do you currently use other female health apps? What for and why? Did you switch from another app to Clue? Which one? Why did you switch? And I'll ask questions about usage: Beside your period, do you track any other options? Which ones? Why? Have you entered anything into Clue today? When do you usually do it? At what time of the day? Where? (I want to know if they mostly do instant data entry or a posteriori tracking) Can you show me how you do it? (and I would about look w ## How we conduct user interviews and user tests at Clue: Part One DevFeed: [How we conduct user interviews and user tests at Clue: Part One]() Original publisher: [Read original article]() Author: Caro Hardy Published: 2018-05-11T13:25:25Z Content type: article Language: en Sources: [Bleeding Edge - Medium]() Topics: [User interface design](), [Testing](), [Usability](), [App]() Tags: [app](), [design](), [interviews](), [product-design](), [prototype](), [testing](), [tests](), [usability](), [user-interviews](), [user-research](), [user-testing](), [ux]() ### AI overview Clue explains its practical process for conducting user interviews and prototype tests throughout product design. The article describes blank-page interviews, feature research interviews, and prototype testing, with the approach shaped by the organization's stage and research goals. ### Source excerpt Illustration by Marta Pucci I find it fun to see exactly how other organizations handle certain design processes. It's the small the little details that I find interesting. So, I thought I'd lay out exactly how we do work with users for research and testing purposes at Clue. Clue is a female health tracking app based in Berlin. We're now at the stage of about 50 employees, and we've raised over $30 million from VC firms such as Union Square Ventures. More than 10 million people use Clue. The reason I give these details is that I think your organization's stage will have a big impact on your approach to user research and user testing. To give a quick example, we're not at the stage where we test a single flow with hundreds of users to get quantitative data on the usability. But we are well beyond the stage where offering free coffee in Starbucks in return for chatting to us for 10 minutes is enough for our research and testing processes. In this two-part article, I'm going to focus on the practical, step-by-step process we use for talking to users, week-in, week out. The design process Our design process at Clue focuses both on designing a product that is scientifically-valid -- our app lets people know when they can expect their period and other menstrual cycle symptoms and stages -- and responds to the needs of the people using it. That means that the two product designers at Clue work closely with scientific researchers and data scientists. This is how we make sure that the product meets rigorous scientific standards. We also talk to the users at pretty much every point across the design process. Here's how I'd break up the stages of talking to users: Blank page interviews Even when we don't have a particular feature idea in mind, we'll carry out some user interviews. At this point we're just looking for interesting problems to dig into that could be the basis of future feature ideas. Feature research interviews When we have a feature idea, we'll kick off a round of ## React Native at SoundCloud DevFeed: [React Native at SoundCloud]() Original publisher: [Read original article]() Published: 2016-08-03T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [React Native](), [Mobile](), [Development](), [iOS](), [JavaScript](), [Android](), [Code](), [Testing]() Tags: [android](), [app-development](), [ios](), [javascript](), [libraries](), [mobile](), [prototype](), [react-native](), [user-testing]() ### AI overview SoundCloud describes evaluating React Native for SoundCloud Pulse, its app for creators. The team built a two-week prototype to assess development speed, native integration, JavaScript and native code boundaries, testing, authentication, deep linking, performance, battery life, and continuous-integration compatibility. ### Source excerpt About a year ago we faced an interesting question at SoundCloud: can we build SoundCloud Pulse -- our app for creators -- with React Native? Is a five-month-old technology mature enough to become part of SoundCloud's tech stack? ## Navigate using just your keyboard DevFeed: [Navigate using just your keyboard]() Original publisher: [Read original article]() Author: Dave Rupert Published: 2013-01-11T00:00:00Z Content type: article Language: en Sources: [The A11Y Project]() Topics: [Accessibility](), [Usability]() Tags: [accessibility](), [article](), [how-to](), [testing](), [usability](), [user-testing]() ### AI overview This article explains how to navigate and test a website using only a keyboard. It covers keyboard shortcuts, visible focus styles, logical focus order, functional interactive elements, and skip links for lengthy content. ### Source excerpt Testing your site for keyboard navigation will help ensure that keyboard users can access your site. As a bonus, sites that can be navigated with a keyboard are more likely to be navigable with other input devices such as switches. How to navigate a website with a keyboard Generally, pressing Tab moves focus between interactive elements and pressing Enter will interact with them. If you are using Safari, Option + Tab is the default keyboard shortcut to move focus between elements. You can update your settings to make Tab the default navigation key by following the instructions in this article: Quick Tip: Safari Keyboard Navigation Additional keyboard shortcuts are described here: WebAIM - Keyboard Accessibility Things to keep in mind while testing It is not enough to simply tab through a webpage from start to end. While navigating the site, keep these things in mind: Interactive elements should be functional using only keyboard input. The focused element should be visible and have an obvious focus style. See article: "Quick Tip: Never remove CSS outlines". Focus should move between elements as they appear on the page and not jump back and forth. There should be a way to skip past lengthy spans of content, like global navigation menus. See article: "How-to: Use Skip Navigation links".