Stadium Browser 1.2
Back in business
I’m now happy to report that Stadium is officially back in the App Store! Introducing Stadium 1.2.
I had to remove my hooks between the GameController framework and WebKit. Apple said that I was “Using public APIs in a manner not prescribed by Apple”. This is unfortunate, but not a complete loss because…
Finally, I (think I) fixed the tip jar.
How do I use Stadia with Stadium 1.2?
Set your Primary URL field to
Set your Custom User Agent String to
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36
Set your Override Custom User Agent String to
Mozilla/5.0 (iPhone; CPU iPhone OS 14_0 like Mac OS X) AppleWebKit/605.1.15
Disable “Require Full Screen Video” if you want to see Stadia’s menu overlays. I kept this as an option because forcing the video full screen may be better for smaller devices (hello there, iPhone 12 mini users).
Before you can properly use Stadia, you’ll need to authenticate to Google. In the “…” menu, select “Authenticate Without Custom User Agent”, and when prompted, visit
Once you’ve logged in and are at your account page, tap “Done”. You should be good to go!
What Controllers Work?
The Stadia controller will almost assuredly work, presuming that your device is on the same WiFi network as your controller.
Bluetooth controllers might work. Using the “Override User Agent” I mentioned, Stadia should properly support the Gamepad API, but iOS doesn’t always seem to pass that through. Please send me your feedback on how this works for you! I have gotten it to work more than once, but definitely not every time I tried.
Keyboards might also work, but I don’t expect it to be a great experience.
Thank you to everyone who has been supportive of this project. I’ve received many kind words on Reddit, Discord, and from many in the press. This was a fun little project I built in a weekend on a whim, and I’m glad you all liked it.