Backend Versus Frontend

We are a data company. That’s to say, what we sell is data which is used for reputation management and social media analysis. But it’s the technology that mines and creates the data that we pour most of our blood, sweat and tears into. That’s to say we are a bunch of geeky guys (apart from Katja!) who build software.

One of the difficult choices we face – one that I face from customer requests, our investors and my inner Magnus Magnusson, is where to best direct and deploy our fabulous, but finite development team? Do we put more emphasis on developing a user-friendly, fast, beautiful, full of wow-factor, no-training-required front end or a robust, scalable, fast, redundant, far-reaching backend?
The answer in the past has been, 8 out of 10 times, the backend. We are after all, a data company and it’s the backend that finds, organises and analyses the data.
But that has meant that our front end has been rather restrictive which can be a pain for our users as well as we ourselves using the system. No longer! We have pushed the weights along the scale a bit towards the frontend.

Not quite balanced as this cute little diagram suggests, but on the way.
So by the End of November – oh my – what UI delights will we have in store for the unknowing world? Some maybe!

signed: your rebalanced buddy