IPhone Analytics Recommendation.
1–5 of 5 posts
Re: IPhone Analytics Recommendation.
#2Re: IPhone Analytics Recommendation.
#3Its not terribly complicated, just POST'ing some data with NSURLConnection. http://colloquy.info/project/browser/trunk/Mobile/Controller... is our implementation, if you're interested. Its under a BSD license (although you'll have to write your own way of sorting through the data).
Re: IPhone Analytics Recommendation.
#4I'm assuming you've written a native app vs. a web app. (If not, my apologies - ignore any advice I give you.) While I'm ridiculously biased, I'd recommend going with Flurry Analytics. In a couple months, it'll have the superset of features from both Pinch and Flurry. The data is processed using Hadoop, and reporting updates very quickly. It's built for multiple platforms, so it'll stay with you if you decide to build for multiple phones. And the company's well-backed and doing well financially - which is an important thing to consider, because once you release a smartphone application with analytics code in it, at least some installs are out there forever, since you can't force 100% of your users to upgrade.
Of course, because I'm ridiculously biased, you probably should check out other solutions in the space as well. :)
Re: IPhone Analytics Recommendation.
#5The "events" and crash tracking functionality was not as useful as I had hoped - if I have a rare crash I'd like to see the events that lead to that crash, but that data is not linked together. I'd also like to know the phone model an OS for the device that crashed, but the OS and device data is logged separately and isn't connected to the crash reports.
Maybe the event integration will improve with the Pinch Media merger.