The performance of your iOS app is crucial when building and publishing it for any number of users. Your users expect it to be delightful, fast and responsive, so if your app seems sluggish or unresponsive, it will affect your reviews and you might lose valuable users. While solving this for your apps, it’s easy to overlook the influence of the choices made on performance throughout development.
This is a conversation we had with our Engineering, Product, and Design (EPD) organization. We are publishing it as we believe it’s important to our customers and fundamental to our open source approach. You can join the conversation on GitHub. Lately, I am spending a lot of my time thinking about Sentry and its core developer story. I also consider why we haven’t been able to overcome the main challenges we recognized years ago.
Benjamin Franklin was a smart dude. Among the many wonderful things he produced was an eternal bit of wisdom - an ounce of prevention is worth a pound of cure. To avoid a bigger problem, spend time early on the things that help you avoid it. That wisdom applies everywhere. Avoid nasty stuff with doctors by exercising and making healthier choices. Avoid getting hit by a car by looking both ways. Avoid sunburn by wearing sunscreen. You get it. So what does this have to do with Sentry? A lot.
Forethought is a leading AI company providing solutions that transform the customer experience. As a high-growth startup with 2x annual growth in their engineering team, they faced increasingly complex processes and found that what had worked in the past wasn’t going to cut it anymore.
Flutter is one of the fastest-growing open source cross-platform development frameworks. The likes of BMW, Google Pay, Tencent, and iRobot all use Flutter to quickly build and maintain mobile applications. In fact, Flutter was used by 42% of software developers in 2021, surpassing React Native as the most popular cross-platform mobile framework.
Monitoring performance is a critical part of software development. We just released version 3.0.0 of our Sentry Android Gradle plugin, which brings a handful of auto-instrumentation capabilities to Android developers, featuring Room and SQLite queries performance, File I/O operations performance, and more.
Some months ago we wrote a quick guide on how to use Sentry with Spring Boot and Logback. Since then, we’ve continued working on improving the development experience, added several features for error reporting and, most importantly, implemented the performance feature in Sentry Java SDK with a dedicated integration with Spring MVC. If you haven’t yet used Sentry in a Spring Boot application - nothing to worry about - you will find all the necessary steps below.
Your applications most likely consist of multiple components. These components could be written in different languages, with each individually instrumented with Sentry’s SDK. The goal of our tracing solution is to make sure developers get a full picture of the data captured within their tech stack. Tracing allows you to follow a request from the frontend all the way to your backend application and back.
As most developers know, alert-fatigue is real, and the last thing you want is another feed of notifications. Read on to learn how the new Alert Details view helps you filter out notifications for Issue Alerts you don’t care about, and how it can help you focus on the ones that do. When you get started with Sentry, you’ll likely create an Alert for every Issue.
We’ve recently completed a large beta test for our new product here at Testmo. We build a test management tool, so most of our users are professional software testers. As you can imagine, our customers are a rather critical group of users when it comes to software quality. We’ve learned some important lessons about running a large beta test and we want to share how we benefited from Sentry error reporting to identify, find, and fix issues quickly.
