Why I’m not sold on Bloapp
Sometimes I feel like I’m taking crazy pills!
I understand that apps are cool, and mobile websites don’t grab the public eye as much. But there’s one question I always try to ask myself when looking at a new technology service or product: What purpose does it serve? In the case of Bloapp, I’m not sure there’s a payoff beyond getting to say “I have an app!”. And even that statement turns out to be not entirely true.
What does a blog as app accomplish that a blog as mobile-formatted website doesn’t? 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.
If Bloapp gave you an actual installable app distributed via Apple’s app store, that real estate grab alone might be worthwhile. But it doesn’t. Instead, users must first install the Bloapp app. They then scan your blog’s QR barcode, which adds your blog to their list of blogs that they follow inside the Bloapp app. That sounds an awful lot like the process of subscribing to a blog in an RSS reader to me, or even just saving a bookmark to an app.
I’m all for playing with new products and services to see what works. I just don’t think Bloapp is one that makes sense. Apps are shiny! But libraries shouldn’t jump into them without a real use case in mind. We don’t want to turn our users off of the concept too early.