Community Debate

Has JavaFX Failed to Win over Designers?

Jessica Thornsby

“JavaFX is a train wreck,” writes Kirill Grouchnikov in a recent blog.

Kirill Grouchnikov has published a blog that makes his view of
JavaFX very clear. “JavaFX is a train wreck,” he writes.

According to Grouchnikov, the problem with JavaFX is that
designers simply aren’t interested. This has resulted in not “a
single significant JavaFX application that looks good.” He uses the
recent JavaFX RIA exemplar challenge rule-change as evidence of
JavaFX’s unattractiveness to designers. Originally, the challenge
required each team to consist of a developer and a designer, but
after a few weeks the rules were changed and a designer was no
longer a prerequisite.

He parallises this against Microsoft, who forged agreements with
companies when they released Windows Presentation Foundation (WPF,)
to create aesthetically-pleasing applications that showcased what
was possible with their UI toolkit. In Grouchnikov’s opinion, Apple
has also attracted plenty of designers, resulting in attractive
apps for the iPad and iPhone.

Some visitors to his blog have tried to pinpoint the disconnect
between JavaFX and designers. Scott Kovatch has theorised that the
problem is that potential JavaFX designers are tangled up with Flex
4.0 and Flash Catalyst, and until someone develops a Flash
Catalyst-style tool for JavaFX, designers will continue to opt for
Adobe. Meanwhile, Osvaldo Pinali Doederlein has suggested it could
be a matter of timing: JavaFX 1.0 shipped eighteen months ago, and
competing products already have a head-start.

The most recent release of JavaFX was version 1.3.


comments powered by Disqus