CoChat

API Designers in the Field: Design Practices and Challenges for Creating Usable APIs

Murphy, Lauren, Kery, Mary Beth, Alliyu, Oluwatosin, Macvean, Andrew, Myers, Brad A. · 2018 · 2018 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)

The DOI matches its Crossref record; 34 of the 35 references it cites were found in a registry or an index.

Abstract

Application Programming Interfaces (APIs) are a rapidly growing industry and the usability of the APIs is crucial to programmer productivity. Although prior research has shown that APIs commonly suffer from significant usability problems, little attention has been given to studying how APIs are designed and created in the first place. We interviewed 24 professionals involved with API design from 7 major companies to identify their training and design processes. Interviewees had insights into many different aspects of designing for API usability and areas of significant struggle. For example, they learned to do API design on the job, and had little training for it in school. During the design phase they found it challenging to discern which potential use cases of the API users will value most. After an API is released, designers lack tools to gather aggregate feedback from this data even as developers openly discuss the API online.

Overview

Integrity signals

Registry

Crossref · 10.1109/vlhcc.2018.8506523

Cites

34 of 34 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Citations

Cites

Show all 34 references

Research works printed but not linked: 13

  1. 2018, FxCop FxCop
  2. 2018, Clang Clang-Tidy
  3. 10.1145/2851581.2851602 · DOI
  4. iyer, 2015, The Strategic Value of APIs, Harvard Business Review
  5. clarke, 2005, Describing and Measuring API Usability with the Cognitive Dimensions
  6. 2017, $200+ Billion Application Programming Interfaces (API) Markets 2017-2022 Focus on Telecoms and Internet of Things
  7. 10.1145/1453101.1453117 · DOI · Paper page
  8. iyengar, 2017, What it really takes to capture the value of APIs, McKinsey & Company
  9. 10.1145/2896587 · DOI · Paper page
  10. 2017, API Design Guide
  11. macvean, 2016, API Usability at Scale, 27th Annual Workshop of the Psychology of Programming Interest Group - PPIG 2016, 177
  12. 2016, API Design
  13. lewis, 1993, Task-centered user interface design, A Practical Introduction

Cited by

See all 39

Metadata

Authors
Murphy, L., Kery, M. B., Alliyu, O., Macvean, A., & Myers, B. A.
Affiliations
  • University of Michigan (US)
  • Capital Medical University (CN)
  • Haverford College (US)
  • Google (United States) (US)
Venue
2018 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)
Publisher
IEEE
Published
2018-10
Pages
249-258
ISSN
1943-6092 (ISSN-L)
OpenAlex
W2898149195
Cited by
38
References
35
Citations by year
2026: 2 · 2025: 3 · 2024: 10 · 2023: 4 · 2022: 4 · 2021: 6 · 2020: 6 · 2019: 3
FWCI
3.02
Type
conference paper
Language
en
Open access
closed
Locations
IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Human-Computer Interaction › Usability and User Interface Design
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
Keywords
API design, API usability, developer productivity, design practice, developer training, use case analysis, developer feedback, developer communities

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: API Designers in the Field: Design Practices and Challenges for Creating Usable APIs. https://app.cochat.ai/papers/10.1109/vlhcc.2018.8506523
The paper
Murphy, L., Kery, M. B., Alliyu, O., Macvean, A., & Myers, B. A. (2018). API Designers in the Field: Design Practices and Challenges for Creating Usable APIs. 2018 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC). https://doi.org/10.1109/vlhcc.2018.8506523

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.