Every day more and more agencies, developers, brands and product managers implement mobile analytics, and Countly is no exception. We see tremendous growth in daily installations and interest in our Countly Cloud, just becase analytics provide an unparalled opportunity to measure the performance of your application in mobile world.
In this context, Countly project has seen many contributions from talented developers, and there are signs that the open source nature has made it a reality to build your own analytics at home, in your own hands. Importance of data liberation and open access is also mentioned by our own Christian Sullivan, one of the most hardworking contributors behind Countly. According to Christian, Countly has an awesome interface and great feature set - but the main critical idea is its openness and extensibility.
You are the author of Titanium Appcelerator SDK for Countly. How did you start with Countly?
Well, I have been a long time hacker of Google Analytics but didn’t like how I am always constrained to what features they choose to implement and having to hack up my apps to work best with GA instead of fixing my analytics to work better with my mobile applications. So once I saw Countly I was hooked! When I saw it was done in Node.js and MongoDB I was sold. I immediately forked the native iOS SDK and created a module for Titanium Mobile.
What are your first impressions with Countly?
Awesome beautiful interface and great initial feature set! Still needs work but this domain has an endless potential. Making it an open source project allows of the platform to grow exponentially faster. I am a huge advocate that open source will allow technology to grow at its intend speed as apposed to how patterns and closed source software cripples the overall grow of tech.
Why did you decide to provide an SDK? Are you actively using your own SDK in your mobile apps?
Since it is open source, it allows me to make changes on the fly to meet my projects needs. The ability to host on my own server allows me to scale as needed. I use Countly in all of my personal, business and client apps even if they are not mobile apps! (Ed: Countly can track any types of apps, regardless of their being mobile in nature)
How many apps are you currently tracking?
I have 8 apps in production and another 10 or so projects in development. We love to implement Countly in all demos and even simple interactive app mock ups and show it to our customers. They love it. We like to push Countly to the limits so at times we are tracking hundreds of custom events. With some of our dev work we have experimented with using Countly as a remote error tracking console and live remote benchmarking logger.
What are the 3 things you fall in love with Countly?
In which areas do you think Countly needs improvements?
I think Countly should separate client and api server apps to different projects. I’d better see that the forced use of supervisor service is removed - since I use forever to keep my apps up with a custom http-proxy. Another thing I wish to get implemented is better upgrade system to allow for many users to always be on the newest version.
By the way, I’m working on a Create JS client API to let users use cross platform in web apps, Cordova (Phonegap) Apps and Titanium Apps with out the need for a native module to use.
Thank you, Christian for your time and contributions.