Resources

Tips, tutorials, guides, and product insights from Fullstory experts

Software Engineering
Filter by Industry
Filter by Type
Blog Post

Lessons from Google: How code reviews build company culture

What are code reviews, and why are they important to Fullstory's culture? Learn how this tradition benefits employees and customers alike.

Read the post
Blog Post

The 7 causes of bad user experiences

What bad web design drives frustrating user experiences? Go to school on the 7 primary drivers of bad UX.

Read the post
Blog Post

Fullstory Helps Education Company Save Over 500 Hours of QA Work

Bug reproduction is time-consuming, and expensive. GenM is using Fullstory session replay to reproduce bugs and fix them fast, saving time and money.

Read the post
Blog Post

How Fullstory Drives Conversions for Car Insurance Company

Metromile uses Fullstory session replay to understand complex UX flows as well as optimize conversions with A/B tests using Optimizely.

Read the post
Blog Post

How Fullstory helps Shortcut save time

The Shortcut team shares with us how Fullstory session replay is used to diagnose bugs quickly and solve issues around design.

Read the post
Blog Post

3 ways Fullstory is indispensable in improving travel booking

Read how TST uses Fullstory in their production process to help capture and understand when things go wrong.

Read the post
Blog Post

How thredUP increases engineer productivity through session capture and error tracking

ThredUP, a growing online thrift store, uses a combination of Rollbar and Fullstory to solve A/B Testing mysteries, and do UI/UX research.

Read the post
Customer Story

Jumbo Interactive saves tens 
of thousands of dollars by identifying critical bug fixes using Fullstory

See how Jumbo Interactive identifies and resolves revenue-impacting bugs with Digital Experience Intelligence.

Read their story
Customer Story

Sendoso provides specialized support and innovates
new features with Fullstory

When a user experiences a problem, the Sendoso team can watch their session in Fullstory to understand if the problem is a bug or user error.

Read their story