Apple’s Music Is Where They’d Not Like You To Touch

by Eric March on March 21, 2008 at 10:55 am

The more developers dig into the SDK, the more restrictions they find. The latest nugget appears to deny developers access to iTunes functions. Presumably this was done to prevent the creation of competing online music stores — which is, of course, in Apple’s best interest. The problem however is that it also eliminates the possibility of creating addons or enhancements to the music player in the iPod Touch and iPhone. This is quite disappointing to me, because I have been clamoring for the creation of a custom equalizer since day one, and I know many others have been after various other enhancements, like additional codec support, in-player touch gestures, and so on. I can’t say as I’m all that surprised though. Stuff like this fits right in with Apple’s iron-fist MO: Any API features that could potentially be used to bring the device to harm or wrest control away from Apple get locked down tighter than detainees in Gitmo. It’s too bad though. So much potential is being unceremoniously flushed down the bog that could otherwise be used to greatly enhance the overall iPod and iPhone experience and boost sales even further. I’d like to think though that if there is enough demand for it, Apple will have to do a cost-benefit analysis on the inclusion of such features in the SDK and maybe ease off the restrictions a bit, allowing developers to do what they do best.

(Source: MacWorld)

If you enjoyed this story, join the growing number of subscribers to our RSS Feed for live updates!

Related Stories:

• March 11, 2008 -- Rogue Amoeba Puts SDK Under Microscope (2)
• March 23, 2008 -- First Glimpse of the App Store? (1)
• March 21, 2008 -- Google’s SDK Hearts iPhone SDK (0)

Posted in SDK