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.
Vitaly Friedman loves beautiful content and doesn’t like to give in easily. Vitaly is writer, speaker, author and editor-in-chief of Smashing Magazine. He runs responsive Web design workshops, online workshops and loves solving complex UX, front-end and performance problems in large companies. Get in touch.
It’s been quite a journey for this very sentence to wind up on this little website. Not many people know it, but every single Smashing article goes through a thorough editorial review, including multiple passes for editing and refinement, before being published.
In this series of articles dedicated to our upcoming 10th anniversary (mid-September 2016), we’d love to shed some light on our editorial process, explain our workflow and introduce the people behind the scenes, as well as address how our little company is earning money to keep the website alive and running.
“Be agile; release early; release often.” We know the drill. But is it strategically wise to keep rolling out features often? Especially once a product you’re building reaches a certain size, you probably don’t want to risk the integrity of your application with every new minor release.
The worst thing that can happen to your product is that loyal users, customers who have been using that one little feature consistently over the years, suddenly aren’t able to use it in the same convenient way. The change might empower users more, but the experience becomes less straightforward.
You can’t be extraordinary in every project, but knowing how and when to break out of the box can go a long way. The upcoming SmashingConf Barcelona, taking place on October 25–26, will be packed with smart solutions ranging from front-end to visual design to UX — and a few delightful surprises along the way. To the tickets.
How do we avoid common traps in UX and front-end development? How do we break out of the predictable, generic, boxy layout? How do we solve complex problems more efficiently? With the second conference in magnificent Barcelona, we'll explore practical techniques and design patterns from real projects.
Design patterns often have a bad reputation. They are often considered to be quick, lazy, off-the-shelf solutions that are applied blindly without consideration of the context of a problem. Solutions such as the almighty off-canvas navigation, the floating label pattern or carousels for featured products are some of the prominent ones.
This article isn’t about these patterns, though. This article features some of the slightly more obscure design patterns, such as responsive car-builder interfaces, mega dropdown navigation, content grids, maps and charts, as well as responsive art direction. Please note that this article isn’t technical; it explores interesting UX patterns out in the wild, rather than code samples. Beware: You will not be able to unsee what you are about to see, and that’s probably a good thing.
So how do you sell a design system to the client? How do you establish a shared commitment within the company to put a pattern library on the roadmap? As designers and developers, we often know and see the benefits of an overarching system that radiates consistency throughout the different experiences of a company. But sometimes it's seen as a very unpredictable investment, and the value isn't necessarily visible right away.
In his article on Selling Design Systems, Dan Mall suggests to illustrate how fractured an organization is by printing out its different presences online and putting them on a large board as an example of all the wasted money and effort that goes into making sites from scratch, one-by-one, needlessly reinventing the wheel every time.
This upcoming September, SmashingConf Freiburg will be taking place on Smashing Magazine's 10th birthday and, well, we definitely wouldn't want to celebrate it all alone.
Freiburg is the smallest of all our conferences; this means a super-friendly atmosphere right at the foothills of the magical Black Forest, but also not that many seats! So, are you ready to celebrate with us?
You know how it works: you spend hours trying to find a workaround for a problem that you have encountered, just to realize that it doesn't quite work in, you know, that browser. Finding little techniques and tricks to help you get to results faster can immensely improve your productivity, so you don't have to waste time on solutions that will never see the light of day.
I love finding those little useful front-end goodies that make our lives easier. Since technologies emerge and evolve permanently, keeping track on what's going on is often difficult, especially since specifications change and so does the browser support. For a replacement talk at SmashingConfOxford last week, I've decided to collect some of the useful techniques from various articles, conversations and my workshops in a slide deck — and since it proved to be useful for many front-end developers I've spoken to after the talk, I'm very privileged to share it with the entire community as well.
Desperate times call for desperate measures. In attempts to fight back against the growing adoption of ad-blockers, many publishers and ad-dependent websites adopt all kinds of techniques from introducing "light" paywalls to limiting access to the site to fully blocking ad-blocker users from accessing the content altogether.
It seems a bit ironic that a website would send away potential customers that are taking measures to actually access the site faster, and read the content published on the site without annoying distractions. Don’t get me wrong: publishers need to earn money, and in most cases advertising is still the most efficient way of doing this. We know it better than anybody: with our smart tech-savvy audience, the ad-blocker usage has grown from 12% in 2012 to 55% today (as of March 2016). That’s a huge growth, and it’s a tendency that hurts us massively.
Guess what: those tricky mystery riddles are never easy to design. The idea has to be evaluated and brought into life, just to be crashed by painful user tests and then adjusted over and over again until it's easy enough to solve — but difficult enough to not solve fast.
When we started out with riddles, we wanted to have an entertaining yet challenging game that wouldn't be easy to crack, and would keep our dear readers busy for quite some time.