If I create a OSS app with analytics to detect & log crashes with feature use, is it a bad practice?

If I create a OSS app with analytics to detect & log crashes with feature use, is it a bad practice? I think analytics is really helpful in finding which features are worth developing & which bugs needs to be solved first. Edit… Things Collected

  • IP Address for use ping (for country)
  • All crashes with IP
  • Feature use with IP Crashes are store for upto 6 months to solve bug but rest are collected and delete after 3 months

It is opt-out but user are informed about it during first / install time. To disable analytics Settings --> Privacy

I want to know right way to introduce analytics in OSS

thejevans,
@thejevans@lemmy.ml avatar

I will not use software that has analytics that I have to opt out of if there is an alternative that has analytics off by default with the ability to opt-in.

The psychology surrounding opt-out vs opt-in is very well understood, and choosing to include analytics with an opt-out structure is taking advantage of people to make development potentially easier. Not cool.

pineapplelover,

For foss apps, I mostly allow analytics to track to help the dev out more. Complete 180 for any big tech since whenever they ask for it, they sell that information to the highest bidder.

Jimbabwe,

All depends on what you collect, how it’s stored, how transparent you are about it, and how easy it is to opt out of. It can definitely be done well.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • opensource@lemmy.ml
  • localhost
  • All magazines
    •
    Loading…
    Loading the web debug toolbar…
    Attempt #