So once again I combined the weeknotes for the past two weeks. As things get busier in the workshop/production phase I have less and less to reflect on. I wanted to use these weeknotes as a way for me to reflect on the direction and process but I find more and more towards the end of this short project that it is slightly harder to reflect on the decision made during the design/prototyping stage because a lot of the time they just feel instinctive or as if it’s the right choice to make in order to progress.
In any case, I decided to force myself outside the workshop and sit down to reflect for just a moment on the direction I have finally decided on taking and in what way it answers the design challenge I set myself some time ago. The first thing that is obvious is the slight change in context of the design proposal. I have (through co-creation and experience prototyping) taken a step away from the ‘service of convenience’ model and more into actually helping people care for and grow a garden themselves. This is mainly due to strong feedback about the current real issues around maintaining a growing project at home. Also the idea of resonating with current, ‘cool’, technology as a platform to use in inspiring younger adults was another key piece of learning. Simply put, young people are increasing connected through devices they find cool. Why can’t something that needs to fit into their lives be the convenience side of the story? Of course I’m not saying that the delivery service concept couldn’t lend itself to this interaction also, but it seems more of larger step for people to identify with. You need to explain the service, then the interaction, then the value etc. It’s a longer, more obscured story as you are having to actually design the CONTEXT as well. (Herb subscription services don’t exist as far as my research suggests).
Enough of what I’m not doing. What I am doing is providing help in the form of, essentially, a little sensor box that sits on your freshly bought herbs or tomato growing project or chilli plant in the kitchen and provides you with a “How am I doing?” sort of information directly to iPhone through a web service. But instead of just a number, a tweet or a bar graph as feedback, what you are presented with is a data relationship specific to the place in your home that you put it. For example, someone growing a pot of basil may know that basil needs sun. Placing the pot with the sensor box on his window sill seems the obvious choice. However, having a radiator under the window sill means that water in the soil (of which basil also needs a fair amount of) seems to dry up quickly. So although the spot seems perfect based on the information provided wherever the basil was bought, actually it’s not. How would you know that? Another example. Am I giving my basil too much or too little water. To you and me looking at a basil wilting, it’s hard to know. It’s hard to remember. Is it dry? Didn’t I water it yesterday? Oh no did I give it too much? This is the lack of information that I am hoping to address. But this isn’t a new thing. Sensing our environment, specifically our home environment, has always been an interest for many who want to save money and energy. And it’s playing an increasingly important role in defining the energy efficiency market. Having knowledge and thereby developing control over your environment is an expanding field that, in my opinion, needs serious attention in the design world in order to allow people to easily, quickly and WISELY make decisions that can long term effects and consequences. Such as the long term consequences, coming back to my project, of plants and horticulture that aren’t cared for in the right way that is specific to YOUR environment, YOUR plant and YOUR lifestyle.
This is what Urbbi is. Urbbi is your little urban gardener. Your little friend who reminds you in a delightful way about the consequences of your environment on the plants you keep & grow. It does this is many ways:
It provides status (What’s up?).
It provides the historical, environmental ‘rhythm’ of your home. (How’s your day been?)
It provides inspiration in the form of personal, communicable touchpoints? (How do you feel?)
It provides a network of other Urbbi’s and their owners that can provide help and support (What is it?)
And finally it provides the very beginning of control over your environment, albeit for now just your digital environment. (When the water is low can you tweet Anna next door to come and water it? Thanks)
How these will manifest is my on-going work at the moment so I should be able to show you the first prototype (v.1) end of next week when this project should officially finish under development at CIID.
(I am seriously considering developing the idea further after I leave Copenhagen however)
Finally, a bit more of an update on what I’ve been up to technically this week. I managed to finish Urbbi V.0.5 yesterday and hes currently sitting at the studio collecting data about light and soil moisture. He’s reporting the data to ThingSpeak.com and then I’ve written a super simple JQueryMobile page to grab the JSON data and parse it. At the moment it’s spitting out the last entry number but I need to heavily develop the interface this weekend to express what I’ve talked about above. I had a look at integrating a node.js server to collect the information (someone recently wrote a MQTT server library for node.js so could be interesting) but I doubt I have time to implement this. For now querying the data from ThingSpeak works very well. And it’s more beneficial maybe to have the data open to the public to use as they want in the future. I may plug it into the slight more well known Pachube but we’ll see. Urbbi also has data output as LED bar levels on the actual device which I am bit shifting so I need to design and implement the indicators as to reflect the web interface. (The question still remains, should I directly reflect the levels or should it’s interaction be slightly different? We’ll see.)
So that’s the plan for the weekend. On top of shooting a short film! Busy busy. So time to run I think, time waits for no man!
Last project weeknotes (10) next week!
— Read more