…or something like that.

It’s all gone a bit crazy since the Twettle post got picked up by Wired magazine, suddenly there were hordes of journalists and bloggers asking for images of the kettle, some even wanted pictures of me and Ben.

Sadly no one wanted to send a photographer to Sydney to snap me so Ben got all the glory in last weeks Metro (above, click to enlarge), he’s even been interviewed on BBC Radio 1.

Following the conversations on Twitter, it looks like there’s over 1000  mentions and it’s showing as 46,000 results on Google, up from oooh about 50. It’s actually gone as far as this (translation anyone?):

The coverage has brought many questions to the surface – Why do so many people like it?  Why do so many people hate it? How has every publication and blogger managed to spell my name wrong? And who the hell just purchased Twettle.com, .net and .co.uk?

The positive feedback mostly came from tech blogs and Twitter. As expected, there is clearly a demand for this from Twitter users and several retailers have contacted me asking when they can start selling it. The most consistent feedback was about the design (good work Ben!). The best writes ups are:

It turns out, the reason people hated it so much was because they didn’t bother to read the original post to understand the rationale. Preferring comments like:

“Not sure if this appliance could attract a lot of subscribers to its Twitter feed”

You don’t say! Well lucky that only the people who own the kettle need to follow it on Twitter, seeing as they will be the ones making tea. Jesus.

One things for sure if you don’t get why and how people use Twitter then you’ll never understand the appeal of this idea. Don’t even try. This wasn’t created for you in mind. But there is another part to this project which you should try and understand, the software.

Let me say this, this project isn’t about a kettle, hell it’s not even about Twitter. Those aren’t important. What this is all about is making a scalable Wi-Fi module with API functionality that is flexible enough to be put into anything.

The tech on this module can talk to any social media site, database or service. It can use SMS, MMS, Email and even trigger phone calls. This is an enabler for any developer to be creative with hardware and make cool stuff off the back of information coming out of the kettle or whatever device is connected.

What this means for manufacturers who place this in their products is that they can create APP STORES for appliances and electronics. Yep that’s right, online and mobile widgets and applications, based around white goods, appliances, even electricity and gas meters. Data mining is also possible so the manufacturers can get details stats on how their products are being used.

Ultimately this gives the tools for devs to run wild and create apps that will sell more of the manufacturers products. Plus this is the part that scales, it’s much more likely for our module to be in more homes than the Twettle.

Admittedly this wouldn’t be the easiest thing to explain to your average Metro reader but should be noted as the part with the biggest potential.

I guess it’s hard for people to think creativity about this but here’s some examples off the top of my head (it’s 2am so this is just a brain dump):

Tea Roulette – (Nothing to do with Chat Roulette and penises) Once the kettle has boiled a service/app could SMS or Email designated workers in your office at random to make the tea.

Energy Tracker– The data from appliances can automatically be sent into a carbon footprint/energy tracking services, allowing users to see their impact on the environment without manually entering your usage.

Data Mining – Services and manufactuers can pull information from Twettles (or any appliance) around the country to produce stats, analytics and graphs about what parts of the country drink the most tea. This information can extracted and mashed-up with Google Maps and social networks. Check out services like TwitterVision for some brain food.

So what’s next? Well due to the publicity we’ve got the funding we needed to get this project underway. More news soon.