krammer
Joined 13 years ago
Joined 13 years ago
I’m also a heavy user of Amplitude and I see how June solves many of my common use cases in a more usable way.
Probably for me it doesn’t make a huge difference, and I still do deep analysis at my dwh or amplitude. But for the rest of the org, that is less data oriented, I found that June increases their data driven mindset just by making it easier to understand and use.
That’s what good UX is for.
It's a different approach than Metaplane, which we are actually evaluating for our dwh and backends monitoring. Trackingplan is more about creating trust on the data collection side of the problem.
Drop me a line, josele (at) trackingplan (dot) com if you want to know more!
Ofc i’m being pedantic here and things are always more complex but... I have one question. How do you say in a safe way: We need more time because I FEEL that maybe, there is a 2$ solution for this problem.
https://www.producthunt.com/posts/hooks-data
Feel free to comment there too.
For the data api we plan to stay free for a while and then charge new users with a low per subscrition fee to indie devs and have a plan for big data consumers.
Offtopic: how much would you have payed for the Hooks app? Just from the top of your mind.
Actually, we want to add what our users/clients want. No region in mind.
As a side note, its quite easy to create alerts about "new item in the data set" but it get worse if you have to understand the use case, as, e.g. sending all the "garbage collection schedule items" its different than sending "garbage collection new items in that street of Geneva". Hopefully the CKAN spec will allow us to let the users to set a query over the data, so we will be able to push them only when the new data matches that query.
Thanks again!