Apple's Walled Garden Will Hurt iPhone Innovation

from the barriers-to-entry dept

The release of Apple iPhone SDK got a ton of attention on the blogosphere. Personally, I found the announcement to be a huge disappointment, because the rules for getting applications on the iPhone are chock full of restrictions. TechCrunch notes some of the major ones: No VoIP over the cell network, no exchanging data between applications, no multi-tasking (third-party apps quit when you switch out of them). But the more serious problem isn't strictly technical, but contractual: the only way to get third-party applications onto the iPhone is through Apple's "App Store." And Apple plans to carefully monitor the apps available through the store. Apparently "porn, privacy-breaching tools, bandwidth-hogging apps, and anything illegal" are examples of what will be off-limits, but that's not an exhaustive list.

The problem here goes beyond the mere possibility that Apple might block apps that some users would find useful. The more serious problem is the effect that the approval process will have on developers. Given how vague the rules are (what counts as bandwidth-hogging?) and that Apple is free to change them at any time anyway, it's going to be risky for a developer to start developing an iPhone app that Apple might reject. TechCrunch wonders, for example, if Apple would allow an app to download songs from Amazon's MP3 store. To avoid a nasty surprise at the end of the development process, any serious developer will want to talk to Apple ahead of time, but negotiating the feature set ahead of time could delay the product by months.

Perhaps most importantly, these barriers are going to be a serious disincentive to casual tinkering. Some of the greatest applications on the Internet -- including email and the Web -- were developed by one or two guys without the support of a large organization behind them. They were able to deploy their applications because the Internet (and the ARPANET in the case of email) didn't have any kind of approval process. You could just install your application and start using it. On an open iPhone platform, the killer mobile app might have been developed the same way. But if a developer has to spend a lot of time arguing with Apple's iPhone bureaucracy, they're likely to give up and develop the app for an open platform like Google's Android instead.

Filed Under: innovation, iphone, sdk, walled gardens
Companies: apple

Amazingly Enough: People Don't Want To Pay To Watch Broadcast TV On Their Mobile Phones

from the who-woulda-thunk-it? dept

Back in 2004, with mobile companies left and right announcing plans to launch premium-priced broadcast TV services for mobile phones, some of us were wondering who would actually pay for such a thing? After all, you were talking about a tiny screen and people on the go who likely didn't have the time to sit and watch an entire TV program. Even more importantly, in the age of both time-shifting and internet video, it's increasingly less important to be able to see a TV program right now, when you can catch up later. Yet, that didn't stop many companies from throwing billions into such projects, spurred on by analyst reports predicting huge revenue to come. Yet, after all these years, it seems that mobile operators are finally realizing that people just aren't that interested -- especially if it costs extra. It's no surprise why mobile operators ignored all the warning signs. Analyst firms were singing the praises of mobile data services and warning any operator that didn't jump on the bandwagon that they'd be left behind. Yet, at some point, you'd think it would make sense for the mobile operators and the analysts hyping this stuff up to take a step back and see if what they were pitching actually had any value to users.

Filed Under: broadcast tv, mobile phones