Now reading the article closely (I mean reading it) this here:
"So to summarize: Apple will neither forbid nor support native code on the iPhone/Touch. They will not design software updates specifically to break native apps, but if the updates happen to break native apps or your native apps turn your iPhone into a rutabaga, don't go crying to Apple, 'cause it ain't their problem. Capiche?"
This sounds much more mild. So, they change an API or so that can break apps? Sure, so an app author has to fix their app a bit, recompile and release a new version? No problem. I can't imagine it being worse than WoW UI Addons which get broken alot, but get fixed if the author is active quite fast (even though they're officially supported).
Reader Comments (Page 1 of 1)
nathan @ Sep 12th 2007 1:04PM
Now reading the article closely (I mean reading it) this here:
"So to summarize: Apple will neither forbid nor support native code on the iPhone/Touch. They will not design software updates specifically to break native apps, but if the updates happen to break native apps or your native apps turn your iPhone into a rutabaga, don't go crying to Apple, 'cause it ain't their problem. Capiche?"
This sounds much more mild. So, they change an API or so that can break apps? Sure, so an app author has to fix their app a bit, recompile and release a new version? No problem. I can't imagine it being worse than WoW UI Addons which get broken alot, but get fixed if the author is active quite fast (even though they're officially supported).