 All right, hi everyone. I'm Mike Deemer. I'm a product manager at Dynatrace and an open feature maintainer. And today I'm excited to tell you about client-side feature flagging with open feature. There we go. All right, so, sorry about that, technical issues. All right, before we dive into the technical details of the presentation, I'd just like to do a quick level set on what a feature flag is and why they're basically essential to modern software development practices. So a feature flag is a technique that allows you to control a pivot point in your application at runtime. They do not require the code to be changed or a service to be redeployed or restarted in order for the value to change. Feature Flags allow you to decouple feature releases from deployments and they allow teams to coordinate feature releases on their schedule. Progressively enabling a feature flag allows you to reduce risk by tightly controlling the impact radius. They also allow you to quickly abort a failed deployment by basically instantaneously allowing you to revert the change. Teams are also able to experiment using feature flags by defining a control group and multiple different variations and then testing the impact that the feature has. So really they become very essential to the whole modern software development lifecycle. All right, then I just really wanted to quickly talk about open feature itself. So it's an open, we're a CNCF incubating project that's created an open specification for vendor agnostic feature flagging. We've created many SDKs in popular languages that seamlessly integrate with the commercial solutions or in-house vendors. And then today I'd like to announce that we've released a web 1.0 SDK. This has basically been a long time coming. We started with server side use cases but really we see that obviously the web is extremely important to people and it's been a long time coming to make sure that we can support client side and server side feature flagging use cases with a consistent API that's completely vendor agnostic. The web SDK is foundational SDK that can be used on its own but it also lays the groundwork for framework specific implementations. So having a web or a vendor neutral web SDK means that everyone can benefit from the SDK regardless of where your future flags are managed. And if you're interested definitely take a look at the blog. It's part of the QR code that you can scan right there. Although basically client side feature flags look very similar to server side feature flags there are some subtle differences. It takes advantage of what we call the static context paradigm and that's what I'm going to talk about in a moment. All right the static context paradigm basically in feature flagging you're commonly leveraging relevant contextual data. So in open feature we call it evaluation context. On web or mobile evaluation context typically remains consistent for the duration of the user session. It allows us to perform async operations early and cache the results. In this example we're setting the user session email and browser in the context and then the open SDK or open feature SDK then bulk evaluates all the related feature flags and stores the results in the client until the context or the feature definition is modified. Notice that all the context defined is unlikely to change for the duration of the session. And if any of this is interesting to you we have a lot of practical examples this week so there is a session on compliance and experimentation. It's called feature management improv with Todd Bart. It's tomorrow at five twenty five and then I'll also be presenting on progressive delivery. It's an observable feature rollouts with myself and Dan Dyla from the open telemetry governance committee. That's on Friday at four o'clock and let's see. Also if you're interested we're going to be in the booth we have the afternoon shifts in the project pavilion so please stop by. If you're also interested if you're around on Friday from 11 to 12 30 we're going to be doing a contrib pass so if you want to get your hands dirty on some code and work with some of the maintainers definitely please feel free to stop by. And there's a quick link to our website if you're interested to learn more. So thanks for your time. Appreciate it.