13.09.2016 Views

TINK - sketching product experiences of connected objects

Tink is the result of my graduation project from the master in design for interaction at TUDelft. Tink is a web platform that connects products with one another via the Internet, it provides designers with a complete Internet of Things (IOT) development environment. Designers are provided with a rich stack of features to sketch, prototype and test IOT projects. Tink is a user-friendly, visual, collaborative, open-source tool for designers to build connected interactions among objects.

Tink is the result of my graduation project from the master in design for interaction at TUDelft.

Tink is a web platform that connects products with one another via the Internet, it provides designers with a complete Internet of Things (IOT) development environment.
Designers are provided with a rich stack of features to sketch, prototype and test IOT projects. Tink is a user-friendly, visual, collaborative, open-source tool for designers to build connected interactions among objects.

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Testing - 91<br />

session the assignment was reformulated<br />

in a more concrete example.<br />

EXPRESSING AVAILABILITIES<br />

Due to our constant connection to<br />

the internet trough different mobile<br />

platforms and devices, we are always<br />

reachable.<br />

Refusing a call might result in a<br />

bad experience for the caller, but is<br />

sometimes necessary.<br />

How can we notify our availability to<br />

friends and family trough a tangible<br />

interaction?<br />

The participants where asked to brainstorm<br />

on the assignment and design a <strong>product</strong><br />

that would solve the given problem. At<br />

the end, they where asked to represent a<br />

system diagram <strong>of</strong> the designed <strong>product</strong> on<br />

paper.<br />

3) USE <strong>TINK</strong> (25min.)<br />

In the third phase the participants had to<br />

use <strong>TINK</strong> to draw the system diagram for<br />

the <strong>product</strong> envisioned in the first phase<br />

<strong>of</strong> the session. Help was provided by the<br />

facilitator just in case the participants got<br />

stuck or when explicitly requested.<br />

4) INTERVIEW (15min.)<br />

Once the participants where satisfied with<br />

their system diagram they were asked<br />

to explain it. An interview was then<br />

conducted to discuss their <strong>experiences</strong>,<br />

the difficulties they encountered with the<br />

interface and gain feedback on the overall<br />

experience.<br />

Figure 44. Setup <strong>of</strong> the user-test<br />

2)EXPLANATION OF <strong>TINK</strong> (10min.)<br />

<strong>TINK</strong> functionalities where then<br />

demonstrated and explained to the<br />

participants. The roles <strong>of</strong> the different<br />

entities and building blocks <strong>of</strong> the <strong>TINK</strong><br />

system were described to the participants<br />

and also provided to them in a printout,<br />

which would be available for their reference<br />

in the next phase <strong>of</strong> the testing.<br />

It was highlighted during the presentation<br />

how important it was to give selfexplanatory<br />

names both to the entities and<br />

to the building blocks.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!