Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
(not a designer myself btw)
Isn't design language mainly used to describe general things about how a design should work?
Take Material for example. Material itself is a design language, telling you how far apart certain click targets should be, how big text should be, stuff like that, to make a generally useable UI. It doesn't tell you what shape or what colour your button should be, that's up to the implementation, like Material UI, to decide, which is what I would call the general design.
"Material is a design, telling you how far apart certain click targets should be."
See, the sentence works without "language". Its addition makes it overstated and pretentious.
If you follow a design, you are following the guidelines of how something should look.
But it's a design for designs - it tells you how to design your own UIs, it doesn't dictate what for example a calculator app should look like. You can follow Material Design and still end up with a terrible UI design.
Surely that's enough for some distinction, right?
Sure the sentence works, but now you've lost the distinction between more of an abstract concept and a concrete implementation. It wouldn't be wrong to call both material and mui a design, but in conversation it can just be useful to have a little more distinction between the two without having to go into the details explaining it.
(also damn i should have chosen a better example than material, their naming is pretty confusing)
No, design and design language are two different things. A design language is a set of design rules that define a common look and feel across a product line. There’s usually a manual put together by a designer and their team defining what these commonalities are.
Look up “Apple Snow White design language“ for example.
They’re trying to solve one of the hardest problems in Computer Science: Naming things.
What do you call the framework, or design system—that thing that’s not quite a glossary of the terms—we’re going to use to describe the meta conversations around design?
“Design language” encompasses the colors, spacing, tokens, typography ramps, general rules, and all the other fiddly bits to unify on so that the more interesting parts of design and user experience can happen.
Naming things is hard :/