search

brandon-patterson / chemist

A virtual lab assistant
MIT License
0 stars 0 forks source link

Consider support for usage metrics #10

Open brandon-patterson opened 5 years ago

brandon-patterson commented 5 years ago

I'm guessing that as a rule, we want to be as minimally invasive as possible, so no PII collection or anything. We could pretty reasonably want to track how often the app's used, the popularity of different modules, or even commonly used formulas to help with ~autocomplete suggestions.

At minimum, this would force us to stand up a server somewhere to store the collected info. Ideally, we'd start with some simple stats collection (one way communication), and optionally evolve into more complexity from there.

zspatter commented 5 years ago

I'd definitely prefer to keep any data collection to a minimum, but I certainly think we should collect some usage metrics. I figure usage frequency and retention rate could be useful metrics to collect.

Additionally, we may want to consider crash logs. We could potentially transmit logs automatically, or we could just store the logs locally and allow the user to control what is shared.