iPhone's Development Limitations Could Hurt It In the Long Run
ZDOne writes "Apple might have finally come around to allowing third party developers to create applications for the iPhone, but only up to a point. ZDNet UK claims Apple is leaving itself vulnerable to the competition and to a loss of lustre
by blocking background tasks on the device. The author notes, 'Perhaps it doesn't trust application designers or users very much. Perhaps it wants the best software for itself, where it can limit what it can do in order not to upset its telco friends. Whatever the reason, it reflects badly on Apple. The iPhone is not an iPod; it's a smartphone connecting to a universe of fast-changing data on behalf of innovation-hungry users. The sooner it stops pretending to be a 1981 IBM PC, the better it will be for everyone.'"
Because of this, if Apple abuses customers by crippling it's device, it is acting against the public interest for it's own gain. I don't blame them for this, their shareholders would be pissed otherwise, but the point of government is to make sure that the selfish interest of individuals does not clash with the collective good of society.
Our regulators should do something about this.
In terms of "background tasks," I think at least part of Apple's goal is to maintain a quality user experience. People have different expectations from a device like a phone than they do from a computer. Most people expect their computers to occasionally freeze (whether Windows, OSX, Linux or otherwise) due to some background process kicking off and monopolizing resources for a few seconds. When it happens, hit Control-Alt-Delete, run "top", or whatever, and figure out what's taking the CPU. People expect their phones to respond instantly all the time, and I don't think many want to bring up a process manager and click "kill process" while they're walking down the street trying to make a call.
Given the amount of sketchy, useless junk that one sees "freely downloadable" on most PCs and Macs, I don't think that Apple should necessarily want to export that same environment to the iPhone right away. The first application that everyone installs and which secretly launches a DoS attack on the mobile phone network at some predetermined time in the future is going to be a PR disaster for Apple. And that's a scenario way beyond some junk application that just locks up or slows down people's iPhones.
In the end, Apple should probably have a "power user" mode on their phones, the activation of which forces you to sign a disclaimer or non-indemnifation agreement that protects them if you screw your iPhone up installing unverified apps, run up your bill because some background process was doing data access thoughout the day while you were in Europe, etc. Many of those things could be "protected" against of course, if Apple put safeguards in their software (e.g., block any automatic data access when on a roaming network where data access might be charged), but I don't expect Apple to have thought of every possible bad outcome yet, but I do expect people to complain/sue like crazy if one of those bad outcomes occurs.
Either way, though, regulators are not the solution here. Any government (Democratic or Republican) is just going to screw things up even more, because they'll have their own set of interests--namely self-perpetuation--at heart.
Actually the GP has a point. I have a Nokia smartphone, and whenever there is a background task the battery is drained in a day or so. Otherwise my Nokia smartphone can last about a week without recharging.
What was bothersome is that I did not know at first why my phone needed a daily recharge. Then it dawned onto me that it was a background task running. And the irony here is that it was a poorly written Java applet that was causing the problems.
On this I have to give Apple quite a bit of credit...
"You can't make a race horse of a pig"
"No," said Samuel, "but you can make very fast pig"