A couple weeks ago, I reached out to the guys at Count.ly to express frustration that the SDK didn't persist events and data.

It's a big problem. If the device isn't connected for a period of time, or the server fails to respond, the SDK would drop the data off into oblivion. The SDK should be able to store the analytics offline easily, and then upload them when the connection becomes available. Now, with a little bit of Core Data work the developers at Count.ly have added event persistence to the SDK.

I was surprised that instead of spending time building the platform they were working on front end clients. You'd think the platform developer would focus on the platform.

I'm impressed that they listened, and I'm even more impressed that they responded so quickly. I hope that they are able to keep moving forward swiftly with a strong focus on their platform.

Adding persistence is great, but will this be something they struggle with frequently? Choosing product over platform? 

  • Charging $50 a month for cloud analytics that can be hosted on DigitalOcean for $5?
  • Having a web dashboard for a mobile analytics platform that can't be viewed on a mobile device?
  • Spreading themselves thin on countless platform SDKs rather than knocking a select few out of the park?

I am a big fan of what Count.ly has, but I'm afraid I've been attaching myself to a ride that's veering off the road.