Appreciate the memes! Sorry for the delayed response to this thread.
What I’ve realized after reviewing this in more detail is that folks have been using the player.twitch.tv URL as the value passed to WebViews. This is understandable, it’s basically doing the same thing as the iframe code we provide in the documentation for the web. This use of the URL was not intended or suggested in the documentation, but on the other hand, nor was it discouraged.
That said, the parent parameter will continue to be required for player.twitch.tv URLs and there is no value that will allow mobile applications to use these URLs as the value for a WebView directly.
Since we currently do not have a native solution (e.g. embed SDK), we suggest the following means to embed Twitch into your mobile applications. Create a static or dynamic webpage that embeds the Twitch content you would like to include on mobile and add the parent parameter with that domain. Then use the URL of that webpage with any relevant query parameters if dynamically generated for your WebView (e.g. video ID).
While not the most elegant solution as it requires traffic to your own domain, it will add embedded content to your application in the short-term. Should there be any long-term updates to Twitch embed products to remove this need, we’ll follow up on this thread and/or make sure to post in the announcements section.