The diary study: a workplace-oriented research tool to guide laboratory efforts
CHI '93 Proceedings of the INTERACT '93 and CHI '93 Conference on Human Factors in Computing Systems
Past, present, and future of user interface software tools
ACM Transactions on Computer-Human Interaction (TOCHI) - Special issue on human-computer interaction in the new millennium, Part 1
Papier-Mache: toolkit support for tangible input
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Six Learning Barriers in End-User Programming Systems
VLHCC '04 Proceedings of the 2004 IEEE Symposium on Visual Languages - Human Centric Computing
prefuse: a toolkit for interactive information visualization
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Proceedings of the 2006 AVI workshop on BEyond time and errors: novel evaluation methods for information visualization
iStuff mobile: rapidly prototyping new mobile phone interfaces for ubiquitous computing
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
The Factory Pattern in API Design: A Usability Evaluation
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Usability evaluation for enterprise SOA APIs
Proceedings of the 2nd international workshop on Systems development in SOA environments
A survey of software learnability: metrics, methodologies and guidelines
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
API usability: report on special interest group at CHI
ACM SIGSOFT Software Engineering Notes
Lessons learned from the design and evaluation of visual information-seeking systems
International Journal on Digital Libraries
| Hi-index | 0.00 |
Application programming interfaces (APIs) are the interfaces to existing code structures, such as widgets, frameworks, or toolkits. Therefore, they very much do have an impact on the quality of the resulting system. So ensuring that developers can make the most out of them is an important challenge. However standard usability evaluation methods as known from HCI have limitations in grasping the interaction between developer and API -- the GUI, which makes this interaction obvious, is missing. In this paper we present a longitudinal approach using concept maps and a question diary to make this interaction visible and study the usability of an API over time.