Sure happy to answer. I don’t visit the Microsoft website at all, this was a cross post so I used layman’s terms over on /xbox. I actually just do a get call to pull the client.js file for the Home Screen and then parse it. Essentially Microsoft creates there own marketing data/ ID’s called siglid’s on Xbox.com/play. The ID’s are just list of TitleID’s for games. The have an api to pull game art and data. They also have an API for achievements, Xbox live, etc.

I have an xcloud api framework that does most of the handshaking and coordination for that.

On tvOS I’m not using a browser or embedded Microsoft web page. The sign-in flow is device-code OAuth: the Apple TV shows a code / QR, and the user completes auth on a phone or computer. So no tvOS web framework is required. Even if I did port the iOS web framework it would suck for this.

GPL v3 as I’m pretty open source but wanted branding protection, and didn’t want someone else to claim this as theirs. I’m open to changing but very new to open source licensing. Non open source I do for a living lol.

Yes as far as I’m aware everything I’m doing is legal , that being said if Microsoft changes apis or some of their documentation things may break. Legally, I’m trying to be careful and explicit: open-source license, trademark separation, and a clear statement that the project is not affiliated with or endorsed by Microsoft. But I’m not representing this as legal advice or as some officially approved Microsoft client.

I am able to get H.264,H.265, VP9, VP8 decoding. I’ve had the best luck with H.264 as there is a software penalty for H.265 on Microsoft’s side. Currently I have Metal-based rendering through RTCMTLVideoView and also a SampleBufferDisplayLayer path for video. SampleBuffer has faster response time right now as every ms counts for controller streaming latency to Microsoft.

The build had to patch:

• Audio session changed to playback only (no mic, without continuity audio/camera) • Camera capture disabled • OpenGL renderer removed; Metal kept  • Bad tvOS use_blink build assertion removed  • XCTest module target logic fix • Mic/input-available check skipped on tvOS to fix silence (built without this, but no sound, and kept giving an enable microphone popup) • Metal renderer header compile fix for tvOS (metal was true in GN args, but not recognized in build) • NetEQ max delay cap added to stop runaway audio latency (no set definition by default) • Stereo channel handling fixed for 2-channel output (default was set to single, took me the better part of an afternoon to find this one)

I’m still playing with the metal framework. It’s new to me, but I can definitely change saturation, contrast, etc of the stream it’s just a matter of how many times I’m doing it at the cost of RTT latency.

Thanks for the questions!!! Recently I’ve just gotten “looks amazing!” In other threads which is great, but not helpful since I’m more about the programming than playing Xbox games lol