Logo
ScienceStack
Table of Contents
Fetching ...
Sign In

Beyond Dark Patterns: A Concept-Based Framework for Ethical Software Design

Evan Caragay, Katherine Xiong, Jonathan Zong, Daniel Jackson

TL;DR

This paper advances a positive, concept-based framework for ethical software design to address dark patterns. It defines software concepts as modular units with state, actions, and UI mappings, and introduces concept catalogs to articulate standard expectations and detect deviations. Through three studies, it shows that the framework can describe existing dark patterns, handle nuanced design differences (e.g., Shopping Cart variants), and capture common functionality across popular websites. The approach holds promise for regulators and practitioners by providing a concrete, interoperable language for evaluating design ethics and guiding safer, user-centered design practices.

Abstract

Current dark pattern research tells designers what not to do, but how do they know what to do? In contrast to prior approaches that focus on patterns to avoid and their underlying principles, we present a framework grounded in positive expected behavior against which deviations can be judged. To articulate this expected behavior, we use concepts -- abstract units of functionality that compose applications. We define a design as dark when its concepts violate users' expectations, and benefit the application provider at the user's expense. Though user expectations can differ, users tend to develop common expectations as they encounter the same concepts across multiple applications, which we can record in a concept catalog as standard concepts. We evaluate our framework and concept catalog through three studies, illustrating their ability to describe existing dark patterns, evaluate nuanced designs, and document common application functionality.

Beyond Dark Patterns: A Concept-Based Framework for Ethical Software Design

TL;DR

This paper advances a positive, concept-based framework for ethical software design to address dark patterns. It defines software concepts as modular units with state, actions, and UI mappings, and introduces concept catalogs to articulate standard expectations and detect deviations. Through three studies, it shows that the framework can describe existing dark patterns, handle nuanced design differences (e.g., Shopping Cart variants), and capture common functionality across popular websites. The approach holds promise for regulators and practitioners by providing a concrete, interoperable language for evaluating design ethics and guiding safer, user-centered design practices.

Abstract

Current dark pattern research tells designers what not to do, but how do they know what to do? In contrast to prior approaches that focus on patterns to avoid and their underlying principles, we present a framework grounded in positive expected behavior against which deviations can be judged. To articulate this expected behavior, we use concepts -- abstract units of functionality that compose applications. We define a design as dark when its concepts violate users' expectations, and benefit the application provider at the user's expense. Though user expectations can differ, users tend to develop common expectations as they encounter the same concepts across multiple applications, which we can record in a concept catalog as standard concepts. We evaluate our framework and concept catalog through three studies, illustrating their ability to describe existing dark patterns, evaluate nuanced designs, and document common application functionality.
Paper Structure (27 sections, 3 figures, 3 tables)

This paper contains 27 sections, 3 figures, 3 tables.

Table of Contents

  1. Introduction
  2. Related Work
  3. Dark Patterns as Deviation from Standard Concepts
  4. Concepts
  5. Observed, Implemented, and Expected Concepts
  6. Defining Deviation
  7. Procedural Considerations
  8. Substantive Considerations
  9. Concept Catalogs: Articulating Standard Expectations
  10. Components of a Concept Catalog Entry
  11. Shopping Cart: An Example Catalog Entry
  12. Refining the definition of dark pattern
  13. Mapping Principles
  14. Transparency.
  15. Uniformity.
  16. ...and 12 more sections

Figures (3)

  • Figure 1: Shopping cart concept catalog entry that designers can can compare to check if their design fulfills the requirements set by the standard concept. (A) Standard, formal concept definition, articulating the purpose, state, and actions. (B) The required synchronizations for the shopping cart, which helps designers meet user expectations of functionality between concepts, in addition to within individual concepts. (C) Example standards for how to map the state (ex: subtotal) and actions (ex: quantity change) to the user interface.
  • Figure 2: The Grove Collaborative user interface clearly communicates that items have been added to the cart (through both text and icons) and that they can be removed. Despite this clear communication, however, some users still feel that the service is "sneaky".
  • Figure 3: Examples of shopping cart user interfaces. (A) items, quantity, price, remove() on amazon.com (B) subtotal, checkout() on amazon.com (C) add() on amazon.com