OK, I get it. You have an excellent team of developers, designers and project managers. You develop a great piece of software for a client. And you test it. Of course.

That is one awesome application. But then, when the application reaches the client’s end, bugs are popping out everywhere. Boom.

Despite all your best efforts, bug reports are coming in. So what’s the issue here?

We at Usersnap are always looking for new ways and workflows in order to be more productive.

This week our UI / UX designer Benedikt worked on some new design drafts. Instead of using a traditional approach of prototyping we ended up using Facebook Origami.

In this post we are going to share some key takeaways and lessons learned for getting started with Facebook Origami. Check out our Facebook Origami review.

OK, I get it. Everyone wants to get high quality at no cost. Right?

It is particularly in software that we see a clear trend towards outsourcing. This is nothing new.

Because of the increasing average salaries of developers and the difficulty in finding qualified engineers, many companies are welcoming the idea of outsourcing.

When it comes to testing, outsourcing might also look like an easy win. Promised high quality at no (internal) costs. Awesome.

But before you consider outsourcing for your company, I recommend that you ask yourself the following questions.

As a recent blog post detailed, agile testing is just as beneficial for web development teams as it is for software teams. In fact, a recent report from the Harvard Business Review shows that agile is “the” advantage for businesses in the digital age.

Of course, knowing that is one thing; applying that knowledge can be slightly trickier.

At Clearvision, we specialise in tools and processes that help companies go agile. In building Spectrum – a scalable, customisable platform designed to bring together the best tools and processes for collaboration – and through our close work with enterprise companies around the globe, we’ve picked up more than a few tips along the way.

It’s all about communication and collaboration. Here’s our guide to breaking it down and making it manageable. Go agile by considering the following 3 stages.

This year’s TYPO3 conference was held in Amsterdam and Usersnap participated for the first time. After two exciting days of talks and great sessions, I’d like to give everyone a peek into the TYPO3 universe.

This is not a review of any particular talk or session but more of a personal glimpse into the world of TYPO3.

When interacting with our customers and blog readers, we usually find that everyone has a different set of ideas on proper user testing workflows. Blame it on the inconsistencies when it comes to the terminology of User Testing, Usability Testing or User Acceptance Testing. The need for clarification on this topic is certainly huge.

In this blog post, I will try to bring some light into the fields of Usability Testing as well as User Acceptance Testing. I will also highlight the main differences of both areas. Check out what user testing is all about.

A while ago – in April 2015 – we launched bugtrackers.io as a small side project. Since then, the site has grown from a three-pager to a website with dozens of interviews.

The increasing number of pages & therefore line of code made us look for ways to improve our internal workflow.

We also ended up using GoHugo as our main website framework for bugtrackers.io. In this post I’m going to share some of our first experiences with GoHugo as well as our path to ending up where we are right now.

You’ve finished some design drafts for a new website. You’ve even shipped those new designs to your website. And now you wonder what people – your website visitors – think about those new changes.

In this post, I’m going to show you 9 creative ways to ask your website visitors for feedback which will help you increase the quantity and quality of gained feedback.

… or how to be the first one who gets going with agile testing.

When working on digital projects and products, you probably encounter the term ‘agile‘ a lot.

The word agile is widely used (and sometimes misused). It refers to the methodology of project management which strives to establish certain principles of collaboration, flexibility and transparency. It emphasizes the importance of feedback throughout the entire development workflow.

So when it comes to testing, web development teams go back to traditional approaches rather than following the agile path.

In this post, I’ll give you an overview on agile testing as well as some useful guides on how to get started with the idea of agile testing.