154 karma · joined October 16, 2013
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!
What use cases do you have in mind?
It will be free for a while and later a per subscription price is what sounds good for us.
We are the makers of Hooks App (gethooksapp.com), and for a long time we have been creating content on notifications for hundreds of thousands of users. Now we are opening our data so developers can do whatever they want with the it.
We are really excited to hear what do you can do with the API.
Feel free to ask anything!
About read rates, we are having a 50-60% open rate on the content we are pushing to the users, but we are connecting our newsletter directly to Messenger using revoice, without modifying titles or anything. I guess that if we tailor the messages, we will get the promised 80%.
We also have an API (private beta for now) for developers to use the content and/or create alerts for our mobile app
So the first product we build with our API is this one, looking forward to find out if it's something useful. What do you think?
Thanks!