@tsrberry @joepie91 @baldur but ultimately at that scale you need input from actual designers - people who really know how to make a good UI/UX, and who can tell you what you can do better. that can be direct, by getting designers to come help with the project and help come up with better approaches and workflows, or it can be indirect feedback. and be humble. don't get defensive because you're attached to the project or it'll be work to fix the issues. it's hard work to do it right!
@gsuberland @tsrberry @baldur One thing I'd want to add to that is that if it's not feasible to find experienced designers (funding reasons, community politics, whatever reason), it *is* possible to just learn how to do this stuff yourself on-the-fly as a maintainer, but it makes the "be humble" part all the more important, and to make that work, you *need* to have an attitude of "if a user complains about something, that means there's a bug, even if it's not where the user thinks it is" (eg. it might sometimes be a documentation issue instead of a UX issue, but as long as people complain, there's *a* bug somewhere).
@gsuberland @tsrberry @baldur One thing I'd want to add to that is that if it's not feasible to find experienced designers (funding reasons, community politics, whatever reason), it *is* possible to just learn how to do this stuff yourself on-the-fly as a maintainer, but it makes the "be humble" part all the more important, and to make that work, you *need* to have an attitude of "if a user complains about something, that means there's a bug, even if it's not where the user thinks it is" (eg. it...