TINK - sketching product experiences of connected objects

Recommendations

Info

42 - TINK 2.4 Tools users Figure 27. End User, Maker and developer: 3 target user of Connected Object tools The fact that different tools require different levels of skill as shown in Figure 26 is also directly connected to the fact that the different solutions are targeting tree different user groups: The End-user End users might be interested in Connected Object tools to simplify their life, keep in touch with people and monitor things over longer distances. In terms of skill, end user don’t have electronic or programming background, they are however able to operate smartphone apps and computers. As already discussed in the chapter about tools, end user products present a limited amount of “openness”. Tools designed for end users are most of the times a combination of hardware and software. This creates a uniform user experience, does
Market analysis - 43 not require the user to choose a specific platform and limits the functionalities to what is really needed. In order to be simple to use, end user tools usually perform one very specific task, providing a very limited amount of options. The Maker Makers are interested in IoT tools that allow them to bring their ideas to life. They have some programming or electronic experience, but in most of the cases they start working on a project by looking at tutorials online. Makers look for versatile tools: usable in different contexts and for multiple projects. Since makers look for the easiest way to implement their ideas, they prefer to hack and modify tools rather than starting with something from scratch. The Developer Prototyping software and hardware is part of the developer’s profession. Most of the time developers have engineering backgrounds, therefore they are either very capable in software or in electronics. Tools targeting developers make use of the specific expertise developers have. In the research for example several boards targeting software developers were identified. The Tessel Board, for instance, is targeting web developers, it comes with a set of sensors that can easily be snapped on to the board to facilitate the electronic development. Additionally the Tessel board can be programmed in Javascript, a very common web programming language. Developers look for tools that are scalable, efficient and stable. They have to feel in control of the project, and even though they might make use of third party libraries, they are able to understand and modify those if required. While the categorization might seem very strong, it is clear in the graph ... that there is some overlap between tools for endusers, makers and developers. Makers in fact might be interested in hacking a product designed for end-user in order to accomplish their goals and at the same time developers might use maker tools to quickly produce and test a prototypes. The interaction designer Defining the average skill level of interaction designers is not easy. A big debate is going on about how much interaction designers need to know about coding or electronics. According to the study program followed, some users might be more skilled with programming and electronic and some won’t. If I look at my fellow interaction design student trained at TU Delft, I can place most of them between makers and end users, in fact some have good making skills, but most of them do not.
Page 1: sketching product experiences of co
Page 5 and 6: Introduction This paper is a summar
Page 7 and 8: CHAPTER 4 67 CHAPTER 5 83 CHAPTER 6
Page 9 and 10: Graduation Assignment - 9 CHAPTER 1
Page 11 and 12: Graduation Assignment - 11 1.1 Sket
Page 13 and 14: Graduation Assignment - 13 bad stru
Page 15 and 16: Graduation Assignment - 15 fact ske
Page 17 and 18: Graduation Assignment - 17 phase. A
Page 19 and 20: Graduation Assignment - 19 1.2 Abou
Page 21 and 22: Graduation Assignment - 21 Figure 7
Page 27 and 28: Graduation Assignment - 27 not expe
Page 29 and 30: CHAPTER 2 Market analysis In the be
Page 31 and 32: Market analysis - 31 Devices The de
Page 33 and 34: Market analysis - 33 1 #011231=#ff0
Page 35 and 36: Market analysis - 35 2.2.2 - Object
Page 37 and 38: Market analysis - 37 2.2.4 - remote
Page 39 and 40: Market analysis - 39 2.2.6 - Object
Page 41: Market analysis - 41 require more t
Page 45 and 46: Market analysis - 45 2.5.1 Hardware
Page 47 and 48: Market analysis - 47 SEVERAL NODES
Page 49 and 50: Market analysis - 49 THE EVENTS LIN
Page 51 and 52: Market analysis - 51 THE REMOTELY C
Page 53: Market analysis - 53
Page 56 and 57: 56 - TINK After having analyzed dif
Page 58 and 59: 58 - TINK Phase 3- Imagine if… Fi
Page 60 and 61: 60 - TINK Research results The reco
Page 62 and 63: 62 - TINK a step was missing: The d
Page 64 and 65: 64 - TINK 3.5 Program of requiremen
Page 67 and 68: CHAPTER 4 Final design Guided by th
Page 69 and 70: Final design - 69 private copy on a
Page 71 and 72: Final design - 71 Monitor Edit Ciao
Page 74: Building blocks Data To Track trigg
Page 77 and 78: Final design - 75 Visual feedback H
Page 79 and 80: Monitor Edit Ciao Lorenzo Final des
Page 81 and 82: Final design - 79 The lamp is now c
Page 83: Final design - 81 developed for sta
Page 86 and 87: 84 - TINK 5.1 Prototyping TINK The
Page 88 and 89: 86 - TINK 5.2 Connecting a coffee m
Page 90 and 91: 88 - TINK 5.3 Prototyping the user
Page 92 and 93:
90 - TINK 5.4 User Test As describe
Page 94 and 95:
92 - TINK 5.4.3 User test results T
Page 96 and 97:
94 - TINK state in a single action.
Page 99 and 100:
CHAPTER 6 Evaluation Here, the grad
Page 101 and 102:
Evaluation - 99 With TINK however,
Page 103 and 104:
Evaluation - 101 related to an enti
Page 105 and 106:
Evaluation - 103 students talking a
Page 107 and 108:
Evaluation - 105 should provide too
Page 109 and 110:
Evaluation - 107 DESIGN After the r
Page 111 and 112:
References - 109 }. Retrieved June
Page 113:
References - 111
show all

TINK - sketching product experiences of connected objects

Create successful ePaper yourself

Delete template?

Save as template?