Android Developer Verification: Difference between revisions

Line 24:

==Consumer response==

{{Ph-I-ConR}}Alongside the announcement, Google provided a Q&A page for existing developers to ask further questions<ref>{{Cite web |date=2025-08-25 |title=Q&A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |access-date=2025-08-29 |website=Play Console Help}}</ref>. There was a range of responses, some with practical questions about the implementation whereas others highlighting key flaws with the plans from both a consumer and developer perspective including:

{{Ph-I-ConR}}Alongside the announcement, Google provided a Q&A page for existing developers to ask further questions<ref>{{Cite web |date=2025-08-25 |title=Q&A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}</ref>. There was a range of responses, some with practical questions about the implementation whereas others highlighting key flaws with the plans from both a consumer and developer perspective including:

*The hypocrisy of enforcing security on side loaded apps (i.e. user installed apps not from the playstore) whilst Google's playstore maintains its levels of scamware, malware and adware.

@@ Line 24: / Line 24: @@
 ==Consumer response==
-{{Ph-I-ConR}}Alongside the announcement, Google provided a Q&A page for existing developers to ask further questions<ref>{{Cite web |date=2025-08-25 |title=Q&A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |access-date=2025-08-29 |website=Play Console Help}}</ref>. There was a range of responses, some with practical questions about the implementation whereas others highlighting key flaws with the plans from both a consumer and developer perspective including:
+{{Ph-I-ConR}}Alongside the announcement, Google provided a Q&A page for existing developers to ask further questions<ref>{{Cite web |date=2025-08-25 |title=Q&A: New Android developer verification requirements |url=https://support.google.com/googleplay/android-developer/thread/361325854 |archive-url=https://web.archive.org/web/20250829100055/https://support.google.com/googleplay/android-developer/thread/361325854/%F0%9F%92%AC-q-a-new-android-developer-verification-requirements |archive-date=2025-08-29 |access-date=2025-08-29 |website=Play Console Help}}</ref>. There was a range of responses, some with practical questions about the implementation whereas others highlighting key flaws with the plans from both a consumer and developer perspective including:
 *The hypocrisy of enforcing security on side loaded apps (i.e. user installed apps not from the playstore) whilst Google's playstore maintains its levels of scamware, malware and adware.