iPhone SDK and Restrictions: Some of the Details Aren’t Great 22 comments
-
Font Size:
-
Print
- TweetThis
Obviously Steve Jobs and team didn’t go through all the details today when they announced the availability of the iPhone SDK. It was more of a high level pass. But details are what third party developers need to think about before jumping into the iPhone with both feet.
Last year when Facebook announced Facebook Platform, developers had to decide to ignore it, build for it along with a standard web site, or build exclusively for Facebook. Venture capitalist Josh Kopelman layed out an argument that some developers should immediately build on Facebook v. developing for MySpace, despite the fact that it was (and is) proprietary.
Facebook Platform has its own venture funds to support new startups. As of today, so does the iPhone.
The decision to build an iPhone application is very similar. Some developers will add one to their existing products. Others will go iPhone only.
Should we expect Kopelman to write a new post, urging developers to build an iPhone application as soon as possible? Maybe. But a number of bloggers and developers did some digging today into the fine print, and there are some troubling details.
Some of the limitations were announced at the event today. VOIP services, for example, are basically out of luck. They can access the Internet only via wifi, not the cell networks. That’s a signal of a larger issue, though - that Apple isn’t going to allow applications to threaten any of their revenue streams from the iPhone. Likewise, SIM unlocking is forbidden. But what about other, less black and white applications? John Gruber asks if Amazon would be able to launch an iPhone application that allowed users to buy songs from the Amazon MP3 store. That’s a great question, currently without an answer.
Other limitations can be found in the developer agreement. Developers can only use the published APIs and only in the way Apple says they can use them. Ok, that helps with stability. Applications also cannot write data anywhere except in their designated area, meaning developers can’t modify data from any other applications.
But the single biggest issue we’ve found is in the 100 page iPhone Human Interface Guidelines. It’s a public document, but you must be a registered iPhone developer to see it. We’ve embedded it below via docstoc.
Users can only run one application at a time, and if they leave an application it quits. That doesn’t seem like a big deal, but it means that you can’t switch away from an application and have it continue to do things. That’s a big issue with the current support for websites on the iPhone - as soon as you leave the browser the connection is broken. With the iPhone, the hope was that an installed application could continue to run in the background and, most usefully, gather and send information from and to the web.
Only one iPhone application can run at a time, and third-party applications never run in the background. This means that when users switch to another application, answer the phone, or check their email, the application they were using quits. (p. 16)
This will be a serious problem for some developers. For example, say a developer wanted to take location information from the iPhone (created via the iPhones cellular triangulation feature) and dump it into FireEagle to keep track of where you’ve been. Well, that won’t work unless you keep the application open at all times, and don’t use the iPhone for anything other than that. Another example: instant messaging applications (we saw a demo of an AIM version at the event today), can’t run in the background and collect messages while you are doing something else. Leave the application to take a phone call, and it shows you offline. The bottom line is - any application that wants to periodically interact with the web to do stuff, won’t be able to on a continual basis.
Perhaps future versions of the iPhone, with additional CPU and memory resources, won’t have this limitation. But for now, whole classes of applications are useless, or are significantly less useful than they otherwise would be.
iPhones Human Interface Guidelines - Get more free documents
Related Articles
|




























This article has 22 comments:
Apple just laid one of the best SDK's ever at developers' feet.
And 100 million in seed money to boot.
This is unprecedented and will have developers tripping over themselves to publish their apps, despite the imaginary impediments you are placing at their feet in this writeup.
With this latest news the iPhone is about to blow up, making the iPod fenom look like a hobby.
I was planning on watching the two companies battle it out, but it's looking more like 'game over man'...
And isn't that what the 4 companies said (and demo'd) after using the beta for 2 weeks ?
So I wish these financial guys (like this bozo) would stick to talking about cash flows and P/E ratios....and stop trying to talk about technology development platforms.
And why no mention that this will be a fantastic game platform with hardware optimized graphics, full access to the 360* motion sensor and over the air game download ?
I could continue but this guy just probably wants hits and not details anyway. I don't know what seekingalpha is....just an opinion blog ?
And then to go and blog it to the world...
Where, oh where, do these people come from?
BINGO WSG ........ to start ..porting Mac games should be very easy
i wonder if we'll ever get to play guitar hero on an iphone
Now, wouldn't that be a phun user experience?
Things are looking seriously bad for anyone not in favour of Apple winning the new global platform...
You deserve to be called idiot, ass, loser, etc for your opinion
All AAPL fans: Support Steve and buy as many iPhones and Macs as possible. He needs your money more than you do.
And while I wouldn't want 60 background apps killing my phone abilities either, I'd have to say that things like AIM would not work without having some facility for a SMALL background application keeping the connection alive. Nor will their Exchange connector with push e-mail, but being from Apple it won't have to follow the same rules.
I'd submit to further application scrutiny to gain additional privileges, if that were an option.
Anyone notice there's no API to initiate a phone call, text message, or e-mail? or not one I could find as of yet..
Take a look at the comments on this and other stories, plenty of names being used to describe the authors.
What is it with the "hope was that an installed application could continue to run in the background and, most usefully, gather and send information from and to the web."
Here's another gem, "VOIP services, for example, are basically out of luck. They can access the Internet only via wifi, not the cell networks."
Isn't that good enough? You expect AT&T to let you make unlimited phone calls with your data plan? Can you even afford an iPhone, or are you interested in selling hacks to swindle AT&T out of its revenue?
Here's another one: "SIM unlocking is forbidden." Did you serious? You expect Apple to sell hacks and give 70% to guys who will cut out the revenue it may receive from its carrier partners? How is that going to affect the negotiations in China, India, Canada, Russia, and 100 other countries where Apple is hoping to sign deals?
"Developers can only use the published APIs and only in the way Apple says they can use them." This is not an open platform. How do you suppose all these API will be updated and incorporated into every iPhone? Who will be responsible to support the device in case of problems or conflicts? You want to write your own API, go make your own phone platform. or develop for Linux or Android.
As for applications running in the background, no, thank you very much. I can imagine people lining up at the genius bar with "my iPhone seems to be frozen, or my battery lasts only 30 minutes" because there are 15 applications running in the background.
And finally ... "this will be a serious problem for some developers. For example, say a developer wanted to take location information from the iPhone (created via the iPhones cellular triangulation feature) and dump it into FireEagle to keep track of where you’ve been."
I don't know anyone who would want such a feature, or a developer stupid enough to contemplate it for the mass market. I can think of a parol officer of a rich youngster who might require the fellow to buy this app, but he would have to make sure the phone is always on and always charged.
Michael Arrington - one must remember that name. With ideas like that you must be sure to toss any resumé on which it appears.
"Did you serious?" It should read "Are you serious?"
and
"parol", should be " parole"
and whatever else I mistyped.
Or maybe I'm just reading too much ValleyWag...
Thank you to all that contribute their thoughts and God bless our troops.
Lots of people. Disney Mobile has such a feature on their phones that allows tracking and they seem to have a mass market for kids phones and parents who want it. There are a lot of other opportunities here too.
A small background application (you are talking less than 1k of code) would handle a lot of the hard work and use very little battery life.
Guys, the SDK sucks, it is nicely packaged but will allow only mild applications to run on the iPhone, it is more closed SDK then an opened SDK. Google, on the other hand, has a completely open SDK, very easy to work with and having 26 cellular manufacturers behind them...they are going to have 10x of the iPhones in no time with much more exciting applications. I have an iPhone, it is the best cellular phone in the world by far ...but i have a feeling that Mr. Jobes, being vain again ... is going to miss the real big opportunity that Apple has ... Unfortunately for Apple i think Arington is right ..