[ygra]

(Disclaimer: yWorks employee)

If you still have that graph somewhere, we'd love to see it. We're always curious (and sometimes surprised and astonished) what people create with yEd.

As far as competitors go, there are lots of other options, both in end-user applications for graph editing, as well as libraries.

For end-users it seems many stick with the first tool they really like and get used to its features, strengths, and idiosyncrasies (and from my experience there are many weirdnesses among those applications, including our own). Automatic layout may be a killer feature for our offering, though. As far as I know there is not much that can compare here (although for many people simple hierarchic or force-directed approaches may suffice and they might not need every option).

For library users it often comes down to a decision based on required features, cost, custom development effort, and target platform. I think we're well-situated for customers where cost is less of an issue, that have competent developers and require extensive customization (and support). It's not uncommon that D3 might be a better choice, depending on the requirements.

[fedups]

Thanks for the response! FWIW, I find nothing lacking in the application, but I'm working on an ipad and it seems a native app would be less constrained by the browser quality.