I guess Apple has been surprised by apps popularity. Their original policy was that 3rd party applications ought to be web apps (initially, it was the only way to go).
Embedded applications make sense:
* for super-tightly integrated user experience: but then, you don't want any lowest common denominator middleware on the way, as they guarantee a crappy experience (typically way worse than a decent and portable web app, see below).
* for driver-like stuff that do magic (but Apple always hated the idea of 3rd parties writing such sensitive code, which is one of the reasons why OSX is way more stable than Windows)
* because in some countries, users are stuck with a not-so-reliable 3G carrier, so being able to run offline is valuable. Hopefully that's a temporary situation, and I understand that HTML5 allows to write offline-compatible web apps anyway.
* because it's culturally accepted to pay a couple of dollars for a fart simulator app, but most people won't pay a dime to access the New York Times content in a web site. That's the reason why most apps are apps rather than web sites, but that's a problem with the web, not Apple's business.
This last point is at the core of most issues with Apple's tight control on iPhone apps: most of them should have been web app. They've been written as apps not to benefit from the iPhoneOS platform, but to benefit from the AppStore's easy monetization and publicity. It's about the AppStore, not about the iPhone!
Brill!
The funny thing is, the price of 'software' has often really been driven by the price of distributing it, not the value it delivers or how much it cost to create it.
(Joel Spolsky has pointed out this is why Enterprise Software costs so much: because it costs so much to sell software to Enterprises).
The App Store really takes the friction out of the business of distributing binaries, including the friction out of marketing it. So it should come as no surprise that a lot of really good software is cheap in the app store.
It won't be long before you won't be able to charge for the NYT in the app store either.
"There's no software priced between $1000 and $75,000. I'll tell you why. The minute you charge more than $1000 you need to get serious corporate signoffs. [Etc. And to get that you need a salesforce and so on.] And with all this, the cost of making one successful sale is going to average about $50,000. If you're sending salespeople out to customers and charging less than $75,000, you're losing money."
(http://www.joelonsoftware.com/articles/CamelsandRubberDuckie...)
Joel was talking almost entirely about the sales effort, not so much about marketing (although you need a much more expensive marketing effort if you're playing the big sales force/big ticket sales game at the upper end, if only to establish your company and/or brand).
And I really wonder about lowering the cost of marketing. I don't know at all how this Apple App ecosystem works, but it seems to me that rising above the crowd and noise of 100,000? 1 million (if not now, soon enough) apps means you need serious marketing of some sort, or a stroke of luck where your app goes viral without much connected effort on your side.
The generally greater interconnectedness of today probably has a lot more to do with lowering the cost of marketing than anything having to do with the App store ... although that'll e.g. depend on its search function and how and if people use it. I note that Amazon gets by with what is by far the worst search engine of any site I've used in years.
And of course that's not a hard rule, there can be software priced in the middle where a less strenuous effort on the part of the corporate buyer gets the job done on his side (and many think that a major reason for corporate software piracy is not that the corporation can't afford it, but that it's so hard to get a purchase order through that borrowing a disk from someone across the hall is by far the path of least resistance).
And maybe this help explains some major failures, like Centerline's Code and ObjectCenter (interpretive environments (with interpreters, but you often just load compiled code on the fly) for C and C++ that are as close to a Lisp Machine as you could get for those languages).
Also, the $1,000 limit is undoubtedly too low, it's whatever your corporation allows you to spend without too much effort (e.g. CxO signoff). A few thousand dollars are OK, e.g. that's how PCs slipped into a lot of companies, on departmental but not corporate budgets. (Heck, that's how a few Z-80 CP/M machines slipped into LMI when we had at most 3 CADRs operational at a time and a strong bias against doing anything outside of a Lisp Machine.)
That said, I'd be surprised if Apple spends too much effort policing the rule. The fact that it exists in the first place will probably be enough FUD to prevent third party toolkits from taking off at all. They'll probably do some kind of automated signature testing for Flash, Unity etc and leave it at that. The upside of that is you'd probably be able to sneak a Clojure or whatever app in and nobody would probably care too much.
Apple wants to drive away developers who are spreading their apps thin over multiple platforms. I think you're right that it's quite unlikely they will relent on this, at least on paper.
As for policing, I think you're also right that it won't be particularly onerous. I see enforcement less to the letter and more to the intention of 3.3.1: If your submitted app feels like a rough port, they'll probably check for cross-compiler evidence and reject it on those grounds, but if it fits right into the iPhone experience, they probably aren't going to go hunting for traces of Lisp.
What is has to do is with lock in. Right now, there's a decent barrier to porting an application from iPhone to Android, and in most cases the port will cost more than the profit it makes, so it won't be done.
If people start using multi platform engines, the ports will be very cheap, and the iPhone will have far fewer exclusive apps, which is a huge threat to their platform. Each multiplatform app reduces the costs of a user switching away from the iPhone to an Android phone or similar.
Apple's been on the losing end of lock in with Mac OS for a long time. I think now they're experiencing the effect in their favour and want to keep it going for as long as they can.
If everyone is writing in Cocoa on XCode, Apple's latest & greatest will be deployed that much more quickly.
I think this interpretation is consistent with Jobs' terse emails here, particularly the line, "intermediate layers between the platform and the developer ultimately produces sub-standard apps and hinders the progress of the platform" (emphasis mine).
Suddenly it matters very much indeed that lots of games start calling new platform-native APIs, right fucking now.
Saying that they're doing it to further their platform sounds a hell of a lot better than saying that they're doing it to hurt their competition!
At best you could say that there won't be an intermediary platform delaying the process...but I'm not sure if that really is a compelling reason to justify this decision.
Without cross-compilers, the lag is as you say: developers update their apps. With cross-compilers, the lag balloons: the makers of the cross-compiler toolset need to incorporate the latest Apple features (if they choose to do so given the rest of their market), roll out their tools to developers, then developers have to use the new tools to update their apps. Slow!
I would agree with you that Apple's been doing the same lock-in with Mac OS for a long time, but I'm not so sure they've been on the losing end of anything. I remember that when Jobs came back to Apple, they had free WWDC videos online, and attendance was very much in decline. Since he came back, they removed the Java bridge stuff, Carbon and at the same time they're charging good money for a WWDC that tends to sell out really quickly. Lock-in on the Apple way seems to me to be a fairly successful strategy.
That's true today because they're the main platform. This might change if, say, Android becomes much more widespread than iPhoneOS. When this happens, they might concede on things like 3.3.1.
Then again, Apple is quite comfortable with having minority share but huge profit margins in a market: I'd guess that 90% of laptops sold over $1000 are Apple, and that their margin is something like 5 times Dell's...
If multi platform engines take off, we are a few short years away from a situation where the choice of mobile platforms is like the choice between browsers is now - no lock in, low switching costs - and I think they want to avoid that at all costs.
There is already a cross-platform, 100% uncensored dev framework, with excellent distribution channels, and it's called HTML5. I'm not sure there is a niche for a 2nd one, especially if Apple is unhelpful.
Apple isn't focused on developing a smart phone operating system. They're focused on redefining what a computer IS, and how we interact with them. That's why they've been so careful about copy+paste, and later multi-tasking. They are taking this as a chance for a clean slate approach to computing and don't want to be hampered (or their customers to be hampered) by slow-moving third party compatibility layers. How much as Window's development hampered by the fear to break legacy apps compatibility moving forward? Apple isn't afraid to make their developers jump through hoops and make changes if they think it will benefit the platform in the end (a la the Intel switch). They'll provide tools to make that as painless as possible when the time comes (e.x. iPhone app compatibility on the iPad, Rosetta) but having another layer in between only slows this process down.
Whether you view Apple's actions as that momentous and revolutionary is largely irrelevant. I think THEY do.
Not that I'm not upset by this as well, but I'm trying to make sense of it.
As I see it, there are two elements that define the modern software: end-user experience (not only GUI, but things like local storage, geolocation etc), and communication with the Internet. With low bandwidth, Web apps have all the advantage with the latter and are good enough with the former; with ubiquitous broadband, the latter advantage is meling away, and the former just being "good enough" might not be, well, good enough anymore.
Moreover, repeated installations and deinstallations degrade a computer's performances and security. It's much more obvious under Windows than under correctly designed OSes, but always remains true.
I expect a 95% web-based slate/phone to be mostly stateless, and to remain functional indefinitely without requiring administration, as opposed to a computer.
I don't think is it. I remember when Metrowerks PowerPlant was the main framework. Apple had let their own MacApp and MPW languish. Arguably Metrowerks CodeWarrior saved the Mac as a development platform.
Anyway, the puzzling thing here is that as Greg says, most iPhone OS apps are written in one of the whitelisted languages already. Couple that with what I think is the likely fact that Apple is being honest about its motives (namely that it doesn't want its roadmap to have to consider third-party toolkits in any way), and it's confusing. Why would they go to the trouble of pissing everyone off to bring about a result that had largely brought itself about?
Two answers. One, I think Apple feared that more third-party toolkits are on the way, and that they'll become more popular. Two (and I think this is a huge part of it), Apple seems to have simply underestimated how mad this would make developers.
I wouldn't be surprised if the company went back on 3.3.1, or at least moderated it. Apple's only willing to be a jerk when it and the public agree about the level of jerkitude at hand. If Apple gets more ire than it was expecting, there's precedent for it backing down.