News for hackers. Stuff that matters.
Re:Steve Jobs’ response on Section 3.3.1 by reitzensteinm on Saturday April 10, 2010 @07:44PM (#1255953)
I would be surprised if they did go back on 3.3.1. They're hurting themselves with the backlash, yes, but they're hurting other mobile platforms far more, further securing their position as the #1 mobile platform to develop for.

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.

Re:Steve Jobs’ response on Section 3.3.1 by mortenjorck on Saturday April 10, 2010 @08:15PM (#1256020)
It took me a few days to figure out why Apple would risk driving away developers like this, until I realized: That's the whole point.

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.

Re:Steve Jobs’ response on Section 3.3.1 by reitzensteinm on Saturday April 10, 2010 @08:30PM (#1256046)
I don't think it has to do with the quality of the applications at all. Apple hasn't taken many steps to control quality in their app store, and there's not much difference between having an app that's bad because it's a port and an app that's bad because it's a badly made original.

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.

Re:Steve Jobs’ response on Section 3.3.1 by davi on Saturday April 10, 2010 @11:08PM (#1256239)
I think there is also another dynamic at play: Apple makes high-end, high-margin 'lifestyle' computing devices. Every time Steve Jobs gets up and announces a new whiz-bang hardware or software capability in one of these devices, that whiz-bang capability needs to be deployed as widely and quickly as possible into the consumer ecosystem. This rapid deployment lets Apple keep ahead of the Joneses and continue to own the high-end space. If there is a lag while least-common-denominator, cross-platform tools incorporate the new whiz-bang features, Apple loses its temporal edge and gives time to competitors to catch up. The last decade has built up the "Apple == newest" identity in consumers' minds, and they don't want to lose that, it is one of the keys to their hold on the high end (another being incredible design and polish, at scale).

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).

Re:Steve Jobs’ response on Section 3.3.1 by blasdel on Sunday April 11, 2010 @12:57AM (#1256386)
At first I was thinking that Apple wasn't targeting the game engines with this, but they're releasing a social "Game Center" API to compete with Xbox live and Facebook.

Suddenly it matters very much indeed that lots of games start calling new platform-native APIs, right fucking now.

Re:Steve Jobs’ response on Section 3.3.1 by davidedicillo on Sunday April 11, 2010 @01:16AM (#1256404)
I completely agree. Also this push more people to learn and write Cocoa, that will ultimately push those developers to build awesome desktop apps as well, increasing the value of the OS X platform.
Re:Steve Jobs’ response on Section 3.3.1 by reitzensteinm on Saturday April 10, 2010 @11:58PM (#1256310)
After some reflection, I think you're definitely right that it's a factor. But I'd still be surprised if it were the primary one, despite what they claim. The developer base is just so huge, any new platform feature is going to have dozens of apps to show it off right away.

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!

Re:Steve Jobs’ response on Section 3.3.1 by davi on Sunday April 11, 2010 @12:18AM (#1256338)
I agree this temporal aspect isn't the only dynamic, but I don't see people talking about it much (at all?). I think it's worth thinking about as an angle on the whole thing. Market tempo matters. Doesn't make what they're doing any more palatable, mind you -- but it does make it more comprehensible (to me, anyway).
Re:Steve Jobs’ response on Section 3.3.1 by stevenwei on Saturday April 10, 2010 @11:17PM (#1256256)
I'm not sure how valid this point is...there is already going to be a lag since all of the current app developers are going to have to update their apps to support the new APIs anyway.

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.

Re:Steve Jobs’ response on Section 3.3.1 by davi on Saturday April 10, 2010 @11:34PM (#1256274)
there is already going to be a lag

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!

Re:Steve Jobs’ response on Section 3.3.1 by MWinther on Sunday April 11, 2010 @09:06PM (#1258078)
The problem with cross-development tools is that the people using them tend to focus on the app working on all the supported platforms, making it effectively using the lowest common denominator. If Apple releases a new API not available in the cross-platform tool, cross-developers are far more likely to ignore it than developers targeting Apple's platform specifically.

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.

Re:Steve Jobs’ response on Section 3.3.1 by fab13n on Saturday April 10, 2010 @07:59PM (#1255986)
> They're hurting themselves (...) but they're hurting other mobile platforms far more.

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...

Re:Steve Jobs’ response on Section 3.3.1 by reitzensteinm on Saturday April 10, 2010 @08:14PM (#1256016)
That's true. I should clarify that I meant in the short term - definitely they'll change their position the minute it benefits them. But right now, it certainly doesn't.

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.

Re:Steve Jobs’ response on Section 3.3.1 by fab13n on Saturday April 10, 2010 @08:22PM (#1256029)
Once 3G will be reliable and truly unlimited, what would cross-platform apps offer that web app don't anyway?

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.

Re:Steve Jobs’ response on Section 3.3.1 by RyanMcGreal on Saturday April 10, 2010 @08:42PM (#1256065)
Native apps still enjoy a pretty hefty UI advantage over web apps. I don't see that changing in the next few years.
Re:Steve Jobs’ response on Section 3.3.1 by ZeroGravitas on Sunday April 11, 2010 @07:42AM (#1256713)
And it appears Apple won't be the one pushing it forward, despite all their work on webkit. Which is enough for me to jump ship when the time to get a new phone arrives.
Re:Steve Jobs’ response on Section 3.3.1 by BerislavLopac on Saturday April 10, 2010 @09:39PM (#1256140)
Actually, I would prefer to put it the other way around: Once 3G will be reliable and truly unlimited, what would web apps offer that cross-platform app don't anyway? Give it some thought before answering.
Re:Steve Jobs’ response on Section 3.3.1 by masterj on Sunday April 11, 2010 @12:02AM (#1256318)
Apple doesn't have to take web apps into consideration when they're considering changing the platform or the API however they see fit. They're committed to upholding open web standards, but have no similar commitment to their own API. HTML standards are slow to evolve by design, and Apple is okay with that, however that is the last thing they want with their own software stack.

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.

Re:Steve Jobs’ response on Section 3.3.1 by BerislavLopac on Sunday April 11, 2010 @04:40AM (#1256577)
Er, I wasn't talking about Apple, but software development in general.

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.

Re:Steve Jobs’ response on Section 3.3.1 by fab13n on Sunday April 11, 2010 @01:56PM (#1257270)
As a developer, I might prefer to write local apps. As a user, the zero install + security guarantees make web apps much preferable. Plus, given that cross-platform toolkits only offer the lowest common denominator, the resulting applications typically don't look better than a good web app.

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.