Countly Mobile Analytics | Blog

Sep 17

Venturebeat recognizes Countly, surveys mobile analytics users

Venturebeat, a company well known for being a leading source about news and perspective on technology innovation, are surveying mobile analytics users

Countly is also recognized among top mobile analytics vendors in this survey, and we want to help them establish their goals. So why not spend some time and answer their questions - which won’t take more than 10 minutes of time, and help Venturebeat establish their goals?

Here’s a link to the survey - thank you for participating!

Sep 08

Updated Countly Windows Phone SDK for WP analytics

image

We’re happy to announce that we rewrote Windows Phone SDK from scratch and committed to Github. Windows Phone Analytics SDK is available for everyone, with an open source (MIT) license, so you can checkout and use in your apps. This version is on-par with iOS and Android analytics SDKs, and has the ability to store data when network is down. 

There’s also a Windows Phone mobile analytics application, when launched, can send basic events, or events with sum and segmentation (screenshot below):

image

We hope you like Countly Windows Phone SDK. Do not hesitate to contribute to Countly by sending pull requests, submitting bugs or simply helping with documentation. 

— Countly Team

Aug 31

Introducing new Cloud pricing model

We have been running Countly business for roughly 2 years now, and in the last 3 months, we have seen a massive increase in signups, subscriptions and downloads. Quality of our SDKs have increased, Countly is used by several Fortune 500 companies and we are more than thrilled to be a part of this ecosystem. 

It’s been 2 years since our last pricing introduction and we haven’t increased our pricing, despite the big difference among other players in the market (we always have been on the low-end). Lately, almost all players have gone through a price restructuring – mostly due to increasing complexity of underlying platform, servers and SDKs. We are also experiencing the same - an increase in cost of data, servers  and maintainance, and our operational costs are getting higher, and we have the desire to continue to offer a quality service for you.

Therefore effective from October 1st, Cloud Edition pricing will increase, starting from 30%. There’s no change in number of sessions and all prices are monthly.

Here’s a list of new prices:

Here’s a definitive table that shows our latest pricing, including number of session and event limits:

image

As usual, one session means one launch of an application, regardless of data points it sends to the server. Usually, in one session, we see 5-15 data points sent to server. This number can go high, up to 80 in some cases (e.g radio, video apps that retain user more than, say, a weather application). In any case, we strongly suggest you compare our pricing with other players in the ecosystem and witness the huge difference still after pricing change.

One event is a “custom event” generated on the device. Unlike other analytics platforms, sessions and events are calculated independently and do not affect each other. When you hit one limit, you’re asked to upgrade to next Plan. Note that stored data has now a retention limit, starting from 2 months to 6 months for bigger plans. If you need more retention in your plans, Countly Enteprise Edition can store your data for longer periods. 

You may immediately ask – “how about my startup discount?”. It’s still there, still the same (20%) for Professional Plan. Therefore startups will pay a flat USD100 for this Plan as soon as they provide us a legal document stating that they are under 1 year old or have less than 10 employees onboard.

How about other editions?

Countly Community Edition is always here to live – we love and use open source, and we are dedicated to give back to community.  Countly server and SDK has been supported by more than 30 developers, and it’s you who make this product a big success in mobile world. 

Countly Enterprise Edition is for those who want to have Countly Mobile Analytics Platform self-hosted, and also enjoy support and several features that  are not available to Community Edition, available to Business plans in Cloud Edition but readily available with Enterprise Edition: Drills, Funnels, real-time dashboard for online users, User Retention and more. If you want to get more information about Enterprise Edition, we have a very good news: we are offering a price reduction until 31st of December, 2014 for companies willing to migrate from Cloud Edition to Enterprise Edition.  Contact us for more information.

New pricing model will go live starting from 1st of October, and will affect existing and new users. If you have any queries about our new prices, please do not hesitate to contact us. 

We’d like to thank you for your compliments and valuable ideas during your tests and production use of Countly. We are continuing to demonstrate our ability to solve your analytics problems and provide a robust, real-time platform with a focus on end user data privacy.

Cheers!

— Countly Team

Aug 29

New Community release: Countly v14.08

Countly is world’s #1 open source, enterprise mobile analytics platform. We are proud to release the latest and greatest Countly v14.08, which is a follow-up to Countly v13.11. In this release, we focused on making Countly easier and less buggy to use.

What’s new?


Our new license: AGPLv3

We thought using a standards compliant license, rather than a hand-crafted one would be more appealing to end developers. Starting from this release, we modified Countly Community Edition license to AGPL

We highly recommend that you upgrade your server to new Countly today to benefit from many improvements in this release.

Need a self-hosted, supported solution?

Countly Enterprise Edition is a self-hosted, customizable, full-featured, white-labeled mobile analytics platform including Countly server, more than 10 SDKs, client API libraries, extensive documentation with full support from same team who developed Countly. Enterprise Edition is used by Fortune 500 companies on mission critical servers. For more information about Enterprise Editionplease contact us.

Links:

Aug 14

Guest post: How I give back to open source community by improving Android SDK

imageEditor’s note: Guest blogger Jason Boehle is Android developer in Coupons, Inc.

He uses open source in his work and occasionally contributes to open source projects. 

It’s been more than 5 years since I became the first mobile developer at Coupons.com, after they acquired my app Grocery iQ.  Since then, we’ve built a great mobile engineering team and used many open source projects in our apps.  Until recently though, we used a homegrown analytics solution, mostly due to data privacy concerns with hosted analytics providers.  Around the start of 2014, we discovered Countly. With it being open source and able to be self-hosted, we found a possible successor to our internal analytics tool.  Fast forward to the end of March, we made our Android Coupons.com app the first Countly test subject and rolled it out to production.  For the initial roll out, we did not use custom events; those were added over the next few months as we integrated Countly into the rest of our mobile apps and expanded to over 50 custom events. We love the slick Countly UI, real-time dashboard, and easy SDK integration

image

Open source software often makes our lives as developers much easier.  When you consider how much development time can be saved by making use of ready-made open source components, it should be easy to justify spending some time giving back to the community.  However, due to the frantic pace at which our industry moves, that is often not the case.  My team has spent a lot of time over the past two years optimizing our efficiency, so recently we have been keeping an eye out for an opportunity to give back to the open source community.

Given our newfound reliance on Countly, I decided to take a look at their open source SDKs.  I checked out the latest Countly Android SDK from Github and started exploring.  After taking the time to understand the code, I saw several opportunities for improvement.  Like most code bases, the SDK was in need of comprehensive unit tests, documentation, and more robust error handling.  

image

I spent some time in late June working to improve the Countly Android SDK.  First I broke out the classes contained in Countly.java to a single class per source file to make it easier to comprehend and maintain.  In parallel to improving the existing code and fixing a few bugs discovered along the way, I wrote unit tests for every class in the SDK.  I also added JavaDoc and code comments to help out new SDK users & future open source contributors.  After committing all of these improvements to my Github fork, I submitted some tickets to the master Countly Android SDK project to cover the improvements I had made. 

Later the Countly team contacted me to go over the tickets I had filed.  They were excited to learn about the improvements I had made to the Android SDK.  Since so many changes had been made to the code, we agreed that I didn’t need to submit a bunch of pull requests.  Instead, they would review and manually incorporate my changes.  After merging my work into a new branch with some minor changes, I updated a few unit tests and fixed a bug (that the unit tests caught!), and now the Countly team is preparing to release an official update to the SDK.

The major improvements made in the new Android SDK release are:

 - Comprehensive unit tests & documentation

 - More robust error handling and parameter checking

 - Ability to supply custom device identifier instead of using OpenUDID

 - Countly API is now thread safe

I am very excited about the improvements in this release and I can’t wait for it to be available to all Countly Android SDK users.

I hope that my experience encourages others to contribute to open source.  The Countly team was easy to work with, accepting of my changes, and appreciative of my work.  I’d like to give special thanks to Artem Salpagarov for reviewing and merging my code. I enjoyed working on the SDK and look forward to further collaboration with the Countly team.  For those developers out there making use of open source, don’t be afraid to jump in head first and give back to the community!