Design Icon

Design

162 Stories
All Topics

Design openmoji.org

OpenMoji – open source emojis for the rest of us

At the moment, there is only a dozen emoji sets, most of them from big tech companies. These emoji are visually adapted to the respective appearance of their software platforms. In addition, the usage rights are often very restrictive (e.g. the terms of use of Apple’s emoji).

That is why we have developed OpenMoji as the first open source and independent emoji system to date. When designing the OpenMoji system, we have developed visual guidelines that are not linked to a specific branding. In addition, our goal was to design emojis that integrate well in combination with text.

A collaboration of 60+ students and 3 professors from HfG Schwäbisch Gmünd.

OpenMoji – open source emojis for the rest of us

Slack Engineering Icon Slack Engineering

How we design our APIs at Slack

This is quite a resource coming from a team whose API has always impressed me.

If APIs are designed well, developers will love them, and can become the most creative innovators using your APIs. They will invest heavily, and sometimes even become evangelists for your APIs. We also value a developer’s time and the resource they risk by building on our platform. Bad API design leads to a bare minimum adoption, and even frustration. Bad APIs become a liability for a company.

They share their six design principles as well as the process they follow through to implementation. A must-read for anyone who designs and builds APIs for fun and profit.

Vue.js primefaces.org

PrimeVue – the ultimate Vue UI component library

Thanks to Lars-Erik Roald for submitting this. Here’s Lars:

It is the most comprehensive suite I have ever seen. Especially the datatable component is really impressive. Personally, I have absolutely no relations with Primetek. I just think it is a pity that PrimeVue goes off the radar.

He also provided this getting started video for you to check out.

Una Kravets web.dev

Web design in a component-driven world

Responsive design is evolving. Una Kravets:

Today, when using the term: “responsive design”, you are most likely thinking about using media queries to change layout when resizing a design from mobile size, to tablet size, through to desktop size.

But soon, this perception of responsive design may be considered as outdated as using tables for page layout.

“Responsive” used to mean a web design would respond based on the size of the device accessing it. In the not-so-distant future, it will mean a web design responds to the preferences of the person, the container its placed in, and to the many form factors (including folding screens) it encounters. Exciting times!

Web design in a component-driven world

Thoughtbot Icon Thoughtbot

Designing for failure

Stephen Lindberg takes cues from the level design in Super Mario 3D World and applies it to user experience design:

You may not know what a Conkdor is, but the design problem is universal: “how do we reduce cognitive load without sacrificing interest and fun?” To summarize the video, game designers would approach the problem like this:

  1. Introduce a new concept in a way that the player is not punished for failing.
  2. Build upon that concept in a way that challenges the player.
  3. Combine the concept with other familiar concepts to put a new twist on it.
  4. Give the player a reward!

Design geofcrowl.com

A collection of human interface and software design guides

Geof Crowl:

After posting about the OpenStep User Interface Guide, I started to wonder how many different human interface guides or software design guides that I could find from the past and present. It doesn’t seem like there’s a good collection of these anywhere on the internet, especially in regard to past software design guides. I think there’s a lot of value in these even outside of just being a historic reference.

An excellent starting place, whether you’re looking for help designing your UI or help designing your UI design guide.

Increment Icon Increment

What the history of HTTP status codes can tell us about the future of APIs

Darius Kazemi writing in Issue #14 of Increment magazine:

HTTP status codes are largely an accident of history. The people who came up with them didn’t plan on defining a numerical namespace that would last half a century or work its way into popular culture. You see this pattern over and over in the history of technology.

Because technology isn’t immune to historical contingency, it’s important for us as engineers to remember that long-lasting technical inflection points can occur at any time. Sometimes we know these decisions are important when we’re making them. Other times, they seem perfectly trivial.

0:00 / 0:00