<off-topic>
I'm not sure what a "Apple software model" is. The concept of delivering minimal but functionally complete (and bug free) software then iterating quickly on it is something we call "Agile development" and is used extensively in the industry (with varying degrees of commitment). Some Apple teams use a specific version of Agile called "Scrum", and they seem to run a pretty good Scrum (although once a year is way slow for a release by Scrums standards, see Google+, Chrome for better examples).
If you want to give someone credit for that "software model" give it to Jeff Sutherland, not Steve Jobs. Jobs just knew a good idea when he saw one.
Sorry for the rant, I just hate when people give Apple credit for sliced bread 'cause they saw a Apple employee eating a sandwich one time. I'm on a one-man mission to make sure the world knows that they are not the pinnacle of human achievement. :tongue:
</off-topic>
Totally fair point. BTW, I run product management for a pretty good sized software team. I've very familiar with agile development.
To be clear, I wasn't intending to give "credit" but rather use them as a very familiar example to just about anyone. People are used to Apple products coming out with little complexity. Also, while agile may call for a minimal first version (even internally creating a minimal viable product, although we don't usually release those), that doesn't necessarily mean hiding complexity from the user (and on that point I suppose I am giving some credit) which I was also intending to convey.
But regardless, for the fellow tech folks out there, yes, I believe agile development including getting a bulletproof but less feature rich version out there must have been part of the deal here.