There’s been a lot of interesting chatter on the interwebs the past couple of days about a new application for the iPhone that enables you to create an app for your website. Seeing as Ned has already provided an outline of what it does, I won’t writing something detailing the ins and outs. However, if you are intrigued to know more, Ned summarises it as follows (it is a handy post if you do want to give it a whirl):
The way Bloapp works is that you download the Bloapp app, and then subscribe to blogs within it that have been ‘apped’. (That’s not a real word, I just invented it; I mean registered with bloapp, basically). A bit like the Stitcher radio app works. So, you can download the Bloapp app from iTunes here, and then you can subscribe to this blog either by searching for thewikiman or, more excitingly, scanning this QR code within the app itself! (By the way, if you scan this QR code outside of the app itself, it just takes you to the normal mobile version of this blog).
As someone who plays around with a lot of web tools for Voices for the Library (and someone who is keen to encourage the whole ‘go on, give it a try’ ethos), I always have a bit of interest in the latest developments and try to find ways to use them to the campaign’s advantage, so naturally I was intrigued.
However, whilst I think this is an interesting tool, I’m not sure it really adds anything. Admittedly, I do use a variety of website type apps on my iPhone (the BBC and Guardian apps to name two) and whilst they are quite good, they are not really satisfactory for seeking out news stories. The free version of the Guardian app doesn’t allow search which is a real pain in the backside (guess I should upgrade really!) and you can’t even search the BBC app whatsoever (I really don’t like the BBC app, it could be so much better). And that’s before we get into the whole closed web nature of apps *shiver* (although I guess this issue isn’t really relevant to this particular development to be fair). Perhaps there is a search functionality on the app so I guess these are kinda moot points. But, in general, whilst I sometimes use apps as my first point of call, I usually use the browser to poke around (old skool).
That said, I’m not sure of the other advantages. I’ve bookmarked my blog on my phone so I can access it quickly and easily. The mobile version of my blog is also in-keeping with the style of my website so I don’t feel I am missing out on anything there either:
I can also share blog posts on Twitter/Facebook etc from the site so that’s not really an issue either (but then I think most mobile sites allow that don’t they??). I know the pointed has been made about the decline in RSS, so I guess this is something where it may have some strengths. But, well, I am in the unconvinced camp…
This does not mean, however, that I am against libraries making use of apps, quite the opposite (and as I have said before I am all for experimentation – I work on a ‘give it a try if it doesn’t work learn from it’ perspective). In fact, I am in the process of putting together an event which touches on how apps can be used by libraries (more on that at a later date when things are finalised). For me, apps should take full advantage of a smartphones capabilities. As Chad at Hidden Peanuts points out:
Apps only make sense when they provide something above and beyond what a webapp can do. Do you need to use a device’s camera or accelerometer? Do you need offline access? Then an app is your thing. A blog doesn’t benefit from any of those doodads.
That quote is worth including alone for the use of the word ‘doodads’.
I will definitely keep an eye on developments and, should it emerge that there is something I have overlooked or there are some interesting developments, I may well give it a try and Bloapp the Voices website. Until then, much as it pains me to say it, the jury is out.