Modern product development is hard. The number of individual roles and titles that go into building a successful digital product at scale is mind-boggling. On the flip side, while we have more distinct specialties than ever, these lines are blurring and most individuals will usually straddle at least a couple of these. Seen as a continuous spectrum of skills, it’s clear that to succeed in today’s
In a recent code review, my passions stirred as I walked through a Pill component’s style with a designer teammate. I could hardly contain my excitement: “Look. Yes, it’s code, but look closely at those tokens. You know what this looks like? Like specs! So what? I can read this, as can you. And we can thread these everywhere: doc, designs, and convos too. Everywhere!“ My teammate’s reaction hinted
design system The Most Exciting Design Systems Are Boring By Josh Clark Principal, Big Medium Published Apr 3, 2017 Tweet Share Email Let us celebrate normcore design systems. We’re building another enterprise design system, and we’re super-excited to make it boring. Brad Frost, Dan Mall, and I have just begun helping a big company express and communicate a design system to govern their many web p
What Is the Purpose of a Design System?A design system is not just a collection of design artifacts; it’s a philosophy. To create a great user experience, product teams should understand not only what they need to build but also why they need to build it. That’s why design vision (in the form of a company or product strategy) and design principles (fundamental ideas about the practice of user inte
A great design system should equip you to quickly and confidently create delicious user experiences. Creating a great design system is a lot like stocking a very specific kind of kitchen. Let’s say I run a food truck. I have a small kitchen in said truck, so I need to be judicious in what ingredients I stock. To determine the right ingredients to bring along, I can ask myself a few simple question
There are many facets of a design system initiative, so it can be extremely daunting to figure out where to begin. There are stakeholders to educate, tools to choose, principles to establish, frontend guidelines to settle on, components to build, tokens to create, design guidelines to write, contribution models to sort out, and so on. In my workshops and consulting engagements, I’ll often have tea
Building on-brand, quality, and consistent digital products at scale is hard. It’s even harder when your designers and engineers span different product teams, departments, and locations. Success requires more than an assortment of PSDs, Sketch files, style guides, a print brand book, pattern libraries, InVision, and whatever else your team claim to be working from. You need a source of truth. You
With the exponential growth of Zomato, we had let a lot of design debt build up for the product. One of the major problems we were facing was that a lot of pages, products, features, and components were not in sync with each other in terms of UI and UX. This happened because all these parts of the apps were designed at different times, by different designers having a different context. There was n
Let’s be honest. The relationship between designers and the engineers who execute their designs can be rocky. A historical reenactment of the designers and engineers working together.Engineers get frustrated when designers design things that were “impossible” (read: would be hard to build, don’t play nice with the API, or are likely to cause cross-browser issues) and that it is the engineers who a
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く