Slashdot Mirror
iPhone 1.1.3 Update Confirmed, Breaks Apps and Unlocks
An anonymous reader writes "Gizmodo has gathered conclusive evidence which confirms that the iPhone Firmware 1.1.3 update is 100% real. It installs only from iTunes using the obligatory Apple private encryption key, which nobody has. The list of new features, like GPS-like triangulation positioning in Google Maps, has been confirmed too. Apparently it will be coming out next week, but there's bad news as expected: it breaks the unlocks, patches the previous vulnerabilities used by hackers and takes away all your third-party applications."
I felt a great disturbance in the airwaves, as if millions of helpless iPhone apps cried out in terror and were suddenly silenced.
They cried out, "don't raze me bro!!!"
The iPhone SDK will probably be released at Macworld (January 14-18).
Do you even lift?
These aren't the 'roids you're looking for.
How dare Apple fix security bugs that can lead to arbitrary code execution!
They're violating hackers' right to run their code on whoever's hardware they like!
Funny. Microsoft allows complete and open access to their Windows Mobile OS (whether or not you can load your apps onto the phone is left to the decision of the carriers). In fact they even opened the source for the OS (okay, it's a Shared Source license, and it requires having an officially licensed version of Windows Embedded CE 6.0, but the source code is all there if you want to modify it while building a new device of your own). I think this is a case where you want Apple to act more like Microsoft rather than less.
On the other hand, I'm an iPhone user. I spent a fair amount of time playing with Windows CE in the past, and while I like the system I was not a fan of any of the current phones using it today. So I bought an iPhone, and I like it. The current lack of an SDK isn't slowing me down, since I probably wouldn't write any iPhone apps anyway (as much as I'd like to think I would, I know that I'd just dabble a bit and never actually finish anything). Sure, there are some things that are missing (GPS, full Exchange connectivity, an IM app), but I can live without those at least for now.
Apple wants to SELL the applications. If any coder can spend a weekend working up a decent solitaire game then that means they won't be able to charge $5 (or whatever) for their solitaire game on iTunes. The cell phone market has ALWAYS been about nickel and diming the customer to death. Charging for text messages?
The movement to provide on-demand services is NOT about improving life for the customer. It has ALWAYS been about improving revenue. Getting more for less.
and anyway...
I own a hacked iPhone with the 1.1.2 firmware with about 15 third-party applications on it. This thing is by far the most useful consumer electronics device I've ever owned (besides my pc of course). I don't have to upgrade to 1.1.3 and it is still useful to me. When it's cracked I'll upgrade.... but either way it's still a win/win for me.
Rats would be more funny if they could fart.
I'm not a developer, but I'm really thinking this Walled Garden thing is for the birds - which makes me want one of these less and less.
Okay, don't buy one. Apple's responsibility is not to you, the hacker (I love when I get the chance to use that word in the traditional sense), but to the person who buys the device and will never do anything unsupported with it. Why? Because these people either don't want to deal with incompatibilities or problems resulting from an update, or because they can't deal with them.
Normal users don't want to "update their phone" (which is a weird concept to many consumers in the first place) and have it break in some way. Because the official SDK isn't out yet, and there are no guidelines that third-party developers are following, Apple has no realistic way to support their software across updates. Attempting to do so at this point would be a massive, stupid waste of the available time of their engineers.
"Well," you're thinking, "the users who install unsupported third-party apps would be able to deal with bugs, or understand." No, most of them are going to whine and bitch on the Internet like they do now when Apple reverts their phone to a standard, known-good state during an update. But even if I'm wrong about that, it doesn't matter. The responsibility Apple's engineers have to the customer base on the whole is to guarantee that this phone that people bought "just works".
But this presents a problem, right? It makes this amazing portable device only what Apple wants. For some, this is a real issue. You can't disagree with that, really. To solve this problem, you need a supported SDK. And that's coming. Officially. That means developers like me can write software for the iPhone and it won't vanish after an update.
Releasing an SDK means you have to support it. Putting together an SDK you can support, and that is easy for developers to use, takes time. It's not just documentation, which in of itself is a large task if you want it done right--it's API design, build toolchain design, getting the supporting websites together and ready, training your developer support people in the new stuff, etc. It's huge! But Apple is doing it.
For now, third-party software developed through unsupported means is just that: unsupported. In the near future, according to Apple, we'll have a supported means of developing software for the iPhone. And it'll be better software, because we'll have the documentation we need.
There's no "walled garden", just a device whose SDK is in beta somewhere inside Cupertino walls.
Mikey-San
Karma: +Eleventy billion (mostly affected by watching Celebrity Jeopardy)