Sounds like the author wants his tools to be as fully featured as the code that will embody the resultant design. In that case I would recommend learning more code instead of relying on a proxy that will never be as flexible. The best designers I’ve worked with not only understand their own domain but the possibilities and limitations of how it will be executed, because they are also developers.
What design tools get wrong
81–84 of 84 posts
Re: What design tools get wrong
#82Sounds like the author wants his tools to be as fully featured as the code that will embody the resultant design. In that case I would recommend learning more code instead of relying on a proxy that will never be as flexible. The best designers I’ve worked with not only understand their own domain but the possibilities and limitations of how it will be executed, because they are also developers.
I've noticed this as well. The best designer I ever worked with was obviously great at design, but also great at css, she rocked! I've seen this more than once, but would estimate less than 10% of designers I've worked with actually took the time to learn css.
I think more designers should learn css, and more engineers should learn at least some basics of design. Then everyone could communicate better and get more done faster.
Re: What design tools get wrong
#83Earlier quoted context omitted.
When someone says HTML & CSS is terrible I ask them to design something better that lets you represent user interfaces that can adapt across multiple screen sizes, and allow complex layouts that Flexbox and CSS Grid makes possible. It is easy to criticize something if you don't have to worry how you would do it better. That said, HTML & CSS is just how the world currently is. It doesn't mean that it is the best possi…
Sure, can you whip up an easy 3 column layout for me using the parts of CSS that are fully standardized? CSS does a lot of things really well, but makes some common tasks way more difficult than they need to be.
https://jsbin.com/nedesuvozo/edit?html,output
The important two css classes:
.Example--outer-container {
display: flex;
flex-direction: row;
}
.Example-three-column-inner-container {
width: 33.333%;
}
Browser support: https://caniuse.com/#feat=flexboxRe: What design tools get wrong
#84Sounds like the author wants his tools to be as fully featured as the code that will embody the resultant design. In that case I would recommend learning more code instead of relying on a proxy that will never be as flexible. The best designers I’ve worked with not only understand their own domain but the possibilities and limitations of how it will be executed, because they are also developers.
Nothing in this article conflicts with the idea that a UX designer knowing how to implement their designs in code would be a benefit.
I don't see a problem with the author (and others like myself) wanting the tools to be more capable.
Have you developed a design system? Do you understand the context of this domain? I don't ask this to be rude, but the issues that the author mention are some of the key problems with the state of being able to maintain design systems.
It's more about the ability to efficiently generate and document the design intent and iterate on the design. This then needs communicated to the full team, whether that's stakeholders or the team implementing the design.
I think the authors suggestions are very good and valid.