Flag

We stand with Ukraine and our team members from Ukraine. Here are ways you can help

Get exclusive access to thought-provoking articles, bonus podcast content, and cutting-edge whitepapers. Become a member of the UX Magazine community today!

Home ›› Business Value and ROI ›› 6 Key Questions to Guide International UX Research ›› What Should Experience Designers Understand About Developers?

What Should Experience Designers Understand About Developers?

by UX Magazine Staff
2 min read
Share this post on
Tweet
Share
Post
Share
Email
Print

Save

The winners of our JavaScript & jQuery giveaway share their thoughts on what designers should know about the work developers do.

Last month we announced a contest with Wiley to give away five copies of JavaScript & jQuery: Interactive Front-End Web Development, by Jon Duckett. To enter, we asked readers to give us their answer to the question: “What’s something every UX designer should try to understand about the work done by developers?”

Though the work designers and developers do in digital product design is directly related, there is often a disconnect between the two roles. While the occasional purple unicorn can bridge the divide and work effectively in both realms, there remains some shadowy confusion about what designers and developers are responsible for separately, and where their responsibilities overlap. We figured that folks interested in a book on JavaScript and jQuery might have some insight into this disconnect, and below you can see the responses from our winners (and also join us on a video flip-through of the book).

“UX designers need to understand that developers approach [projects] from a functionality standpoint; often concerned more about features and functionality than intuitive design. They may also be so wrapped up in debugging and creating clean code that they never take a step back to consider design and the user experience. Both are necessary for a good product and cooperation and an understanding of the challenges from each side can create harmony.”—Jennifer Midkiff-Mitchell of Cincinnati, Ohio

“Developers also know how to use a dry-erase marker.”—Russ Gossett of Boston

Developers also know how to use a dry-erase marker

“UX designers should keep in mind that (good) developers are also designers: They design code in a way that makes it easier to add new features and easier to fix bugs, and makes it less prone to performance issues. All with the same goal: to deliver an optimal user experience.”—Robin Zuiderwijk of Leiderdorp, The Netherlands

“UX designers should try to understand that the work done by developers is usually done by evaluating interfaces based on certain patterns they’d see every day, on a more technical basis, possibly causing certain design considerations to be left out.”—Lamar R. Glenn of Philadelphia

“UX designers should know at least the basics of coding so they understand what the product they’re creating is made of—like an architect, who knows exactly which materials to use for each part of the building.”—Matej Latin of Trier, Germany

Excerpted with permission from the publisher, Wiley, from JavaScript & JQuery: Interactive Front-End Web Development by Jon Duckett. Copyright © 2014.

Image of origami unicorn courtesy Shutterstock.

post authorUX Magazine Staff

UX Magazine Staff
UX Magazine was created to be a central, one-stop resource for everything related to user experience. Our primary goal is to provide a steady stream of current, informative, and credible information about UX and related fields to enhance the professional and creative lives of UX practitioners and those exploring the field. Our content is driven and created by an impressive roster of experienced professionals who work in all areas of UX and cover the field from diverse angles and perspectives.

Tweet
Share
Post
Share
Email
Print

Related Articles

Learn why your badges and streaks won’t wow kids raised on Minecraft.

Article by Montgomery Singman
Gamification 2.0. Beyond Points and Badges: Designing for Players, Not Metrics. Chapter 4: Special Considerations
  • The piece explains that young users, trained by thousands of hours of expert game design, can smell fake gamification at a hundred paces.
Share:Gamification 2.0. Beyond Points and Badges: Designing for Players, Not Metrics. Chapter 4: Special Considerations
4 min read

Learn about the most difficult challenge for designers in Agile.

Article by Paivi Salminen
The Part of Agile Designers Fear the Most: Imperfect Work
  • The article argues that designers aren’t afraid of shipping imperfect work; they’re afraid of imperfect work remaining imperfect because teams tend not to come back to improve what they’ve already shipped.
Share:The Part of Agile Designers Fear the Most: Imperfect Work
4 min read

Find out why slapping gamification on your product without first selecting a genre is the silent killer of your engagement strategy.

Article by Montgomery Singman
Gamification 2.0. Beyond Points and Badges: Designing for Players, Not Metrics. Chapter 3: The Framework
  • The article argues that “adding gamification” without selecting a genre is akin to “adding music” without referencing jazz or heavy metal: a category error that most product teams never realize they’re making.
  • It contends that different game genres are not just aesthetic choices; they are fundamentally different motivational architectures, and mapping your product to the wrong one is why most gamification fails.
Share:Gamification 2.0. Beyond Points and Badges: Designing for Players, Not Metrics. Chapter 3: The Framework
19 min read

Join the UX Magazine community!

Stay informed with exclusive content on the intersection of UX, AI agents, and agentic automation—essential reading for future-focused professionals.

Hello!

You're officially a member of the UX Magazine Community.
We're excited to have you with us!

Thank you!

To begin viewing member content, please verify your email.

Get Paid to Test AI Products

Earn an average of $100 per test by reviewing AI-first product experiences and sharing your feedback.

    Tell us about you. Enroll in the course.

      This website uses cookies to ensure you get the best experience on our website. Check our privacy policy and