Not sure if this is the correct place to post, but I just wanna kinda rant a bit.
I’m not the only one that hates this, right?
An app can just do a “This App Does Not Allow Screenshots”? Like… wtf?
Like, its my phone, and some app can just decide to disable a fuction of my phone. It’s my phone and if I wanna take a screenshot, I’m taking a screenshot. I don’t care about whatever “security” the app developer wants.
Imagine if every online shopping app whether fast food or amazon, just used this to block you from taking a screenshot so you can’t save the records in case of a dispute.
Which android developer thought it was a good idea to let an app disable a function on your phone. Even iPhone doesn’t have this stupid concept.
Sorry for the rant.
Anyone wanna share your stories?
(P.S. I have a cheap secondary phone to take photos of the screen. “This App Does Not Allow Screenshots” my ass lmao, I’m taking the screenshot whether the app wants it or not.
I work for a company that builds an app /sdk that handles credit cards / payments. It’s one of the (many) requirements for getting an industry standard certification (like PCIDSS / MPOC). The app Must block screenshots, and Must disable the camera while using it…
Why did you capitalize “must”?
Probably a nod to the written style of RFC definitions, which have the word entirely in capital letters, as in… the implementation MUST do such and such, and SHOULD do this other thing. In this case, the relevant security standard(s)
We have italics and bold characters for that.
RFCs were being written back when line printers couldn’t do either.
What on earth are those in charge of certification standards thinking they’ll achieve with requirements like this?
It’s probably to stop third party apps from screenshoting the banking app.
Accidentally screenshotting your bank acct and routing number is the only one I can really think of.