"We're playing with some ideas, but it turns out to be a really hard problem."
Yeah, this is definitely true. But it correctly puts the burden on the developer instead of the user. What's more, generally it makes for a more forgiving environment by which the user can interpret the data. If you say "you had a huge ecommerce day!" and it's Black Friday, the user interpreting it will be able to put that together, even if the app (initially) can't.
Part of my bias here is that this is based on our experiences building ThinkUp, which is open source, and thus we're hoping to iterate on exactly these kinds of improvements when community members find the insights to be insufficiently, well, insightful.
Yeah, this is definitely true. But it correctly puts the burden on the developer instead of the user. What's more, generally it makes for a more forgiving environment by which the user can interpret the data. If you say "you had a huge ecommerce day!" and it's Black Friday, the user interpreting it will be able to put that together, even if the app (initially) can't.
Part of my bias here is that this is based on our experiences building ThinkUp, which is open source, and thus we're hoping to iterate on exactly these kinds of improvements when community members find the insights to be insufficiently, well, insightful.