Operations | Monitoring | ITSM | DevOps | Cloud

From the first introduction of Core Web Vitals, Google has maintained that these user experience metrics will keep evolving. Since 2022, the Google team has been testing Interaction to Next Paint (INP), a new interactivity metric, and asking for feedback from the development community. Late in 2023, they announced that INP would replace FID as a Core Web Vital. The transition to INP is effective from March 2024.

Before the Raygun API limited release last year, we'd been consistently receiving requests for a public API for a long time, to provide a way for our customers to access their Raygun data programmatically. We're now proud to say we're providing a public API with a range of endpoints, but it took us a lot of planning and development to get here! In this post, I'd like to take you back to the beginning of development on our big API project. Specifically, I want to walk through the pivotal decisions we made around testing when we started development on the project, and how (and why) these have paid off.

In the expanding world of APIs, meaningful error responses can be just as important as well-structured success responses. In this post, I'll take you through some of the different options for creating responses that I've encountered during my time working at Raygun. We'll go over the pros and cons of some common options, and end with what I consider to be one of the best choices when it comes to API design, the Result Pattern. This pattern can lead to an API that will cleanly handle error states and easily allow for consistent future endpoint development.

In the world of software development, quickly finding and fixing errors drives better experiences for both end-users and developers. One key tool in this process is the symbol map, which records debugging information that was lost in the compilation process. Symbol maps (or source maps if we're talking JavaScript) connect the code developers write to the minified code in production, making it easier to decipher crashes by pinpointing the exact source code that caused the error.