My Photo

About Me

  • Hello you. I'm a 38-year old MSc student, studying Advanced Computer Science at Sussex University. I'm especially interested in Internet and mobile software, sensors and pervasive computing, user interfaces, and the process of developing great software.

    Before that I spent 11 years running Future Platforms, a software company I co-founded which makes lovely things for mobile phones, and which I sold in 2011.

    I read a lot, write here, and practice Aikido and airsoft. I live in Brighton, a seaside town on the south coast of the UK, with two cats and a clown.


Stalk Me

  • Email me:
    twhume at gmail dot com
Blog powered by Typepad

« Modding mobile apps | Main | Making Sense of Sensors, Future of Mobile 2011 »

September 30, 2011



Hi Tom,

Do you have idea, how much your productivity has increased with this approach? How many hours did your team hav spent developing the Kirin?

Tom Hume


We used this approach for the Android and Qt ports of the Glastonbury 2011 app. The Android version came second and took half the time of Qt, we think much of this was down to our use of Kirin.

Modelling we did up-front indicated that using Kirin on a 3-platform project would save 30% of effort overall, and this feels about right to us.

I don't have a separate estimate for how long Kirin took to develop I'm afraid - we validated the approach in 3-4 days of experimentation and prototyping, but there's a journey between having a prototype and production quality code.

The comments to this entry are closed.