Once apps can present one thing to the user and another thing to the captured image, there are some pretty weird possibilities

This is an interesting case of "Good use" of a "bad feature". This feature is bad because it works against the user and device owner, but this use case like hiding your password when sharing your screen is a good use case.

Dear app developers: please do not detect screenshots, and do not change behavior. It is my phone and I should have the right to save anything on my screen for my own purposes and you should not know that I do that.

https://drive.google.com/file/d/1Y-P92-yDZ9zqwuXjWjqA4JGyKGq... .ai features premium comment for funny videos sharing subscribe like remix camera filter

If the feature can sometimes be useful (including this situation, which some other comments mentioned; but also for other things such as hiding actual secure data), then perhaps it should be made as a setting which can be changed in the setting menu (e.g. "Exclude secure data from screenshots"; it should also mention which apps use this feature), so prevent abuse. (This would also make it clear what the feature is, as well as being able to disable it.)

Reading between the lines:

Oh, so you can take screenshots of the content that tries to avoid it if you do it mid-switch?

If it's reliable and WONTFIX, that's almost enough to get me to switch away from Android.

Screenshot taking prevention is harmful and should not have ever been allowed to become a platform-level feature in the first place. Because if there's one rule of platform/client interaction, is that if you add a feature that can be abused against customers for stupid reasons, it will be. There's a number of apps I have on my Android phone that block screenshots for dubious reasons, that can be maaaybe charitably explained by calling them "growth hacking pretending to be a security feature", but in some cases even that's a stretch.

This feature should never have existed in the first place.

(At least Bluesky is open about it, both by being Open Source and calling out the "growth hack" by name in source code.)

Is this the relevant issue for Graphene OS?

https://github.com/GrapheneOS/os-issue-tracker/issues/664

Upvote the issue if so.

I appreciate the Game Changer reference

This sort of stuff to me is an example of fear within an organization. Whenever I see engineering resources allocated towards self promotion and branding rather than quality and features for its users it shows how leaders want control over narratives.

> The “Follow” button is visible when I take the screenshot mid-switch.

Does this indicate that the privacy feature has a gap, where you could reveal the length of your password if you take a screenshot mid app switch?