To be a successful cross-platform development environment, there would have to be lots of these. To my knowledge, only web apps are that widespread and used by the general public, not primarily for in-house apps.
So although end consumers might not see them, it will certainly take a long time for SWT or Swing to die. These are the same class of applications that are keeping IE 6 alive, after all.
Does this matter to Apple? I doubt it's significant, as most of these applications are probably running on Windows desktops already. Probably more significant is the legion of Java developers that have been vocal proponents of Macs over recent years. The numbers of such developers might not be so great in an absolute sense, but the amount of noise they create is disproportionate. And, more importantly, they are more motivated to build interesting stuff for the platform they use.
http://blog.backblaze.com/2008/12/15/10-rules-for-how-to-wri...
While the underlying logic should be the same, each UI should be leveraged towards whatever OS is running the app. It requires a bit of across-the-aisle thinking to create a decent UI for the other OS, but it's do-able.
UI design should be more like a cross-channel ad campaign (print, web and TV) than porting.
How about Kickstarter?
Desktop Java is a ruinously expensive legacy that they need to do something about.
All the angry screeds against Steve Jobs won’t change the fact that this is the “ball and chain” that’s pulling Java below the waves.
I think attempting to do cross-platform UIs held Smalltalk back as well. You either have Least Common Denominator native UIs that stink, or emulated UIs that don't look native. "Cross Platform" failed for the general public end-user. Web Apps took up their niche.