We've improved our editor to make it easier to take notes and work with your team. You can now pull quotes from transcripts into your interview notes, you can download images that you've added to your interview notes, and we've made it easier to write notes using markdown.

Easily keep your customer interviews organized with our new Tag system. Use tags to keep track of anything from different types of feedback and personas to features and products. You can even add your own custom tags.

Status Page We have released a status page to track the health of our services. This page will help us improve and debug our app while we…

You can manage your account and your workspace in Clarity Hub with our new admin tools. We've been working to make it easy for you to onboard your entire team onto Clarity Hub so you can share interview notes, recordings, and transcripts with each other.

What is a regular expression Denial of Service and how do we protect against it? Let's investigate and discover how innocuous regex can take down our servers.

Clarity Hub uses machine learning and natural language processing to provide APIs that make it easy to create language driven products…

We use Open Source projects every day – React, Tensorflow, Express, the list goes on. The least we can do is give back to Open Source. But you don't need to contribute code to help out the open source community. Here are some quick ways for you to help your favorite Open Source project!

Design systems are made up of foundational styles, components, and patterns. By using the principles of affordances and signifiers, we can design effective elements for our applications that are easy to understand by our end-users.

At Clarity Hub, we've decided to evaluate our existing applications and go through their designs to make a better overall experience for our customers. In order to do this, we had to rethink our current design system, how we implemented it and how we will craft a better design system moving forward.

Back in 2014, I was part of a small team that was in charge of maintaining dozens of websites and applications for the Global Institute it Sutainability at Arizona State University.

The key to creating maintainable code is adhering to “low coupling, high cohesion”. But what exactly does this mean? At what point is your code loosely coupled and highly cohesive?