After posting my Screensaver Culture presentation yesterday it was blogged on Creative Applications by Greg Smith and I’ve gotten quite a few responses on Twitter. Some of the comments are on point and some are just funny.

Below is a more or less complete list. In summary, the arguments are roughly as follows:

  • “Screensavers are outdated / unnecessary.” Well, yes. But that has never meant much in terms of deciding whether a cultural phenomenom succeeds or is banished to the Wasteland of Forgotten Memes. Tamagotchis or animated GIFs, anyone? 90% of all iPhone / Android apps are unnecessary for everyday living, yet the smartphone app culture is a runaway train.
  • “Developing screensavers is currently way too hard.” I share this sentiment and suspect it to the main culprit along with its corollary: “Installing screensavers is too hard / scary / likely to mess with the rest of my computer.”
  • “It’s impossible to improve on flying toasters.” This terrifying thought is exactly why I would suggest screensavers need revisiting.

In conclusion: Between being tricky to develop and just as tricky to install and successfully use, screensavers stand no chance of recovering ground as a cultural phenomenom. Despite their close link to the app culture that is currently dominating our lives, screensavers (aka “ambient software”) will get no love.

This might not seem like such a terrible loss, but I still posit that ambient data gadgets with possible integration to web / mobile apps would’ve been a great usage scenario. There are some ways this could still happen:

  • Microsoft and Apple realize the lost potential and relaunch their screensaver frameworks complete with app stores for screensavers. (Unlikely.)
  • Google develops a screensaver mode for Chrome as part of their Chrome apps initiative and allows sales of screensavers through the Chrome app store. (Entirely possible if a little optimistic. My favorite option by far, though. Google, are you listening?)
  • In both these scenarios, new screensavers would be based on HTML5 with WebGL, allowing them to be cross-platform and based on open standards. Because you all understand that proprietary is stupid, right?

A sad footnote: I had to uninstall the brilliant Briblo screensaver after realizing it was interfering with the taskbar on Windows 7. So I’m back to the ever popular blank screen, like so much of the world population.

The Tweets

3 Comments »

There are 3 comments to "Screensaver Culture – Twitter responds". You may leave your own comment.
1. Code & form » Screensaver culture, January 17th, 2012 at 17:12

[...] 2011 (2) October 2010 (3) Meta functions Log in WordPress   Home | « Screensaver Culture .. AHO Processing Intro.. »   Screensaver culture 120116 | AHO, Processing / Java, [...]

2. Christian, January 17th, 2012 at 17:34

Funny, an ambient screensaver was in my todo list. Hopefully with Cynder shouldn’t be too hard. But definitely harder than it could be.

3. Pete Jones, January 17th, 2012 at 18:13

Screensavers might be the only reason to miss the CRT days.

What’s striking is that new ambient hardware seems primed to flourish. For instance, I find that people with internet-enabled TV’s (built-in, AppleTV, GoogleTV, Roku, etc) tend to leave them on (at parties, primarily) to stream music or show photo slideshows in the background. (The open API’s are non-existent, but there may be growing demand in this space that might encourage a platform to compete by opening.) And then there’s all those wacky LED panels showing up in see-through windows, restaurant tables, mirrors, etc. – truly integrated with the ambience…

Maybe there will be a resurgence… in a few decades?

Comment on this entry

You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="" highlight="">