I’ve recently been provoked to take a serious look at Kaplak again. I thought I would drop a few lines in this place to announce that I’m back to work on Kaplak – if only in a tiny slice of my time – but no less ambitiously.
The truth is I’ve never really left. For various reasons, it made a lot of sense to close down the company Kaplak and focus on other things, but I’ve never quite left the ideas we worked with in Kaplak, and I believe the world still needs what we had coming for it. In the meantime there’s not much else to do but figure out ways to build upon the experience we had then.
So in the back of my head, this is what I have been doing. I am right now on three months of parental leave from work – which among other things, have lent me some long-missed time to think about the meaning of my life and the connected world. When teaching one does actually do a lot of thinking – but it’s mostly about teaching and planning classes and lessons, and not much else. Since August 2009 I’ve been teaching history and media full time at Aabenraa Statsskole – and since the summer of 2007 I’ve also had two kids (one now aged 4 and one nearly 9 months), which in sum means that my life is totally different today than what it was when I first started Kaplak.
So what did provoke me to take yet another long arduous journey to the far far away land of the slim ends of the long tail? (Plural because they come in large numbers!) Among other things, I’ve come across a couple of online phenomena which deserves a few words in this space.
Earlier this year Google launched Google+ which I have embraced and played with – at times enthusiastically, at others somewhat reluctantly. It’s like Friendfeed has come back – but different and with a whole new feature-set, which combines the best of what Twitter and Facebook have to offer. But it’s still a proprietary monster, where Google (among many other things) gets to decide what their users are ‘allowed to call themselves’, simply because while Google+ empowers users to share their stuff in ever more flexible ways, the network is still owned by Google and this ownership is never in question. Nevertheless, the ease of sharing stuff on Google+ has made me into a regular poster.
Google has been quick to add hashtags to it’s service, and I’ve now begun to add hashtags to my stuff, which makes it easy to find #copyfight stuff and posts on #landvaluetax, as well as all those #thingsthatmakeyouseetheworldjustalittlebitdifferently. It often has stricken me though, that I ought not to use Google to make what is in essence niche micro sites much like the ones we were developing with Kaplak Stream. Instead, I’d like to share stuff using WordPress as a platform as we did in Kaplak, and only use Google+ as a secondary channel.
If this then that
Just recently I stumbled (via my Google+ network) across an online service which goes by the name If This Then That, which stirred up a lot of thoughts about Kaplak in the back of my head. Occasionally I come across something which contributes a piece to this ongoing puzzle. Ifttt, I believe, is such a piece. Now these stirred-up thoughts have fallen into place again, and although a lot of the ideas we worked with in Kaplak remains (making a sound business out of less-than-popular (“long tail”) products – and transforming work life and the universe as we know it in the process), some have landed in new places.
My instinct tells me that Ifttt (and similar services) paves the way for the future of the internet. Ifttt truly empowers users because it puts users in charge of the what, when and where of their online activities – not the services they use. It widens a door already opened by the APIs of online services, which adds a new parameter to the equation. Companies such as Facebook, Google and Twitter will increasingly have to compete on how well they serve the needs of users to bring their data where they need them to go (and in that process make more data available flexibly and cater to the needs of services such as Ifttt) – and not where those companies would like them to go.
Now, what does this entail for Kaplak?
We had two working strategies in Kaplak – one was widgets, the other was Kaplak Stream. Both aimed at the same target : selling niche products in rich niche contexts, which would easily be found by their niche customers, and in doing this connecting seller with buyer. The middleman – the “skipper” making the connection, would in turn earn kaplak, a percentage of the product value given by the seller.
Now, it’s a top priority to concentrate efforts on making Kaplak economically feasible. This means, that with the greater ease and the less hazzle we can create these connections, the better, as the turnout (kaplak) from each sale must be expected to be very small. Therefore, we will focus on the “stream”-approach, but with a few decisive changes to make sure we must do as little “clean up” and maintenance as possible – more on this at a later time and place.
This aligns well with what my life looks like right now. Among other things, I can not dedicate as large a portion of my time as I would like to build up Kaplak, at least at this point in my life. I will keep teaching history and media, and continue to devote a large part of my spare time to my precious family.
But what I do have, are those spare minutes during the day, which cannot be used for much else. I will continue to cruise the web and share stuff, using my phone, my laptop and my PC. But increasingly I will ‘share with Kaplak’ i.e. develop a sharing platform and work out posting routines accordingly, using Kaplak – rather than use Google+ just because I am too lazy to use my own platform. Google+ has other excellent possibilities and uses – but should never be the end destination for shared stuff, no less so than Facebook or Friendfeed should.
Using services such as Ifttt we can easily distribute items to their proper place, and since I’ve last worked seriously with WordPress, useful and valuable plugins such as FeedWordPress has only improved – and will assist to help create the niche sites, which in turn will deliver the helpful contexts for future Kaplak products.
What is important though, is that I sense that it is in fact possible – right now, using the tools that we have right now – to build a site architecture, without the need for a lot of coding, which will (if very slowly, to begin with) help accomplish the beginnings of what we set out to do with Kaplak.