Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analytics #723

Open
skellock opened this issue Jul 3, 2018 · 11 comments
Open

Analytics #723

skellock opened this issue Jul 3, 2018 · 11 comments
Labels
discussion 💬 Just chatting. No action required.

Comments

@skellock
Copy link
Contributor

skellock commented Jul 3, 2018

@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 skellock added the discussion 💬 Just chatting. No action required. label Jul 3, 2018
@skellock
Copy link
Contributor Author

skellock commented Jul 3, 2018

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

@jamonholmgren
Copy link
Member

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
Copy link
Contributor Author

skellock commented Jul 9, 2018

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

@jamonholmgren
Copy link
Member

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.

reactotron-usage

@skellock
Copy link
Contributor Author

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

I like the opt-in approach.

Thx!

@rmevans9
Copy link
Collaborator

@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
Copy link
Contributor Author

whatever yall think is best

@jamonholmgren
Copy link
Member

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

@rmevans9
Copy link
Collaborator

@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
Copy link
Member

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

joshuayoes pushed a commit that referenced this issue Jan 17, 2023
joshuayoes pushed a commit that referenced this issue Jan 27, 2023
joshuayoes pushed a commit that referenced this issue Feb 1, 2023
silasjmatson pushed a commit that referenced this issue Mar 14, 2023
@markrickert
Copy link
Member

This will be closed by #1406 when it lands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion 💬 Just chatting. No action required.
Projects
None yet
Development

No branches or pull requests

4 participants