Well, this was stupidly easy to integrate into a web-app, but my first (and only) session has consistently been grouped into the 30-60 minute session length bucket, from the moment the session was born (first event logged) to ten minutes later. (The user event stream for the individual user shows the correct session length though.) This would make me wary of the rest of the data. Not to mention that all of the more i…
What questions are you trying to answer about your web-app? While I think reports like individual user streams are neat, I find they're not very good at diagnosing a product and driving growth. One of the best charts for doing that is a simple cohort analysis / retention chart. If you've been storing historical data about your users in your database or in a log file, one thing you could try is importing historical da…
I was only referencing the fact that the individual user data appeared to be correct in one view, even though the session length distribution chart was way-off. Had it been off for all users, it would be a big problem, but only affects the first session (See my edit above).
I agree cohort analysis is useful, but not particularly difficult to capture and chart on the server side for web apps, or mobile apps with a server back-end. For SPAs or hybrid or mobile apps you need a facility to capture client side events, which is where something like Amplitude really adds value.
It's one less thing to build or run, but if it's hamstrung by limited reporting, free isn't really free - you have to pay to unlock the value of that event stream.