I would rather not go deeply into activation and retention numbers publicly but hundred out of our users I’ve talked to were using 3rd party chat software and despite they had in-extensions transactions they simply didn’t know about those. I consider such numbers significant to extrapolate for the whole rather yet small extension ecosystem.
One could convince streamers to use native chat if one works with up to 10 or 20 streamers but while having hundreds, thousands or dozens of thousands installs one just gotta consider this to be a default pattern to deal with. Which doesn’t make se/sl/etc best possible experience but we just gotta deal with that as being significant behaviour.
I hope it’s not a way to solve the issue of being initially notified about something happening and about the fact that you gotta go to the extension dashboard. The reason behind is that to accomplish such deep integration with 3rd parties it would require a lot of clicks from a user to integrate in order to be notified on event while at the beggining user is not quite sure if there’s any value out of extension at all. So putting barriers upfront is not a way to solve notification issue. Install, activate and do its magic. That’s any normal user behaviour.
that might be my mood speaking but I was just expressing feedback and contributing to original issue’s importance with our own experience of loosing installs despite their viewers use the extension.
thank you, Breci! more people experience the issue more likely Twitch product team would notice and take action
I would for sure prefer more straightforward way of notifying all of participants with just one command rather than supporting all of connections for multiple and possibly parallel events happening but thank you for a backup plan, Barry!