They've certainly gotten the look and feel right, because I didn't realize it was a Java application, but it is pretty sluggish, at least on my machine.
I don't think this is how it works, at least in the OS X market. I never seen any but 2-3 Java apps become popular, and none that much. All the popular, successful apps are native.
So, you can maybe deliver faster with Java (doubt it, since you'll have to implement all the Cocoa goodies and cool integration APIs by yourself) but it wont get you that far.
At least one of the built-in apps on early versions of Mac OS X (10.0/10.1?) was actually Java/Cocoa -- I want to say TextEdit, but I'm not certain. Soon after, of course, everything got ported to Objective-C.
Only up until Tiger. And you still had the "uncanny value" effect, despite the native-ish look and feel to Swing.
Plus, even SUN and then Oracle abandoned Java on the desktop.
Yes, then they would have been unusable because of slow performance and regular gc pauses, like almost any Java program I ever met.
It's a lot faster now that it used to be around 2002+ with the Swing of the day, but still lags perceptibly behind C/C++ for UI work. And don't even think using it for a multimedia app (video/sound) etc, or a game, except if you delegate all the work to a hardware accelerated C/C++ 3D backend.
I know that ARC was recently added to Obj-C, but you can still accidentally harm yourself even with such simple tasks as adding items to array. If you need to deliver your app fast then sluggish (Java) is better than not working at all.