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
I'm semi-open to the idea, but there were two things that made me decide to not publish the extension when I first wrote it that we should investigate further:
My main concern is complying with the web store's Branding Guidelines and avoiding problems that can come with using "Google", "Meet", the Meet logo, etc on the Google-run store. We'll probably have to create some icons & graphics that don't include any Google trademarks.
My other worry is it'll also increase the risk of the browser extension and plugin versions drifting far out of sync, since the former will get silent auto-updates and the latter will continue running the same old version until users come back here to get the latest release. The Elgato docs mention they're working on a developer portal to help with Stream Deck Store management, which would at least keep both components relatively fresh with auto-updates. However, for now getting listed on the store seems to be a manual process after emailing support. I'm unsure if the process of releasing an update is any more automated, or if that requires contacting support as well.
The Elgato side might be easier now w/ the marketplace? I haven't been through it though. It just seems like a new thing and they may have fixed the manual process you were talking about.
That would significantly reduce the effort in consuming this. I've done some work with publishing extensions before and can help with automating that.
The text was updated successfully, but these errors were encountered: