Google: Difference between revisions

Line 31:

In 2019, Google took away the ability to turn off the "pull-to-refresh" gesture on the mobile edition of their Chrome web browser, following by refusing to reinstate the option after an abnormally high number of complaints that the gesture causes accidental refreshes. See [[Google_Chrome#Mandatory_pull-to-refresh|Google Chrome § Mandatory pull-to-refresh]].

Google lets app developers arbitrarily [[screenshot blocking|prevent device owners from capturing screenshots and screen recordings]] on Android. While the original intention was to prevent sensitive information in banking apps from getting outside, it has been severely overused by app developers and prevents legitimate uses such as asking for help in forums and bug reports. Google provided no option for device owners to override it, so the only way is to unlock the bootloader and modify the operating system.<ref>{{cite web |url=https://www.howtogeek.com/why-screenshots-dont-always-work-especially-in-secure-apps/ |website=How To Geek |author=Faisal Rasool |title=Why Your Phone Blocks Screenshots in Secure Apps |date=2025-08-23 |access-date=2026-05-26 }}</ref><ref>{{cite web |url=https://old.reddit.com/r/LineageOS/comments/f3xk35/bookingcom_app_disallow_to_take_screenshot_can_i/ |website=Reddit |title=Booking.com app disallow to take screenshot, can I bypass this? |date=2020-02-14 |access-date=2026-05-26 }}</ref>

In 2025, Google announced their [[Android Developer Verification]] program, which if executed will make it impossible to run apps by developers not personally identified and approved by Google.

@@ Line 31: / Line 31: @@
 In 2019, Google took away the ability to turn off the "pull-to-refresh" gesture on the mobile edition of their Chrome web browser, following by refusing to reinstate the option after an abnormally high number of complaints that the gesture causes accidental refreshes. See [[Google_Chrome#Mandatory_pull-to-refresh|Google Chrome § Mandatory pull-to-refresh]].
+Google lets app developers arbitrarily [[screenshot blocking|prevent device owners from capturing screenshots and screen recordings]] on Android. While the original intention was to prevent sensitive information in banking apps from getting outside, it has been severely overused by app developers and prevents legitimate uses such as asking for help in forums and bug reports. Google provided no option for device owners to override it, so the only way is to unlock the bootloader and modify the operating system.<ref>{{cite web |url=https://www.howtogeek.com/why-screenshots-dont-always-work-especially-in-secure-apps/ |website=How To Geek |author=Faisal Rasool |title=Why Your Phone Blocks Screenshots in Secure Apps |date=2025-08-23 |access-date=2026-05-26 }}</ref><ref>{{cite web |url=https://old.reddit.com/r/LineageOS/comments/f3xk35/bookingcom_app_disallow_to_take_screenshot_can_i/ |website=Reddit |title=Booking.com app disallow to take screenshot, can I bypass this? |date=2020-02-14 |access-date=2026-05-26 }}</ref>
 In 2025, Google announced their [[Android Developer Verification]] program, which if executed will make it impossible to run apps by developers not personally identified and approved by Google.