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.
This month we’re updating several of our mobile SDKs. You might think it’s madness… Mobile March Madness. First up is Flutter. It’s fair to say that all of us have had a bad mobile experience which frustrated us enough to warrant switching apps. Getting the experience right requires a lot of work due to the variety of OSes, screen sizes and orientations.
In January we brought Release Health to JavaScript. This month we’ve been thinking about the overall experience for JavaScript developers, some could call it JavaScript Jebruary. Think back to your last frustrating experience. It was probably caused by slow page loads or getting dizzy from staring at the ever-ending spinner. One survey showed that the average desktop load time on a webpage was 10.3 seconds and on mobile, it was 27.3 seconds.
