February 2024 Summaries

We've identified that most developers are currently at the "ensuring stability" stage of their mobile monitoring journey, with nearly a quarter optimizing performance. To help them move up the maturity curve, Sentry is improving how they can detect and fix mobile performance issues by focusing on four key components: optimizing slow screens using TTID/TTFD, identifying the root cause of slow app starts, improving application responsiveness, and seeing key metrics in a mobile service view. These improvements aim to enhance user experience by addressing stall metrics such as slow and frozen frames, frame delays, and scroll hitches, providing a unified mobile service view for developers to quickly understand performance issues or regressions release-over-release.

The Sentry .NET SDK 4.0 release includes several exciting new features and improvements, building on top of .NET 8.0. Profiling support is now available, allowing developers to analyze performance insights into their app's runtime behavior on real user devices. The SDK also supports native Ahead-Of-Time (AOT) compilation, which can lead to faster startup times and reduced app size. Additionally, the release includes improvements to stack traces, including syntax highlighting, fixes for Stack Trace Linking for C# exceptions, and leveraging Source Link to pull .NET's runtime code into the stack trace. The SDK also supports diverse metric types, seamless aggregation with Sentry, and accessible metrics through the static API. Furthermore, Spotlight support is now available, allowing developers to see all of Sentry's telemetry data directly in their development environment. The release also includes enhancements to MAUI support, including streamlined debugging processes and optimized performance. Overall, this release aims to provide a better development experience for .NET developers.

Sentry, a company, recognized the need to comply with European cookie laws and US privacy laws by requiring user notice and consent for cookies, including non-advertising cookies. They took a radical approach to avoid subjecting users to intrusive pop-ups and banners, instead opting not to use certain cookies that don't meet the narrow exceptions available under applicable law. To identify and evaluate all their cookies, they looped in a technical team, used scanning tools, and worked with third-party providers to determine which cookies could be disabled. After landing on retained cookies, they removed their cookie banner and implemented website scanning technology to ensure continued compliance, choosing to prioritize user digital privacy experience over business flexibility.