Why Experimental Interfaces Should Include an Application Programming Interface

Authors

  • Stan Ruecker
  • Peter Hodges Illinois Institute of Technology
  • Nayaab Lokhadwala Illinois Institute of Technology
  • Szu-Ying Ching Illinois Institute of Technology
  • Jennifer Windsor University of Alberta
  • Antonio Hudson Illinois Institute of Technology
  • Omar Rodriquez University of Alberta

DOI:

https://doi.org/10.22230/src.2015v6n2a220

Keywords:

Application Programming Interface, API, Experimental Interface Design, Digital Humanities, Prototype

Abstract

An Application Programming Interface (API) can serve as a mechanism for separating interface concerns on the one hand from data and processing on the other, allowing for easier implementation of alternative human-computer interfaces. The API can also be used as a sounding board for ideas about what an interface should and should not accomplish. Our discussion will take as its case study our recent work in designing experimental interfaces for the visual construction of Boolean queries, for a project we have previously called the Mandala Browser.

Author Biography

Stan Ruecker

Stan Ruecker is Associate Professor at the Institute of Design, Illinois Institute of Technology, 350 North La Salle Street, 4th Floor, Chicago, IL, USA 60610

Downloads

Published

2015-10-14

Issue

Vol. 6 No. 2 (2015)

Section

Articles

License

SRC embraces online publishing and open access to back issues under the Creative Commons Attribution-Noncommercial-No Derivative Works 4.0 Licence. This license allows users to download an article and share it with others as long as authorship and original publication is acknowledged and a link is made (in electronic media) to the original article. The article can be quoted but not changed and presented differently.