March 13th, 2008
There seem to be 2 camps of opinion as to why the SDK wasn’t released until almost a year after the iPhone’s release:
- Camp a) suggests be that the iPhone was to remain closed, but developer protest and internet whining forced Apple to change their stance.
- Camp b) is more realistic and says the SDK was planned from the start, but had to be whipped into shape and locked down first.
I tend to agree somewhat with camp b), but I also think that another factor might have been relevant as well: Thanks to the “development via webapps” farce that Jobs presented last year at WWDC, the iPhone has more websites optimized for its user interface than any other mobile device available.As iPhone-optimized websites seemed to be the only way to achieve any sort of interaction with iPhone users, not only can those users they access the “real internet”, but they can actually use a “version” of the internet custom-designed for them.
Whilst some people have derided iPhone-optimized websites as missing the point of MobileSafari being able to render “real” webpages, I personally love their simplicity and they’re perfect for getting things done whilst on the go. Would all that effort have been made if developers went after the real prize, namely nabbing the native iPhone app market? I doubt it.
Getting developers to focus on the boring task of optimizing websites would be impossible with the shiny, exciting iPhone SDK occupying their time.Did the SDK need time so Apple could add some spit, polish and padlocks? Undoubtedly, but I believe the quality of the user experience while browsing the web on the iPhone is much better for that delay. Was the delay intentional? I wouldn’t go that far… but it certainly didn’t hurt the platform as a whole.
Posted in iPhone | Comments »