UXPin Blog — Design Studio

Design systems insights from Github designer Diana Mounter.

Design systems advice from Dan Mall.

Get insights from Intuit’s Head of Design Systems.

Insights from a designer for Salesforce Lightning.

16 free webinars across 4 days.

Wireframes are dead! Interactive prototypes are everything! We’ve heard these shouts for at least the past 7 years. If the popularity of these discussions proves anything, it’s that the opposite is true. The mere fact that we continue to discuss the alleged death of wireframing proves that wireframing is doing fine and continues to exist

Design systems are products that enforce consistency while expediting development. But the default patterns don’t always cover every case — so they must adapt.

Like any project that involves UX, design systems must solve people’s pain points, like being able to find the right widget under deadline pressure. Here’s how it works.

Especially in hi-fi prototypes where the nuance between “save” and “submit” is fuzzy at best, you should customize buttons to fit your meaning.

While UXPin won’t sort data on your behalf, you can create a “sortable” table, if you don’t mind rearranging a few elements.

Documentation may sound like a chore, but it’s a vital part of creating a design system. And it doesn’t have to be a monotonous time-sink. Refer to these notes as you write yours.

Not all radio buttons are created equally. Some have custom looks and styles. Here’s one approach to creating your own radio buttons in UXPin.

Shortcuts are great — in moderation. Don’t let sloppy dev workmanship degrade your digital products. Instead, get code from the source.

Drop-down lists that appear on hover are a great way to hide options until they’re needed. A handy technique to make them work in UXPin: group ’em twice.

Design systems do more than provide visual and interactive style guides to which teams should adhere. They also make their contents easy to find. After all, UX doesn’t just apply to non-designers.