Sounds like that’s a heavy handed dev friendly solution, but also plenty of comments around this post about why what’s not user friendly. Common theme of People needing to capture the info on a screenshot and don’t want it blurred on a screenshot. The Boolean flag to trigger the blur should be user input. The option to blur can be set by dev but user gets control as to whether it triggers or not.

Good to hear it’s pretty straightforward on the dev side I guess, I can’t tell if this is a net benefit as a feature. I think my opinion is still rooted in user needs and I’d simply expect they are responsible for their screen shots and what sensitive info they may contain. So this feature as it exists is not a net good thing.