5 ms·

why it doesn't work on my iPhone if it's html5?

LukaD 14y ago
It doesn't work because they probably haven't implemented the necessary html5 features on iOS' browser yet (e.g. Audio API).
- seclorum 14y ago
  In fact, Audio on Safari-iOS has been intentionally crippled by Apple (its not "un-implemented" features, its intentionally-not-implemented features") so as to prevent any disruption of iTunes revenue stream from Audio-playing websites.
  - hej 14y ago
    iTunes revenue stream. Ha. Playing mere music files is simple enough. I think mobile Safari can handle that.
  - ZenPsycho 14y ago
    I really don't think that's the reason. Not only does Apple not actually make very much revenue from iTunes, it is probably more to do with audio hardware on an iphone being limited.
    - kamjam 14y ago
      Not only does Apple not actually make very much revenue from iTunes Really? I guess 6% of it's net sales isn't a huge amount i guess, but when that equates to £6.3 billion I wouldn't regard that as small fish.
      - robmcm 14y ago
        Zing
      - ZenPsycho 14y ago
        Fair enough, nevertheless the motivation just doesn't ring true to me. Apple doesn't cripple things to protect revenue streams. They cripple things to maintain control.
  - huskyr 14y ago
    That's not a fact. However, the fact is that HTML5 audio is indeed crippled on iOS because you need a user action every time you want to play some audio, which also leads to lots of lag. However, even if that would be correctly implemented the Moog synthesizer would only be possible if they added the Web Audio API that Chrome and Firefox have.
    - TazeTSchnitzel 14y ago
      That sounds like intentional crippling. Apple haven't done that to avoid annoying people, they've done it so you can't make games with sound on the iPhone.
      - robmcm 14y ago
        They haven't removed the Geo Location API from Safari because it means websites could steal your location. They added a dialogue to ask if you want to allow them to use it. I imagine a simular API for sound would surfice.
  - robmcm 14y ago
    That's crazy, next they will be banning Flash in the browser ;)
  - juanpdelat 14y ago
    Audio on Safari for iOS is not crippled, in fact, Google Music[1] and other apps, for example GrooveShark[2] work on Safari. [1] http://play.google.com/music/listen http://play.google.com/music/listen [2] http://html5.grooveshark.com http://html5.grooveshark.com
wcoenen 14y ago
"html5" can refer to just the core markup specification, or it can refer to an entire collection of specifications for modern javascript APIs[1] in various stages of completion. No browser implements all those specifications. [1]http://upload.wikimedia.org/wikipedia/commons/f/f7/HTML5-APIs-and-related-technologies-by-Sergey-Mavrody.png http://upload.wikimedia.org/wikipedia/commons/f/f7/HTML5-API...

LukaD 14y ago

It doesn't work because they probably haven't implemented the necessary html5 features on iOS' browser yet (e.g. Audio API).

seclorum 14y ago
In fact, Audio on Safari-iOS has been intentionally crippled by Apple (its not "un-implemented" features, its intentionally-not-implemented features") so as to prevent any disruption of iTunes revenue stream from Audio-playing websites.
- hej 14y ago
  iTunes revenue stream. Ha. Playing mere music files is simple enough. I think mobile Safari can handle that.
- ZenPsycho 14y ago
  I really don't think that's the reason. Not only does Apple not actually make very much revenue from iTunes, it is probably more to do with audio hardware on an iphone being limited.
  - kamjam 14y ago
    Not only does Apple not actually make very much revenue from iTunes Really? I guess 6% of it's net sales isn't a huge amount i guess, but when that equates to £6.3 billion I wouldn't regard that as small fish.
    - robmcm 14y ago
      Zing
    - ZenPsycho 14y ago
      Fair enough, nevertheless the motivation just doesn't ring true to me. Apple doesn't cripple things to protect revenue streams. They cripple things to maintain control.
- huskyr 14y ago
  That's not a fact. However, the fact is that HTML5 audio is indeed crippled on iOS because you need a user action every time you want to play some audio, which also leads to lots of lag. However, even if that would be correctly implemented the Moog synthesizer would only be possible if they added the Web Audio API that Chrome and Firefox have.
  - TazeTSchnitzel 14y ago
    That sounds like intentional crippling. Apple haven't done that to avoid annoying people, they've done it so you can't make games with sound on the iPhone.
    - robmcm 14y ago
      They haven't removed the Geo Location API from Safari because it means websites could steal your location. They added a dialogue to ask if you want to allow them to use it. I imagine a simular API for sound would surfice.
- robmcm 14y ago
  That's crazy, next they will be banning Flash in the browser ;)
- juanpdelat 14y ago
  Audio on Safari for iOS is not crippled, in fact, Google Music[1] and other apps, for example GrooveShark[2] work on Safari. [1] http://play.google.com/music/listen http://play.google.com/music/listen [2] http://html5.grooveshark.com http://html5.grooveshark.com

wcoenen 14y ago

"html5" can refer to just the core markup specification, or it can refer to an entire collection of specifications for modern javascript APIs[1] in various stages of completion. No browser implements all those specifications. [1]http://upload.wikimedia.org/wikipedia/commons/f/f7/HTML5-APIs-and-related-technologies-by-Sergey-Mavrody.png http://upload.wikimedia.org/wikipedia/commons/f/f7/HTML5-API...