More and more SaaS businesses are taking off the ground today. And it’s great.

The SaaS business is a super-fast growing industry attracting more and more people and companies. These organizations are more and more floating applications in the cloud. Scaling in the cloud has some essential benefits and risks as well.

In this article we are going to show you how to start building a cloud-based SaaS architecture, dealing with issues of scalability and what this means for your SaaS application.

‘Errors’ happen. They happen in our apps and they happen in our life. Sometimes they happen because we made mistakes. Sometimes because a system failed. Whatever the cause, these errors — and how they are handled — can have a huge impact on the way a user experiences your app. Often overlooked, a lazy error handling and ill-constructed error messages can fill users with frustration, and make them stop using your app. A well-crafted error handling, on the other hand, can turn a moment of failure into a moment of delight.

In this article, we’ll examine how the design of apps can be optimized to prevent excessive user errors and how to create good error messages.

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.

Reading through Microsoft’s 1995 Interface Guidelines is like unearthing a lost relic. The 381-page tome — for designers creating Windows apps — got me thinking about how much has changed, not only with Microsoft but with software overall. The guidelines are ahead of their time.

They’re concerned with helping the user get to grips with the OS, and there’s a focus on empathy and a hint Microsoft is starting to think about UX. That’s which isn’t something Windows 3.1 makes any effort to do. On first run, you’re thrown into this jumble:

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.