AT&T Welcomes Programmers for All Phones Except the iPhone
An anonymous reader writes "Apple's reasoning for keeping the iPhone a closed platform is that they don't want to 'potentially gum up the provider's network'. An article in the New York Times, though, points out that there are hundreds of phones out there working on open platforms that don't seem to be causing network interference. AT&T and Palm, in fact, welcome experimentation on their platforms. In AT&T's case ... on every phone but the iPhone. 'Hackers who have explored the workings of the phone say it uses the frameworks and structures that Apple uses on its other platforms to enable development; it just hasn't been documented. So if Apple is going to allow applications later, is there any reason -- other than vindictiveness or obsessive interest in control -- that it would want to cut off those developed by the pioneers who figured things out ahead of the official launch?'"
Control I buy into, but vindictive?
My guess is that the short answer is "Yes", and the long answer is "Yes, AT&T cut them a big fat check to do exactly that."
I've said from the beginning that the reason Apple's iPhone was closed to outside development was due to Apple, and not to AT&T. Apple is obsessive about controlling the end-user experience, so they don't want any third-party development on the iPhone. And what happened? I got accused of starting flamewars by rabid, foaming-at-the-mouth Mac fanbois.
There's nothing wrong with Apple intent on the iPhone. It's their product and they can market and sell it how they see fit. If you don't like it, don't buy an iPhone.
My blog
I remember back when Apple was going after people selling mac roms for Amiga emulators.
Apple has always been proprietary and exercised iron-fisted control over what THEY want done with the hardware they sell for a profit. Why are the iPhone actions such a surprise?
The most obvious reason for me would seem to be simply avoid responsibility for the API until it is fully matured? Surely, if they were to release their API for the entire multi-touch aspect of the iPhone and iPod Touch at this point, they would be in a position where they have a lot of responsibilities:
* extensively documenting the API for a broad base instead of only for internal usage
* testing for possible bugs for usecases which are not relevant in Apple's internal usage
* making it feature complete
* making it secure
* when upgrading the API, supporting older applications built on that API (in other words, keeping full backwards compatibility)
All in all, this can be summed up as the basic fact that officially releasing the "mini OS X" that Apple uses on its portable devices as a development platform requires a whole different approach then simply using it themselves and not publishing it. All these responsibilities are easily avoided by simply not publishing the API and is a no-brainer if the company is on a tight deadline. Given the iPhone's short development lead time, i can fully understand that there was no time to get all of the above in order, so avoiding responsibility of the API for the time being seems like a logical thing to me.
That said, the above reason would steer them towards a tolerance stance regarding 'hackers', while Apple seems to be leaning more towards an 'active prosecution' stance, which i considere pretty much unjustified, together with the rest of the world.
"Apple's reasoning for keeping the iPhone a closed platform is that they don't want to 'potentially gum up the provider's network'."
Yes, and I'm sure that's why they're keeping the iPod a closed platform, too.
Gifts for Geeks - Stuff that really matters!
And, why would anyone be surprised by this? It's very much in keeping with the way Apple has done business for years and years.
If you want news from today, you have to come back tomorrow.
They are selling an iphone, a way of thinking, an idea. The problem is, the cellphone market really doesn't give a shit. Apple hasn't learned that. The question becomes, who budges first? Apple or the cell phone market?
* Winners compare their achievements to their goals, losers compare theirs to that of others.
Are people just heart broken that Apple locked down the phone so much or what? If you want to support open platforms don't give Apple your money. I don't think it was a secret before the iPhone began sales that it was going to be a closed platform. Just like anything, support what meets your needs/wants.
"Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
The reasons were discussed before the iBricking event, but in summary:
1. Stability. Whenever third party apps are on your device, instability develops. Of course, sometimes the OS is unstable with no third-party apps running at all. Before the 1.1.1 firmware, Safari used to crash all the time. There haven't been a lot of reports about third party iApps being any worse behaved than the built-ins.
2. Support. Support issues are a perennial nightmare for any platform. It was speculated that lots of Apple and AT&T's support time was for applications that weren't native. Anyone have any numbers for this?
3. Development. It could be that the APIs are still in motion. The iBricking may be due to some bad updating; Mac OS X does have problem occasionally.
4. Developer support. Let's face it, lots of apps on other mobile platforms are ugly as all get-out. Apple's only now released human interface guidelines for the iPhone. If it's been this long for the HIG, the real developer docs'll take even more time.
So...there are lots of possible reasons for Apple's stance...before getting to the negatively-tinged personification excuses (control, vindictiveness, etc).
Once they sell it to someone, it becomes that person's product to do with as they like.
Apple has the potential of crushing RIM and Microsoft in the handheld market if the full capabilities of the device are unleashed.
-b.
It'd be trivial as hell for Apple to allow java apps that run in a sandbox. It's obviously not security that Apple's worried about.
As with most of their products, Apple tends to dictate the user experience to an unusually high degree.
For whatever reason.
Steve Jobs can't come right out and say this, as it can be seen as tantamount to saying that users are stupid. Security. Not on the cell network, but the iPhone as a new platform. User's can't be trusted to install their own apps!
So you're putting the blame on the user rather than the engineer? I thought we like to put the blame on the engineer around here (example: Microsoft).
I honestly do not think that the reason why the iphone is closed is simply due to security concerns. The reason why the iphone is closed is because cellular networks in the United States have enjoyed a monopolized control over their networks. Their biggest fear is that the cellular networks become more like the internet as it is now; a network where they are only seen as the provider to everyone else's services. Cellular networks have enjoyed making extra business by doing stupid things like selling ring tones, restricting accessible services (unless an additional cost is paid), and locking phones to their services. The basic deal with a cell phone is if you want to sell your service or software on the network, you either pay the provider or the provider hires you and pays you in a contract basis. Furthermore, once you're in, you play by the provider's rules. They dictate to you want you can or can't do.
You are correct about Macs and 6800's, but different user accounts have nothing to do with protected memory.
Well.. maybe. Or Maybe not. But Definitely not sort of.