It’s a bold claim for me to say that every developer can benefit from something 40% of them haven’t heard of, but hear me out. I was among the 40% who didn’t know tracing existed until this summer. Still, I spent the last three months learning why it’s critical to a developer’s workflow and the different ways developers pragmatically use it. In this blog, I hope to show you that you can benefit from tracing regardless of your stack, role, size, or project.

Debugging Android apps has its unique challenges with crashes, ANRs, and inconsistent logs. But there are some easy ways to quickly identify and resolve issues, ensuring better performance and user experience. In this blog, we’ll explore basic tools and techniques to streamline Android debugging, talk about ANRs, and then go deeper with how Sentry can track errors and provide insights to help you prevent future issues.

As developers (and as front end developers in particular), we usually talk about web performance in the context of measuring what happens when we start to see things appear in a browser window, and when we can consume content or interact with the page.

For those who like to get straight to the point, here’s a quick summary of the latest noise-reducing improvements to the Issues experience: We’re feeling pretty good about these features. Might even go out on a limb and say they’re some of the most significant improvements to our error grouping and alerts ever. Need more convincing? Keep reading.

Twilio Flex is a React-based web app that lets you run your contact center as a service, and years ago, while working at a previous company, I was tasked with setting it up with Sentry for application observability and error monitoring. To help you set up Flex with Sentry— and using all the lessons I learned along the way— I’ve teamed up with Bruno, Solutions Engineer, from Twilio to build a new Twilio Flex integration.

Dan Mindru is a Frontend Developer and Designer who is also the co-host of the Morning Maker Show. Dan is currently developing a number of applications including PageUI, Clobbr, and CronTool. As a developer, few things are more frustrating than an API that’s slower than molasses. You know the code works, but you know it can’t possibly be a good user experience anymore. I had one of those and looked the other way for a couple of weeks. However, some issues become personal after a while.

Today we’re launching Fair Source, a new approach to software sharing that is safe for companies to adopt and developers to use. Before Fair Source, companies that wanted to engage the developer community with their core products often did not know how to do so while maintaining control over their roadmap and business model. The result is that most software products today are closed-source. With Fair Source, companies have a new option. The Fair Source option is not theoretical.

Over the past few months, we introduced several new features and capabilities. While we released larger product updates like Trace Explorer, Insights modules, and our JavaScript V8 SDK (to name a few), it’s the smaller, iterative improvements that really make a big difference in your debugging workflow. Let’s dive into 8 recent updates that you should know about.