Fluid annotations in an open world
Proceedings of the 12th ACM conference on Hypertext and Hypermedia
Agile, open source, distributed, and on-time: inside the eclipse development process
Proceedings of the 27th international conference on Software engineering
Computers in Entertainment (CIE) - Social television and user interaction
Why web 2.0 is good for learning and for research: principles and prototypes
Proceedings of the 17th international conference on World Wide Web
Enterprise Mashups: Design Principles towards the Long Tail of User Needs
SCC '08 Proceedings of the 2008 IEEE International Conference on Services Computing - Volume 2
Appropriation Infrastructure: Supporting the Design of Usages
IS-EUD '09 Proceedings of the 2nd International Symposium on End-User Development
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Hi-index | 0.00 |
In Software development, the always beta principle is used to successfully develop innovation based on early and continuous user feedback. In this paper we discuss how this principle could be adapted to the special needs of designing for the Smart Home, where we do not just take care of the software, but also release hardware components. In particular, because of the 'materiality' of the Smart Home one could not just make a beta version available on the web, but an essential part of the development process is also to visit the 'beta' users in their home, to build trust, to face the real world issues and provide assistance to make the Smart Home work for them. After presenting our case study, we will then discuss the challenges we faced and how we dealt with them.