We use ad-blockers as well, you know. We gotta keep those servers running though. Did you know that we publish useful books and run friendly conferences — crafted for pros like yourself? E.g. upcoming SmashingConf Barcelona, dedicated to smart front-end techniques and design patterns.
This category features articles on general design principles, Web design, typography, user interface design and related topics. It also presents design showcases and practical pieces on the business side of design. Curated by Alma Hoffmann.
How do you make sure all the software products you spend time building are something that your customers will actually want to buy? It's one thing to spend a few weeks coding your next big idea. But are you sure that you have an audience of customers that want what you've built?
The last thing you want is to create something, invest in Adwords, only have your potential customers arrive non-plussed, and then navigate away, never to return again.
The history of the Internet has been a steady march towards websites that are richer, bigger and more interactive. As websites have become more robust, we — as designers and developers — have often placed the burden on our users to make more decisions, each of which distracts them from their wants and needs.
However, by using a combination of technical solutions and some careful decision-making on our part, we can often remove interface barriers for our users.
Do you remember those “10 Useful Legal Documents for Designers?” Well, it turns out that you, designers who read Smashing Magazine, liked one in particular: a plain-language, straightforward “Contract of Works for Web Design” which is based heavily on Andy Clarke’s “Contract Killer”. Since Mr. Wong published that template eight months ago, almost 1,500 designers have downloaded it on Docracy alone.
Why is this legal template so popular? Does it really work better than other contracts? Can it help you close that job faster and protect you from getting stiffed? Could it become an industry standard, like grid systems and agile development?
The ambigram is one of the few modern letterforms that engage both your intellect and intuition simultaneously. It reads as a word while also communicating a deeply familiar pattern. This is something beyond the ambigram’s obviously clever construction. I’ve thought quite a bit about why I love this word-image hybrid, and I’ll set out here to uncover just what it is about the ambigram’s design and structure that makes it so captivating.
My primary design background is as a symbolic logo designer, so I begin with what I know: symbols. I look to nature to create my work as a matter of practicality as well as aesthetics, because symbols are derived from nature and are the first language of all humans. Symbols engage us deeply as expressions of the organic principles and forms that life embodies. Nature is common to everyone, and when it is used symbolically in visual language, the chance of creating a relationship with the audience is significantly elevated because it mirrors the relationships within and around us. Nature even embeds symbols that mirror universal processes directly in our DNA.
As a Web professional, you can get great inspiration from a good conference session. While conferences may not bring value to all industries, the Web industry is stacked high with inspirational experts and quiet little geniuses beavering away from small home offices. A good Web conference shines a light on these clever souls and promotes professional growth and shared knowledge.
The number of conferences surrounding the Web design and development field continues to grow as new processes, techniques and other shared experiences, turned learning opportunities, are always presenting themselves throughout the industry. The problem becomes, with so many conferences that are out of reach for one reason or another, how does one catch the highlights from the conference that won't fit into a 140 character tweet?
The rapid pace of UX design in the agile world can lead to shortsighted design decisions. Focusing on addressing the immediate needs of particular user stories within the limits of a sprint can lead to neglect of larger design questions, which can come back to haunt UX designers later.
Sometimes, UX practitioners just need some time to work through big design issues that don’t fit neatly into an existing user story or an individual sprint. This article will explore one answer to these problems — namely, design spikes, an agile approach that I have developed for large projects. Design spikes, which are bubbles of time that allow designers to focus on complex UX issues, can fit comfortably within the scrum framework and can be an effective tool for designers who have holistic design questions whose answers could potentially invalidate the work being tackled by the team.
We tend to think of navigating a website as clicking from page-to-page via some kind of global navigation that's always visible. When it comes to a single page, we often think scrolling is the one and only way to move from one end to the next. Sometimes global navigation and scrolling are the best, most appropriate ways to move about, (however, they aren't the only ways).
The websites in this article let you scroll, but they also provide alternative ways of finding cues and means for getting around. In several cases the designs encourage exploration, which is both more engaging and also teaches you how to navigate at the same time.
I have an idea for a new product — can I tell you about it? It will take months to develop, and even though this kind of thing is usually given away for free, I’m going to charge for it. Oh, and the market for it probably won’t be very big… Wait, come back! Where are you going?!
It does sound like a crazy idea, but it’s exactly what a small group of designers and writers have been doing for the past year or so. On a Web littered with SEO-ified headlines (“17 Jaw-Dropping Responsive Design Templates and Funny Cat Pictures”), easy-to-share design gallery slideshows and quick tutorials that help you recreate the latest texture fetish in Photoshop, these people are taking a step back from what we have now come to refer to as the “fast Web.”
Last week at the fabulous Smashing Conference in Freiburg, I gave a new talk, one I’d written just a few hours prior. I chose not to use slides, but instead to speak about three things that I’m incredibly enthusiastic about: Responsive design is not (just) a design or development problem; the client participation process is broken; how to call your client an idiot, to their face. Here are the (slightly expanded) notes that I made before my talk.
In all the excitement about responsive Web design over the last few years, someone forgot to tell our bosses and clients, so we’ve been treating responsive design like it’s a design or an implementation problem, whereas in fact it’s as much an issue for business. In fact, it’s an issue for everyone involved: designers, developers, content specialists, the people who commission websites and those who structure the teams who make the websites.