diff options
Diffstat (limited to 'build/avoid')
| -rw-r--r-- | build/avoid/index.html | 83 |
1 files changed, 83 insertions, 0 deletions
diff --git a/build/avoid/index.html b/build/avoid/index.html new file mode 100644 index 0000000..317d92f --- /dev/null +++ b/build/avoid/index.html @@ -0,0 +1,83 @@ +<!doctype html> +<html lang="en" id="top"> +<head> + <meta charset="utf-8"> + <meta name="viewport" content="width=device-width, initial-scale=1"> + <link rel="icon" href="data:,"> + <title>A Warning for New Designers: Avoid Dribbble</title> + <link href="https://bt.ht/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" /> + <style>*{box-sizing:border-box;}body{font-family:sans-serif;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{overflow:auto;}table{text-align:left;width:100%;}</style> +</head> + +<nav> + <a href="#menu">Menu ↓</a> +</nav> + +<main> +<h1>A Warning for New Designers: Avoid Dribbble</h1> +<p>2022-09-08</p> +<p>Everyday a new designer begins their journey into the world of [<em>insert design industry here</em>] and it is magical! Having a fresh pair of eyes untainted from the current trends of the time can help improve design as a whole. Newbies can even teach new things to older, grumpier luddites (like yours truly). But over the years I've noticed a concerning trend among junior designers; <strong>they rely too heavily on Dribbble</strong>.</p> +<p>Relying on Dribbble for minor inspiration is one thing. Referencing "shots" as justification for real-world design work? Not so much. I believe Dribbble shouldn't be used for either of these use cases, but I can at least give a pass at browsing for basic inspiration (colors, padding, layout).</p> +<p>Now, using concept shots to push for your own design decisions? That is a terrible idea. We "senior" designers need to step up and help newbies avoid this trap.</p> +<h3>Designing for Other Designers</h3> +<p>Dribbble is rarely a place for design feedback and discussion anymore. Hell, most people use it as a digital portfolio to share with prospective clients. Others use it like some form of "design Linkedin", which has its own host of problems.</p> +<p>Dribble is now (mainly) a place where designers post "work" for other designers. There <em>is</em> a small minority of users still looking for real, human feedback on their work - but they are a rarity.</p> +<p>Take a look at the <a href="https://dribbble.com/shots/popular">popular shots</a> category at any give time. Most shots are promo pieces used to attract potential clients. Nearly all design concepts are impractical or simply impossible to create in a real-life setting. This is incredibly damaging to newcomers trying to learn "good" design practices. Dribbble shots simply ride the wave of the current trends, which doesn't provide junior designers with a solid foundation or core understanding of design as a whole. It just causes them to endlessly chase the "latest and greatest" trend.</p> +<p>Shot posters rarely go into the reasoning behind their design decisions. No research or iterations are shared to show the process. Instead it simply states "here is a cool website layout for a company that doesn't exist". Zero constraints or goals needed to be met. No discussion about how one version of their design didn't perform as well when tested on real users. So of course it ends up looking <em>so cool and original</em> - <strong>it wasn't designed in reality</strong>.</p> +<h3>I Don't Have All the Answers - But I'll Try</h3> +<p>I am not the holy savior of <em>all things design</em>. I'm just a designer who has been around the block a few times. If new designers want to keep using Dribbble as their main source of guidance and think I should go kick rocks - that's fine. I will. But for those with a little more passion for the profession, might I suggest some humble alternatives to get you on a more consistent path?</p> +<ul> +<li>Read some good design books (to get you started): +<ul> +<li><a href="https://sensible.com/dont-make-me-think/">Don't Make Me Think - Revisited</a></li> +<li><a href="https://en.wikipedia.org/wiki/The_Design_of_Everyday_Things">The Design of Everyday Things</a></li> +<li><a href="https://www.edwardtufte.com/tufte/books_vdqi">The Visual Display of Quantitative Information</a></li> +<li><a href="https://www.amazon.ca/Dieter-Rams-Less-But-Better/dp/3899555252">Less But Better</a></li> +</ul> +</li> +<li>Talk to <em>real</em> people +<ul> +<li>Chat with your team's marketers, customer support specialists, senior design leads, and developers about new features (they often have better insights than you)</li> +<li>Perform customer interviews early and often (they use your product or service - let them tell you what they want!)</li> +</ul> +</li> +<li>R ad through some quality UX reports and research +<ul> +<li><a href="https://www.nngroup.com/">Nielsen Norman Group</a></li> +<li><a href="https://baymard.com/">Baymard Institute</a></li> +</ul> +</li> +<li>P y attention to real world design (good and bad) +<ul> +<li>Grocery item designs, labels packaging</li> +<li>Vehicle analog and digital dashboards / safety features</li> +<li>Warning and safety labeling (great for universal and minimal design inspiration)</li> +<li>Government websites and applications (notoriously terrible - great for "what not to do" examples)</li> +</ul> +</li> +<li>Your own experience (over time)</li> +</ul> +<p>These are just my own suggestions to help new designers get a better foundation of core design concepts <em>before</em> falling down the Dribbble hole. Take it or leave it. I'm not your dad.</p> +<p>Most designers who are pro-Dribbble will most likely write me off as a grumpy old man yelling at a cloud. That's only half true. But if just one person reading this even <em>considers</em> avoiding Dribbble as a source for learning proper design - then it was worth it.</p> +<p>Now if you will excuse me, there are many more clouds to yell at...</p> +<footer role="contentinfo"> + <h2>Menu Navigation</h2> + <ul id="menu"> + <li><a href="/">Home</a></li> + <li><a href="/projects">Projects</a></li> + <li><a href="/uses">Uses</a></li> + <li><a href="/wiki">Wiki</a></li> + <li><a href="/resume">Resume</a></li> + <li><a href="/colophon">Colophon</a></li> + <li><a href="/now">Now</a></li> + <li><a href="/donate">Donate</a></li> + <li><a href="/atom.xml">RSS</a></li> + <li><a href="#top">↑ Top of the page</a></li> + </ul> + <small> + Built with <a href="https://git.sr.ht/~bt/barf">barf</a>. <br> + Maintained with ♥ for the web. <br> + Proud supporter of <a href="https://usefathom.com/ref/DKHJVX">Fathom</a> & <a href="https://nextdns.io/?from=74d3p3h8">NextDNS</a>. <br> + The content for this site is <a href="https://creativecommons.org/licenses/by-sa/2.0/">CC-BY-SA</a>.<br> The <a href="https://git.sr.ht/~bt/bt.ht">code for this site</a> is <a href="https://git.sr.ht/~bt/bt.ht/tree/master/item/LICENSE">MIT</a>. + </small> +</footer>
\ No newline at end of file |