I don't think this is as big a "reversal" as the story leads on.. I read this to mean that the API for the Apple Touch Devices (iphone & ipod touch) is still maturing. They are still working out API breaking changes (like adding cut and paste for example). And they aren't tying themselves down to the idea of backwards compatibility.
I would put money on that in 18 ~ 24 months (maybe sooner) Apple developers (specifically their software architects) will rubber stamp an API as stable for publication and shortly after that some kind of official SDK will be released. The definitely wouldn't want to do something like that until they were VERY comfortable with the idea of chaining the weight of backwards compatibility onto their development team!
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
I don't think this is as big a "reversal" as the story leads on.. I read this to mean that the API for the Apple Touch Devices (iphone & ipod touch) is still maturing. They are still working out API breaking changes (like adding cut and paste for example). And they aren't tying themselves down to the idea of backwards compatibility.
I would put money on that in 18 ~ 24 months (maybe sooner) Apple developers (specifically their software architects) will rubber stamp an API as stable for publication and shortly after that some kind of official SDK will be released. The definitely wouldn't want to do something like that until they were VERY comfortable with the idea of chaining the weight of backwards compatibility onto their development team!