Dave Latta

#DaretoShare24 reignited my creative side❤️‍🔥 Thanks for getting this going @bentenwoodring! Illustration created in @figma New on X so really appreciate ❤️ and 🔄 🙏🏽

@bentenwoodring Expect fire. Also curious to see those scroll depth metrics.

Designing the longest web page of my life over here

It'd be great if we could set base values in CSS as you've laid out and use a CSS filter to force accessibility. (If this exists I haven't heard of it yet) Concept: .icon-brand { background-color: var(--color-brand-primary); /* Set base color value*/ filter: force-contrast(3:1); /* Force 3:1 contrast across any bg*/ } a { color: var(--color-brand-primary); /* Set base color value*/ filter: force-contrast(4.5:1); /* Force 4.5 contrast across any bg*/ }

Been thinking a lot about the volume of variables we create in systems and whether there's a way to consolidate them massively by using...opacity I'm still hung up on the efficiency of primary/secondary/tertiary labels 🤔

Yeah, sure. Here are a few examples where icons are defaulted to 3:1 for a more subtle default and text is defaulted to 4.5:1. I'll grant that differences can look subtle but if accessibility is an imperative then this is a decent approach that provides more flexibility especially for fine tuning "what feels right" across modes.

@dave_latta Do you have cases where your icon and text combos have different darkness/lightness then? Would love to see an example

@nathanacurtis imo teams or projects adopt and people who use ds resources are users. I think about it like this because tracking metrics and conducting research at each level is different.

Can we norm on what we call those that our design systems are for?

@rogie I created these in Figma earlier this year.

Who uses Figma and vectors like whoa these days? I wanna see who pushes its limits for product illustrations, art, and rich visuals.

@miggi @figma Love the way you used the geometry of the building. Very cool.

Hello Times Square, but say it with a @figma prototype. 👋🏽

@kyleanthony Hell yah 👊

5 mile run to end the day

@ethansuero_ @figma I carefully name every layer in a component library. But that’s the only situation.

Am I the only designer naming layers in @figma?

@itsdesignertom More often than not I see this used as a rhetorical question following an opinion rather than a sincere question. It often translates to: “You obviously agree with me, right?”

Hot debate on in my TT video comments going down right now: Is “Does that make sense?” passive-aggressive?

@itspatmorgan “Cognative load”. I know what it means but I still get second-hand embarrassment whenever it’s used.

Which design terms baffled you when you started your career? I'll go first: "Affinity Mapping"

@disco_lu Really wish I could!

@dave_latta Show usssssss

I'm in a hellhole of colour contrasts and variables and modes, please send snacks

@HonzaTmn 😂

Designers and engineers trying to get dedicated time for design systems work

@pablostanley @figma You have a rare gift for keeping people engaged. Good vibes 😎

multi-edit by @figma

I’m in favor of prioritizing discoverability over variant construction. Cramming all options under one variant group forces users to explore all props to figure out what the options are. Putting component “types” in separate variants shows users at a glance the major options available. That said, in your example, I’d consider these “styles” because it’s just a color change. A “type” would be a difference in construction or use case. Example of “types” might be: article card, profile card, data card.

Okay my favourite question – should component types be split into separate variants, or bundled as one? Or, a third option? Possible a neutral style, where you apply overrides at the instance level

Late last year I broke my ankle running. I was just a few miles away from a new personal best. Wanted to quit for good. Yesterday, early into a run I wanted to quit but managed to push thru it. It reminded me that overcoming your own mind is one of the best reasons to run.

@jina I attended Clarity back in 2019 and recall @beep’s standout talk calling for unionization because designers and devs were being tasked with working themselves out of a job. That seems, at least partially, to have come to fruition with AI.

publishers shutting down. indie conferences cancelling. continued layoffs and professional development budgets slashed. I can't help but worry about the future of learning in the indie design & dev communities. At this rate, all that will be left are corporate marketing efforts.

From my experience, when design is truly democratized, outcomes tend to be mediocre because the output is a compromise between many people that don’t share the same expertise or tastes. At some point you have to just get something out there usually by giving everyone a little say and calling it an MVP. The other issue is that democracies are designed to be slow with the hope that progress is gradually made over time. Not sure this is the best model for rapid innovation or progress. Of course, there are outliers. And as a caveat, I have seen many out-of-the-box, creative ideas by including everyone in the ideation phase of design.

I'm all for collaboration and inclusiveness in design activities, and work hard to get everyone's voice heard. Yet, across all my roles: designer, architect, manager, leader, business owner, consultant, one reality remains true: Design is not a democracy.

@pwnies For line-height I prefer ems which are relative font-size. It’s essential a percentage though

% or px for line height?