The future of my games on Apple and what this means for art games

Re:The future of my games on Apple and what this means for a... by ChrisAntaki on Monday November 11, 2019 @12:10PM (#21506528)

Last year I was building web games* with Phaser. To better support iOS, I just changed the renderer to `canvas` when an iOS user agent was detected. In the end, the games worked pretty well on iOS devices.

*Games I worked on: https://livegame.show/play/ride_v3 | https://livegame.show/play/pewpew_v6 | https://livegame.show/play/bubbleshooter3

I will say though, Apple does seem to almost purposefully hold back the web on iOS. I suppose this makes native iOS apps, which must pay Apple 30% of their revenue, more appealing to users. On iOS, the Firefox and Chrome apps aren't allowed to include their own browser engines. They have to just wrap Safari webviews.

On Android, the Firefox app is allowed to include it's own browser engine. An engine that supports adblocking extensions like uBlock Origin.

[ Parent | on HN ]

Re:The future of my games on Apple and what this means for a... by fingerlocks on Monday November 11, 2019 @12:57PM (#21507010)

I think this is an issue with phaser. I’ve also made a bunch of web games with various frameworks, and webGL works fine on iOS in many other contexts. The js port of cocos2d is webGL compatible on iOS.

[ Parent | on HN ]