Quote:
Originally Posted by
Relic 
OTA, over the air updates which was just introduced in 2011, it took Apple almost 5 years to come out with it, that's a pretty long time.
I sure hope Microsoft can do it, we need more successful competition not less. Just having two main platforms to choose from just sucks. RIM is pretty much dead so now more then ever we need a good corporate mobile phone and I really think MS is the way to go. Here's hoping they can pull off the impossible.
Mea culpa. Thought were you referring to the SDK and App Store.
Slightly over 4 years* is a long time in tech but consider what has to be done to make it safe and effective.
It's not just making sure the system can hold the image, but making sure that the update can't be hacked so it pushed a malware update to users. This would happen fast enough that it's unlikely Apple could resolve the issue before devices are compromised.
Another issue, and the one that I think Apple has taken for too long to get a handle on, is the size of the updates. You can't have 700MB updates being pushed to a device over an 802.11g network every time you have a tertiary (x.x.1) point update.
Are there benefits to Apple's previous method? Absolutely! It's more secure and has built in redundancy but it means it's slow and clunky in comparison. It's much like iDisk is to Dropbox. IOW, if you lose a connection to an iDisk download you lose the entire file and have to start all over, but with Dropbox you maintain the packages you've already receive, hidden from view until they can be put together.
There are still issues with Apple's OTA update service as of iOS 5.0.1. For instance, if you didn't have enough room on your device in your "user space" the IPSW couldn't load the files that it needed. Or maybe it could expand the files after it downloaded them. Either way, it was an issue that I'd think could be easily resolved by the system first getting the download (or expanded installer) size before it starts. If it's not enough it could then inform you of the issue. As of 5.0.1 it didn't offer any usable error message.
Finally, there is network congestion. I'm sure you haven't thought about this but when Apple issues an iOS update it goes to all their iOS devices at the same time. This means 3 years of iPhone releases, 3 years of iPad Touch releases and soon to be 3 years of iPad releases. Now consider how many of those iOS-based devices Apple has sold since 2009. With other mobile OSes you get 1) stepped OTA updates so that even if you have a device that is updatable you may not get it for more than a month if your device isn't chosen by the powers that be. I knew of no way to contact HTC of MS to get the update for a WinPh device last year when Mango arrived. And that's just one device model!
You can't simply say that since one company did x that Apple should have been able to do x, too, without considering all the factors. Even then you can't say that because Apple could have technically done x that it would have been smart to do x simply because it was technically possible. We've seen this year-after-year as some new
Apple-killer comes to market with specs that are technically superior but poorly executed. Bottom line: Having something you check off on a spec sheet doesn't mean shit if it doesn't work.
* If you are going to round then round to the nearest year.