In a recent Offscreen magazine issue, Eric Meyer, a famous consultant, author, and web designer explains why he stopped calling himself a “web designer” and prefers the title “experience designer” instead.

In the realm of the design world today, the term “web design” has become something of an understatement, especially when we look at where web design has come from compared to 20 years ago.

The traditional idea of web design has evolved tremendously, especially in the last couple of years. The web is all around us, no matter if we think about smart bubbles, glasses, or other IoT devices. I guess the pioneers of the web, would be surprised in which devices web design can be found nowadays.

On September 7th, 2016, Divi 3.0, as a new way to build WordPress websites, was released.

Divi 3.0 not only brings WYSIWYG-style editing to WordPress but it also makes building WordPress websites way easier. Doesn’t matter if you’re a WordPress developer or a complete newbie, you should definitely consider Divi 3.0.

WordPress is a great tool. In fact, about 50% of all websites out there use WordPress. So, it’s no wonder that when you’re thinking of starting a blog for your company or simply develop a new website, WordPress is one of the first things that comes to mind.

But it isn’t all sunshine and rainbows and sometimes, you’re better off looking elsewhere. At least you should consider other alternatives to WordPress before getting starting without losing even a thought.

I’m super happy to work with a company that puts a lot of energy into the quality assurance part of every single software development project.

Quality assurance is a discipline that’s overlooked and under-appreciated. We produce software, share it with the team, test it, collect feedback, ask beta testers and then do it over again. Share, test, collect, ask, repeat. Yup, that’s pretty much it.

Yet people treat quality assurance as something superficial – a few tests here, a few user feedback there, and with one big eye staring at the release button.

Building a global SaaS product isn’t easy. You have to localize your product, translate your website, and make sure that everything’s still up and running.

And there might be a major interface problem, which looks like a tiny thing at first but is actually something to think about a little longer. What I’m talking about is the visualization of selecting a language. How can you visualize the option to change languages so that your global audience can choose which language they want to use?

In this article, you’ll find everything you need to know when it comes to designing a language switch for your application or website, including some examples and best practices.

A lot has been written on how companies can grow their business through customer success. The terms “customer success” or “customer experience” seem to be the new buzzwords in the growth-driven tech world.

These discussions are great, and we at Usersnap believe that customer support and customer success are important factors when it comes to business success.

However, I do believe that some basic and core questions remain unanswered. And one of these questions is this:

Is email still the best customer support channel?

We at Usersnap love 404 pages. Don’t get me wrong. We don’t want our website visitors, customers, and users to see our 404 page. Because it would mean that something went wrong. A broken link or some other mixup.

But if someone happens to see our 404 page, she should get at least some fun out of it. And luckily we’re not alone here. More and more software companies are putting fantastic 404 pages out there.