Without Analytics, I'm blind: I can't tell which feature are popular and which aren't. I need those infos to undertand where I should focus, what are users the more interested in.
By "Privacy respected", I meant that I am not asking you for your email, your name, and what you do on the editor stays on your machine: no cloud uploads of your files.
> Without Analytics, I'm blind: I can't tell which feature are popular and which aren't.
There's plenty of alternatives to google analytics though. This sort of basic breakdown could be done with goaccess (or an awk one-liner); plausible, matomo or simple analytics would be decent options that cover most reasonable requirements.
> Without Analytics, I'm blind: I can't tell which feature are popular and which aren't. I need those infos to undertand where I should focus, what are users the more interested in.
I have a suggestion which has always served me well: Ask. Or don’t even ask, users will tell you what they want anyway. Analytics will only give you skewed information, as you are unable to distinguish the popularity of a feature is due to its usefulness, its prominence, or a general lack of clarity.
What exactly is tracked though? What information about my videos and my usage patterns are send to Google?
It would be great if you could use a self-hosted analytics platform instead! :)
And I would strongly advise not to develop based on anonymous analytics, users might tell you different desires if you ask them and use completely different workflows if added. Optimizing for web analytis metrics has ruined many projects.
With ads/analytics, Google and the site operator know you're hitting certain pages at certain times, but assuming what they wrote under "privacy respected" is true, none of your content is uploaded.
That's an important distinction to make especially for a browser based app. It's also a very low bar IMO, but one that many other companies aren't clearing anymore, like MS, Adobe, and others.
clementpiki|1 year ago
creshal|1 year ago
There's plenty of alternatives to google analytics though. This sort of basic breakdown could be done with goaccess (or an awk one-liner); plausible, matomo or simple analytics would be decent options that cover most reasonable requirements.
latexr|1 year ago
I have a suggestion which has always served me well: Ask. Or don’t even ask, users will tell you what they want anyway. Analytics will only give you skewed information, as you are unable to distinguish the popularity of a feature is due to its usefulness, its prominence, or a general lack of clarity.
notachatbot1234|1 year ago
It would be great if you could use a self-hosted analytics platform instead! :)
And I would strongly advise not to develop based on anonymous analytics, users might tell you different desires if you ask them and use completely different workflows if added. Optimizing for web analytis metrics has ruined many projects.
stefantalpalaru|1 year ago
[deleted]
smolder|1 year ago
That's an important distinction to make especially for a browser based app. It's also a very low bar IMO, but one that many other companies aren't clearing anymore, like MS, Adobe, and others.
aloisdg|1 year ago
unknown|1 year ago
[deleted]