Tuesday, October 31

Extending the swipr documentation

As you may have noticed, documentation on swipr is quite sparse. It is difficult to find the time to create a very elaborate set of documentation, which is why I have set up the documentation in a wiki. It would be great if there are more people that would like to add to, and enhance the current set of documentation.

If you would like to contribute, please send me an email (info at swipr dot com). You'll need to be registered on swipr.com (which you probably are already). I will then change your role in swipr.com, so you have sufficient rights to modify and add content in the documentation area. Thanks in advance for your contributions!

swipr visitors & downloads

This picture is taken from google analytics, that is keeping track of visitors to swipr.com. As you can see there are two peaks. The first (very small) one happened directly after the release of swipr in Berlin, during the weekend of Sep 30th - Oct 1st. A maximum of 46 visitors and 579 pageviews on one day was the result of this.

On Wednesday, Oct 25th, I sent a message to two IA mailing lists (IxDA Discuss and SIGIA-l). This peak was a bit more impressive, resulting in 261 visitors and almost 3000 pageviews in one day. Visitors then sharply fall again, but I'm hoping that there will be a bit of publicity within the blogosphere after people start using swipr in the next couple of weeks.

The total number of swipr downloads is now up to 92. I'm hoping at least soe of these people will actually start using swipr. I've been helping out a couple of people here in The Netherlands with setting up and starting to use it, which might be a bit more tricky for people further away. Still, it should not be an excuse not to use swipr, as there is a support forum on the swipr site which I am constantly monitoring.


Monday, October 30

swipr goes blogging

Welcome to the swipr blog! After releasing swipr last month in Berlin, during the Euro IA, I was wondering how to keep people updated on new developments. It seems that a blog might be the best way to do so. The plan is to give regular updates on further development of swipr. Also, I might give some hints and tips for common problems, and it would be great if swipr users would allow me to show different applications of swipr in real life.