API Designers in the Field: Design Practices and Challenges for Creating Usable APIs
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
Cites
Statistics
Verification
Claims the paper makes
Citations
Cites
Using thematic analysis in psychology
Braun, V., & Clarke, V. (2006) · Qualitative Research in Psychology · doi:10.1191/1478088706qp063oa · Cited by 194,414
Interrater reliability: The kappa statistic
McHugh, M. L. (2012) · Biochemia Medica · doi:10.11613/bm.2012.031 · Cited by 19,877
Grounded theory research: Procedures, canons, and evaluative criteria
Corbin, J. M., & Strauss, A. (1990) · Qualitative Sociology · doi:10.1007/bf00988593 · Cited by 11,133
Knowledge management in software engineering
Rus, I., & Lindvall, M. (2002) · IEEE Software · doi:10.1109/ms.2002.1003450 · Cited by 742 · cited 1×
“, the role of knowledge sharing within organizations [33], the impact of distance between engineers [34], and the importance of well defined tasks [35], understanding the specifics of the API design process, and the barriers facing API designers, have not been previously studied.”
BackgroundA field study of API learning obstacles
Robillard, M. P., & DeLine, R. (2011) · Empirical Software Engineering · doi:10.1007/s10664-010-9150-8 · Cited by 352
Myers, B. A., & Stylos, J. (2016) · Communications of the ACM · doi:10.1145/2896587 · Cited by 269
Self-citationEffective Java Programming Language Guide
Bloch, J. (2001) · CERN Document Server (European Organization for Nuclear Research) · Cited by 261
Rethinking SSL development in an appified world
Fahl, S., Harbach, M., Perl, H., Koetter, M., & Smith, M. (2013) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/2508859.2516655 · Cited by 156
Tricorder: Building a Program Analysis Ecosystem
Sadowski, C., van Gogh, J., Jaspan, C. N. C., Söderberg, E., & Winter, C. (2015) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2015.76 · Cited by 152
The Factory Pattern in API Design: A Usability Evaluation
Ellis, B., Stylos, J., & Myers, B. (2007) · 29th International Conference on Software Engineering (ICSE'07) · doi:10.1109/icse.2007.85 · Cited by 148
Self-citation
Research works printed but not linked: 13
- 2018, FxCop FxCop
- 2018, Clang Clang-Tidy
- 10.1145/2851581.2851602 · DOI
- iyer, 2015, The Strategic Value of APIs, Harvard Business Review
- clarke, 2005, Describing and Measuring API Usability with the Cognitive Dimensions
- 2017, $200+ Billion Application Programming Interfaces (API) Markets 2017-2022 Focus on Telecoms and Internet of Things
- 10.1145/1453101.1453117 · DOI · Paper page
- iyengar, 2017, What it really takes to capture the value of APIs, McKinsey & Company
- 10.1145/2896587 · DOI · Paper page
- 2017, API Design Guide
- macvean, 2016, API Usability at Scale, 27th Annual Workshop of the Psychology of Programming Interest Group - PPIG 2016, 177
- 2016, API Design
- lewis, 1993, Task-centered user interface design, A Practical Introduction
Cited by
In-IDE Code Generation from Natural Language: Promise and Challenges
Xu, F. F., Vasilescu, B., & Neubig, G. (2022) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3487569 · Cited by 154
“Moreover, this need is likely to continue in the future, as new APIs appear continuously, and existing APIs change in non-backwards compatible ways [80], requiring recurring learning effort [57, 84].”
BackgroundExploring How Machine Learning Practitioners (Try To) Use Fairness Toolkits
Deng, W. H., Nagireddy, M., Lee, M. S. A., Singh, J., Wu, Z. S., Holstein, K., & Zhu, H. (2022) · 2022 ACM Conference on Fairness Accountability and Transparency · doi:10.1145/3531146.3533113 · Cited by 99
“We also identified four distinct design requirements [75, 77] ML practitioners had when using fairness toolkits, namely, (1) the abilities to use the toolkit to learn more about ML fairness and the landscape of current ML fairness research, (2) rapidly on-boarding toolkits due to workplace time…”
BackgroundMethodEnabling Data-Driven API Design with Community Usage Data: A Need-Finding Study
Zhang, T., Hartmann, B., Kim, M., & Glassman, E. L. (2020) · Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems · doi:10.1145/3313831.3376382 · Cited by 25
“Unfortunately, a recent study found that API designers still have difficulties in gathering and interpreting user feedback from their communities [37].”
BackgroundMARBLE: Mining for Boilerplate Code to Identify API Usability Problems
Nam, D., Horvath, A., Macvean, A., Myers, B., & Vasilescu, B. (2019) · 2019 34th IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2019.00063 · Cited by 19
“The understanding gained from such studies, along with the insights from experienced API designers, have led to the development of guidelines for API designs and heuristics for evaluating APIs [1]–[3], [7].”
BackgroundInfluentialSelf-citationSingjai, A., Zdun, U., & Zimmermann, O. (2021) · IEEE International Conference on Software Architecture (ICSA) · doi:10.1109/icsa51549.2021.00011 · Cited by 19
“[25] studied the usability aspect from API designers’ perspective.”
Background
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.