Top of search for you means top of mind for your customers. And with Google’s upcoming Page Experience update to Web Vitals taking place in a few weeks, now’s the right time to optimize your user experience. But before you can optimize your user’s experience, you need to be able to measure it. We’re kicking off Measurement May by breaking down breaking down how Google uses Web Vitals data — and how you can instrument that data with Sentry.
Responding to and ignoring notifications can be a full-contact sport. It makes sense, though, from GitHub, Slack, to Jira and Sentry; our world revolves around robots telling us everything is important, critical, and urgent. Just like that, it’s near impossible to see what actually matters so you can solve quicker and more comprehensively.
Recently, Sentry converted 100% of its frontend React codebase from JavaScript to TypeScript. This year-long effort spanned over a dozen members of the engineering team, 1,100 files, and 95,000 lines of code. In this blog post, we share our process, techniques, challenges, and ultimately, what we learned along this journey.
From testing in production to running A/B tests, feature flags have a range of uses. At Sentry, one way we use feature flags is to safely allow beta access to new features for some of our “Early Adopter” customers. Because you can set multiple combinations of feature flags, every user is likely to have a different experience.
Just like that Mobile March Madness 2021 is almost in our rearview. Before we look to April, let’s recap some of our most notable mobile updates from this past month with a few tips on how to solve what matters faster and a sneak peek of what’s coming next. That’s right. We’re constantly improving our mobile monitoring solution independent of our alliteration-based marketing campaigns.
Like many companies, Sentry uses feature flags to determine when certain users see certain features. Recently, we decided to switch our feature flag software to an open-source system called Flagr. And while implementing Flagr, we used our new Performance tools to find — and ultimately fix — a serious issue in how we were fetching our flags.
Android is arguably the most ubiquitous operating system in the world. Whether it’s a tablet, phone, folding phone, computer, TV, or IoT device, chances are you’ve interacted with Android OS. And to help developers get full visibility into how their customers experience Android’s myriad applications, we’re extending Performance to Android.
Like many companies, we have a Hack Week at Sentry. In 2017, we coded an app which blared entrance music for anyone who stepped foot in our office. In 2019, we encouraged folks to be nice on the Internet. Noble causes, sure, but for this year’s Hack Week I was determined to advance a cause near and dear to my cold British heart: dark mode.
March Mobile Madness continues with Performance support for React Native. Our friend, Jenn Meung shares how Performance supports his mobile appliction. In addition to working with Sentry, I also contribute to Tour, a travel app which helps people plan trips with a drag-and-drop interface. Because Tour is built with React Native, we’ve always had issues accurately gauging how people use our app and its performance.
One of Sentry’s most-trafficked pages is our issue details page, as it helps our customers understand the root cause an error. For those of you who are new to Sentry, we define an issue as a group of similar events. To render the issue details, a significant amount of data needs to be fetched — counts, charts, event details, and other metadata. The two main components on this page are the latest event, and summary statistics.
