top | item 24153083

(no title)

ss3000 | 5 years ago

I wonder why Fortnite doesn't also make a WebAssembly version of Fortnight and deploy it on fortnite.com?

Then Apple would get jack shit from any sales there, so they can fight this battle with them while still offering access to the game for Apple users.

I'm probably missing some esoteric limitation Apple places on web-based games to cripple this use case.

discuss

m4rtink|5 years ago

AFAIK Apple prevents this by forcing every browser app to use the half broken Safari engine that does not implement many modern web APIs and standards.

ffdjjjffjj|5 years ago

I don’t know if that’s true otherwise but webgl is supported by safari on iOS.

mhh__|5 years ago

I would assume someone has tried somewhere at Epic but I think the issue is not only targeting WebGL (as opposed to VK/OpenGL/D3D) but the sheer size of the assets a game like Fortnite has.

Epic has the money to fund development to make it happen on the technical side, but currently you'd need to download so much stuff that you'd be doing the same thing as their game launcher anyway.

shaykk|5 years ago

Why doesn't everyone make a WebAssembly version of their game and host on their own servers? I'm pretty sure there are a thousand big problems with this idea.

lvturner|5 years ago

Mostly latency around WebSockets.

hjnilsson|5 years ago

Restrictions on how much data a website can store prevents this. You can't cache 4GB of game data on a website (maximum in mobile Safari is 5MB for app cache).