objectiv-analytics

Thanks for the detailed comments. To create the first version of the taxonomy, we looked at the 50 companies we worked with doing modeling on their existing analytics data (from GA, Adobe, Mixpanel etc) and mapped their product UI’s and data team requirements into one extensible data format. In your examples, the taxonomy would classify these as interactive user actions, with a PressEvent on a Pressable UI element. This way, models can work both on the GitHub and HN examples in one generic way, so there is no need to come up with very case-specific naming and map these once you build a model. If you still have use-cases that are not covered, the taxonomy is also extensible, which enables you to use our validation & data modeling. About replacing components: no need to do this if you don't want to, you can either: A) Swap native component

Hi! One of the creators here. Very proud to finally be able to show you what we've been working on for over a year now. Curious to hear your thoughts! Objectiv is open-source (APLv2) product analytics infrastructure. It's built around a generic but strict event taxonomy, open/common data- and infra tools (currently PG, snowplow, working on bigquery with more to come), and the analyses are done using our pandas-like, SQL speaking modeling library called Bach. As a result, we’re moving towards a vision wherein models can be shared openly, independent of product, platform[1] or data platform[2]. How? - Fully assist the dev doing the instrumentation using tools for ide support, run-time validation, ci integration. No auto capture, but very low-effort[1] instrumentation. - Scale using proven tech: a single collector writing to PG for small or