You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2021. It is now read-only.
Look into options for collecting analytics for the project (both Admin and Client)
Would be optional (see #189 for opting in).
Needs to track the follow
Installed version
Distribution version/type
Number of hotspot user accounts
Number of active hotspot user accounts (active last X days)
Maybe the number of actual logins
If we had "website" analytics then tracking the admin pages used, how often, etc would be useful
Enabled/disabled features?
Usage of features?
Any analytics needs to consider:
GDPR
Hosting costs
Privacy
Marketing of data (making sure the analytics provider doesn't use it for marketing)
Why??
It's hard to understand what features are used, needed etc. If time is being spent supporting an LTS version from 4 years ago, but no one is using it, then it's wasted time. If the average install size is 300 users, then we don't need to optimise for 10,000 users and can afford to show more rich information on screens. etc
The text was updated successfully, but these errors were encountered:
Look into options for collecting analytics for the project (both Admin and Client)
Would be optional (see #189 for opting in).
Needs to track the follow
Any analytics needs to consider:
Why??
It's hard to understand what features are used, needed etc. If time is being spent supporting an LTS version from 4 years ago, but no one is using it, then it's wasted time. If the average install size is 300 users, then we don't need to optimise for 10,000 users and can afford to show more rich information on screens. etc
The text was updated successfully, but these errors were encountered: