Introduction
What are tinyTools?
tinyTools mostly start out as proof-of-concept mockups for inspiration or to quickly check how a design-concept 'feels'. Many of these tools stop right there when the point is made. The tool has served its purpose. Other tools turn out to be more than that, and at some point we realise they could be usefull for more than our own experiments. Some of these tools are presented on these pages.
Why tinyTools?
At the ID-Studiolab, we practice 'Research Through Design'. We build working prototypes that are rich in experiential quality and developing design tools is essential to the research approach. Prototypes with design variables are tested in real environments, in an iterative cycle. Results from user experience testing leads to design knowledge and refinement of research issues.For more info on our research (which is the source of our tinyTools), visit our research pages.
How tinyTools?
The tinyTool motto is 'prototype early, prototype often', but it might as well include 'prototype quickly'. As tinyTools start out to get a quick 'feel' of a design-concept, it is important making them does not take an high effort. Therefore we use relatively low-ffort/high-result authoring tools such as Macromedia Director.Using low effort tools such not only makes it possible for most of the members of the ID-Studiolab to create tinyTools themselves (instead of a dedicated programming specialist), it also allows our students to participate in creating and evaluating tinyTools through our education programmes.
Tinytools are characterized by:
- a focused functionality (fewer features)
- a minimal interface (content up front)
- an emphasis on aesthetics (often sketchy, perceptual)
