Hey @BarryCarlyon , thanks for the reply. I see you constantly on these threads and appreciate it.
A couple of things:
1: In regards to this:
This problem exists on all platforms due to browser interaction score.
I guess I should have been more clear here. I know that its the browser that causes this and that its out of Twitch’s hands. I guess my point was more that if we had a native solution then that wouldn’t be an issue.
2: I wasn’t familiar with UserVoice until you suggested it. I will definitely create an idea for both a native SDK and a mobile parameter. Is UserVoice an actually useful way to get things implemented? Or does it tend to be a blackhole of ideas? I’m speaking just based off of my experience of Apple’s version of UserVoice, which gets heavily ignored.