Operations | Monitoring | ITSM | DevOps | Cloud

Crash Reporting

Mobile crash reporting and debugging best practices

Maintaining a crash-free, stable mobile app should be top priority for all mobile developers. App stores penalize mobile apps that have high crash rates, and more importantly, buggy apps create poor user experiences, resulting in bad reviews and lost customers. Watch this session to learn key tips for identifying, resolving, and preventing crashes, fast, so you can spend less time troubleshooting and more time building.

Why Early Crash Reporting Saves Time and Prevents Costly Bugs

At BugSplat, we always advocate for teams to introduce crash reporting and establish a bug-tracking/bug-fixing workflow early in their development process. So you can imagine my excitement when I found myself at Denver Startup Week chatting with the founder of a startup that has several projects in flight. He mentioned they’d just kicked off development of a new application, and things were moving quickly.

The 80/20 Rule of Bug Fixing

At BugSplat, we've been supporting applications and video games with crash and error reporting for a long time. Over the years, we've collaborated with a wide range of teams, handling applications of all sizes. From our experience and numerous conversations with users, we've noticed an interesting trend: the distribution of crashes isn't uniform. If your application experiences 100 crashes in a given version, those crashes aren't caused by 100 different defects.

Introducing Custom Attributes

At BugSplat, we’re constantly striving to enhance our platform to meet the evolving needs of our users. We’re excited to introduce our latest feature: Custom Attributes. This powerful addition allows developers to attach any number of custom attributes to crash reports, making BugSplat more customizable to your individual use case and enabling deeper integration with your projects.

Improve mobile vitals using Site24x7 mobile APM and crash analytics

Between your app server and your customer's fingertips, your mobile application or website's performance depends on many factors. Often, what you give may not be what the customer gets, as several things can get in the way, such as bottlenecks, server performance issues, network woes, and un-optimized code. All these factors prevent your customers from experiencing fluid, fast, and functional apps and websites as intended.

Raygun4Aspire: (Free) lightweight Crash Reporting running locally

NET Aspire is a new type of project and set of NuGet packages that make it easier to coordinate the multiple moving parts of a cloud-native web application. Announced near the end of 2023, .NET Aspire is currently in Preview 6, so still a work in progress. We’ve just released Raygun4Aspire, our Crash Reporting client for Aspire applications.

A Look Back at 2023

As we've turned the final pages of 2023 and now set our sights on 2024, it felt like an appropriate moment to pause, reflect, and shine a light on the steps we've made over the past year at BugSplat. There are a couple of compelling reasons to do this: First, we recognize that some of our key updates might slip under the radar amidst the hustle and bustle of daily tasks. Highlighting these changes is our way of giving you a second chance to discover some useful new features at your disposal.