Discussion: Track usage. Will help developers decide which fixes and features to work on

[subu28]

I have wanted to keep the app very lightweight and collect no data unless I needed to. Considering that developers other than me might want to work on this project I think they deserve to know if their contributions have as much impact as they like.

The data points I am comfortable collecting

1. everytime an activity ends on strava
   a) duration - helps understand how much the app is used and discard 10s activities etc.
   b) a sample of notification text - helps understand what activities users are engaged in. (like cycling, running). This helps tweak the app for these activities
   c) device id or similar. To help understand number of users

I do not know where these details can be stored yet. I might setup a s3 bucket with access logging and a tiny file. See pixel tracking

[koenschauwaert]

As the new maintainer of this project (hi to you all!) I would like to say that I normally - with all my publically available projects - do not collect any data. None. Zero. But it might be a good idea to track basic information, just to know how to deal with issues, etc. - maybe I'll go with a 'submit issue' button somewhere and only collect this data on tapping that button, together with a small description about the user and how this issue could be reproduced.
These details can be easily stored for free in a Firebase environment or send by email whenever the button has been tapped.

I think we - @subu28 and I - should stay in contact.