Transcript Threshold and Ceiling

CS 376
June 3, 2008
Nicholas Briggs, Michael Fischer, Sudheendra Hangal
1999
2008
Is this diagram too limiting?
What are the implications for
Prototyping and Development
tools?
Should the same tools be used
on devices at different scales?
Should the same applications
be built at each scale?
How should new input devices
and modalities be prototyped?
How much
should tools
guide designers
and developers
in creating
interfaces?


Low-threshold prototyping for devices
Integrated user test and analysis
◦ Video (why is video more important here than with
software?)
◦ Associate actions with snippets of video
Debuggers
Who is the ideal user?
Chickenfoot: "End-user" programming for the web, e.g.
enter ("Olympics"); click ("feeling lucky");
Greasemonkey: HTML/DOM etc. e.g.
document.frames[0].links[2]...
General theme (Rob Miller et al):
"Sloppy" Programming
Low information content in routine syntax
Inky: sloppy command line for the web, e.g.
% email CS376_presentation to Nick
% reserve Gates-498 4-5pm
What is the right level of end-user
programming?
What alternatives are there?


Watch what people do instead of requiring an
input
Classifiers used to determine input
◦ Fast test-analyze-update iterations
◦ Rapid feedback

Crayon metaphor




d.tools: Devices
Crayons: Vision
SUEDE: Speech
What other input types could use a rapid
prototyping tool?