Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I really hate this statement. You're asserting that because the project doesn't have somebody in a dedicated role they have bugs, unspecified issues, and subjective "problems". Not only is it a logical fallacy, it asserts nebulous "faults" that can't be addressed because they're so ill defined.

None of what you're asserting is true of Inkscape. I've been using it for 10 years and while the UI/UX isn't familiar, there's nothing wrong with it. It isn't chock full of bugs or "edge case" (whatever the hell that means) and like all UI/UX it has rough edges AND that's no different from any other sufficiently complex Application.

Does it follow Adobe's UI/UX paradigm? No. Is that bad? No. If you started out using an Adobe competitor in the 90s then you might be familiar with alternatives, that's where I started and I can't stand the UI/UX in Adobe products to this day.



Now, I agree that Inkscape has a fairly solid UI as far as OS software goes.

BUT, in general, UX and interaction design simply is not a reductionist process the way implementing functional requirements is. It is an inherently holistic endeavor, an art more than a science, and that is why it helps tremendously to have a single competent person in charge who has a vision of how things should work.

I understand that to the typical programmer mindset it is frustrating when people come and complain that the UI is clunky and unintuitive without being able to express their frustration as a list of actionable "this does A but it should do B" tickets. But that's just how it works! Understanding and empathizing with the users simply requires a different skillset than programming.


I don't think anyone disagrees that the interface is less than perfect for them. And there is no one ideal user interface for everyone.

That's how software goes, it's a conglomeration of all the features for all of it's myriad of uses. What would benefit one use case might be detrimental for another, and no one UI/UX developer is going to be able to fathom all of those different use cases or conceptualize a UI that's ideally suited for them all.

What you do often get with dedicated resources is a direction drive and clarity of vision that is not in line with what everyone wants and their UI/UX ends up driving people away.

I don't use half of what Inkscape has to offer and I use Inkscape for two very distinct and very different use cases. And for both of those use cases Inkscape is far and away the best piece of software.

For web development, Inkscape is my go to SVG editor. I don't use it as a vector drawing tool at all, if the drawing and filter capabilities went away it wouldn't matter much to me. But the ability to quickly manipulate canvas sizes, add and remove objects, and tweak paths is essential.

When I use Inkscape as part of a CAD/CAM solution engraving, the use case and what UI/UX elements are important is completely different than when I'm optimizing SVG Assets for the web. Certain UI/UX elements I require as a web developer could vanish and I wouldn't care as a CNC operator.

I'm reasonably certain that much of what I value in Inkscape isn't of much use to someone who is producing vector art.


It feels like it wasn't designed, but grew.


That's the nature of most mature sufficiently complex software. They don't start out as a set of user requirements cleanly laid out that are developed in a straight shot waterfall process.

Instead they grow organically over time and are a reflection not just how things are implemented but also of when they were implemented.


The difference is it with software that has product management, it can grow and shrink. Features can be dropped, deprecated, or re-worked into a more appropriate presentation. With OSS it seems like everything is additive, since you have no idea what users are using what features.

The blender 2.50 release was awful for me, since it broke so many of my workflows, but the UI absolutely needed a revamp, and I have incredible respect for the team throwing so much away to make something better.

I wish more open source software would delete more things in order to provide a better or more thought out user experience.

I’ll also note that telling users that their sub-par user experience doesn’t mean that the application has bad UX is foolish. That’s what user experience is. And it’s not a unique position; look at the comments here. The number one complaint is UX. These people ARE the users. I can’t imagine more direct feedback than that.


In the software universe I have always preferred intelligent design to evolution.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: