Re:Mobile Safari's Performance Is Not the Problem
by untog on Wednesday July 29, 2015 @01:56PM
(#9970369)
I ran into the same issue trying to use a video as a texture in WebGL. Worked beautifully on desktop, mobile and even in an iOS UIWebView with inline video allowed. But in Safari? Nope.
I do get the reasoning why it was done when the iPhone 1 came out, but come on. Everyone ends up using animated GIFs instead, which just chew up more bandwidth.
Re:Mobile Safari's Performance Is Not the Problem
by CPLX on Wednesday July 29, 2015 @01:08PM
(#9970001)
> I had to develop a video overlay
Define "had to"
Re:Mobile Safari's Performance Is Not the Problem
by happyscrappy on Wednesday July 29, 2015 @01:45PM
(#9970268)
Apple puts users before developers and actively thwarts advertisers. If you are not concerned with security or usability Android is fine.
Wasn't a problem with performance - even an aged iPad1 was able to fluently do all the movement, translations etc.
What forced us to choose the ridiculously expensive option of server-side prerendering with After Effects was that iOS Safari is unable to play a HTML5 video inline on iPhones and thus cannot be overlaid with a Canvas.
Fuck you very much, Apple.