# Sdk
18 posts- Building Type-Safe Metrics API in Swift: Part IIdate: author: Phil Niedertscheider
Replace Any with type-safe protocols, handle array conformance limitations, and future-proof your Swift enums.
- Building Type-Safe Metrics API in Swift: Part Idate: author: Phil Niedertscheider
Explore protocol extensions, enums with associated values, and ExpressibleByStringLiteral to build type-safe Swift APIs.
- Reverse Engineering iOS to Fix SDK Crashesdate: author: Phil Niedertscheider
We reverse-engineered a private iOS framework to uncover why iPadOS 26 broke type casting in our SDK.
- Keeping Up With the Python Ecosystemdate: author: Ivana Kellyer
The Sentry Python SDK has built-in support for more than 60 popular packages. This is how we make sure we actually support what we claim to be supporting.
- From /users/123 to /users/:id: A Guide to Route Parametrizationdate: author: Sigrid Huemer
How Sentry's JS SDKs figure out your dynamic route names to make querying your issues easier.
- Enabling Out-of-the-Box Performance Insights in Unity Games with the Sentry SDKdate: author: Stefan Jandl
Learn how we built the autoinstrumentation in the Unity SDK via IL Weaving
- Preact or Svelte? An Embedded Widget Use Casedate: author: Catherine Lee
Preact or Svelte, which framework is best for building an embedded user feedback widget?
- Sentry JavaScript SDK v8 - A Retrospectivedate: author: Francesco Novy
This post will outline learnings the Sentry SDK team had from releasing v8 of the JavaScript SDKs.
- How to Refactor and Not Break Thingsdate: author: Anton Pirker
How we completed a huge refactoring of a software used by thousands of developers without breaking things.
- Should you, could you AOT?date: author: James Crosswell
How ASP.NET Core application developers can make the transition from JIT (Just-in-Time) to AOT (Ahead-of-Time) compilation, using the Sentry SDK for .NET as a case study.
- How We Reduced Replay SDK Bundle Size by 35%date: author: Francesco Novy
An in-depth analysis of how we managed to cut the Session Replay SDK bundle size by 35%.
- Measuring Session Replay Overheaddate: author: Billy Vong
The best way to figure out how overhead impacts you is to measure it yourself. Follow along as we show you how we went about measuring overhead on Sentry and how you can measure it on your own applications.
- How we reduced CI time by 35% with Nx Cachingdate: author: Francesco Novy
Sentry is a very fast-moving company. In just one month we merged 165 pull requests from 19 authors and changed over 800 files, with a total of over 22,000 additions and almost 10,000 deletions. By updating to Lerna 6...
- How we run our Python tests in hundreds of environments really fastdate: author: Anton Pirker
One of Sentries core company values is “for every developer”. We want to support every developer out there with our tools. But not every developer uses the newest or widely adopted tech stack, so we also try to suppor...
- Understanding the Performance Impact of Generated JavaScriptdate: author: Abhijeet Prasad
In the modern web, the JavaScript you write is often down-compiled using a compiler like Babel to make sure your JavaScript is compatible with older browsers or environments. In addition, if you are using TypeScript (...
- JavaScript SDK “Package Size is Massive” - So we reduced it by 29%date: author: Abhijeet Prasad
Developers started to notice just how big our JavaScript package was and yeah, we knew. We weren’t ignoring the issues; after all, we don’t want the Sentry package to be the cause of a slowdown. But to reduce our Java...
- How we trimmed the Sentry JavaScript SDK file size by 20%date: author: Abhijeet Prasad
SDKs naturally increase in size over time. After all, it does take more bytes to implement more features. This is not a big deal for most languages—the relative size of each new feature is small, and load times and st...
- Alias: An approach to .NET Assembly Conflict Resolutiondate: author: Bruno Garcia
Most plugin based models load all assemblies into a single shared context. This is a common approach because it has better memory usage and startup performance. The history and rules of assembly loading in .NET is con...