The Cross-Platform Myth
marcuscavanaugh.com
marcuscavanaugh.com
Edit: But you're right it's quite a nice interface.
But regardless of my friends' feelings on the matter, my stats just do not say that Mac users are rejecting the program. They convert at fully twice the rate of Windows users. If anything I need to look at what I've screwed up in doing a Windows-y interface that wasn't Windows-y enough, apparently!
That said, having a truly native interface can't hurt: if you were to pit a native interface against a non-native one, the non-native application would have a hard time competing.
I hate using Java Swing apps. It's an accumulation of minor irritants that cause this hatred:
1. the inability to interact with OS X Services;
2. copy/paste not working exactly like Cocoa apps;
3. font rendering being messed up;
4. the fact that the menu system is usually different than a Cocoa app and that I can't customize keyboard shortcuts as easily.
.
.
.
However, the presence of all of these irritants doesn't mean I won't tolerate a Java Swing app if I absolutely must, because there isn't another feature/functionality equivalent application out there.
What Apple have is a consistent interface. This is the real point here, that if each OS has a consistent interface between native applications, then a cross-platform application will be at a disadvantage because by definition it will be inconsistent with most platforms. This is true to some extent.
But these days the real competitor to a native app is not a cross-platform app - it's the cloud. It would be interesting to see some data as to whether people prefer an inconsistent cloud app (say, gmail) to a native consistent app (say their native mailer). Absent any data, I am not sure what can be learned here.