[markostamcar]

A few years back I tried getting a related Gboard bug fixed and it was really frustrating getting the report to the right people. In the end, I did not manage it and what happened was after a long time the bug was fixed, probably due to some internal testing rather than the Gboard devs seeing my report :(

"Android 11 - Gboard not triggering Enter keypress event on <textarea> in Chrome when there are suggested words in the Gboard suggestion strip"

https://issues.chromium.org/issues/40738692

The first frustration was getting push back from every place I tried reporting it - Android bug tracker, Chromium bug tracker,... and of course there is no public Gboard bug tracker, the only option is the "Send feedback" option in modern Android OS on Google devices that I'm sure gets lost somewhere. While I do understand each of the mentioned bug trackers has its rules, I had to give it a try considering there is no other way to actually write a technical bug report and get any Google developer to notice it :(

My suggestion is that each Google product/app should have a public bug tracker of some type. A place where power users and developers can reach the corresponding Google teams more easily.

[zelphirkalt]

I sometimes get this feeling from open source projects too. They require you to be very specific and provide lots of info, understandably, but it zaps energy of the reporter. And then at the end turns out all was for naught, except that you learn you should have raised the issue in another repo or bugtracker. And worst is, when projects have the audacity to tell you to sign up to yet another forum service to report it to them. Nope. No energy left for that shit, maybe someone else will raise the issue then.