Analytics

[skellock]

@kemiller asked this about a month ago.... do we know how many people use Reactotron?

My answer: 🤷‍♂️

Let's find out ... but let's do it in a non-douchey way where people don't think we're stealing their information.

Opt-in would be preferable, but nobody will turn it on.

Perhaps show them exactly what the payload looks like if people are curious?

[skellock]

We can put the off switch in the upcoming #721 config file.

[jamonholmgren]

I’d love to see this info, but agree it needs to be done in a non-douchy a way as possible without making it an option nobody turns on.

Perhaps there’s a way to make a compelling case for leaving it on in the message that tells people that we are doing this. I have some ideas; I’d love to show some examples of what I’m thinking once I get a few minutes to put together a mock-up?

[skellock]

I'm all ears, as I have pretty much 0 ideas on how to do this right! haha.

[jamonholmgren]

So this isn't exactly what I was thinking, but it's an option. Let's call it Option A. I'd like to hear feedback, and will be thinking about other options as well, including not hitting them in the face with it right away. This is probably the most up front one of the options I was thinking about.

[skellock]

Ya, I’ll probably go with some like this.

I like the opt-in approach.

Thx!

[rmevans9]

@skellock have you considered if you want to build a custom little analytics server to ship this data to or would you want to use Google Analytics or something of that nature?

[skellock]

whatever yall think is best

[jamonholmgren]

I'd probably vote for a small serverless app to pump this info into.

[rmevans9]

@jamonholmgren sounds great. Given that this serverless app wouldn't technically be a part of Reactotrons offering would you think we build it as a standalone "analytics server" that we could ship analytics of multiple apps to (for ex Ignite)?

[jamonholmgren]

That's an interesting idea, @rmevans9! I like it a lot.