The following shows which android permissions are most frequently request by United Kingdom app publishers. Use our App Market Explorer to filter the Google Play Store by apps with specific permissions.
android.permission.INTERNET makes it possible for app publishers to create network sockets and use custom network protocols within their apps. This permission is not required for internet connection however, as the mobile browser provides all apps with the ability to send data to the internet. 100% of the apps from British publishers use the Internet Access permission. Total 46,853 apps.
The android.permission.ACCESS_NETWORK_STATE permission can be leveraged by app developers to enable their apps to view information about network connections. This information includes such things as which networks exist and which already have connections. 100% of the apps from British publishers use the Network Information Access permission. Total 42,933 apps.
android.permission.WAKE_LOCK gives apps the ability to prevent the phone they are running on from going into sleep mode. This is good for apps, like YouTube, that get extended periods of engagement that do not necessarily require the user to touch the screen or otherwise interact physically with the device. 85% of the apps from British publishers use the Phone Sleep Mode Preventation permission. Total 34,331 apps.
android.permission.WRITE_EXTERNAL_STORAGE makes it possible for app developers to enable their apps to modify or delete the contents of users’ SD cards. 67% of the apps from British publishers use the Write External Storage permission. Total 26,896 apps.
com.google.android.c2dm.permission.RECEIVE can be used within apps to allow them to accept cloud to device messages sent by the app’s service. It should be noted however, that using this service will incur data usage, and malicious apps could cause excess data usage. 62% of the apps from British publishers use the Push Notification permission. Total 25,184 apps.
The android.permission.READ_EXTERNAL_STORAGE permission allows app developers to enable their apps to read the contents of user SD cards. 53% of the apps from British publishers use the Read External Storage permission. Total 21,262 apps.
Apps often advertise other apps. By leveraging com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE apps can make sure that installs of other apps launched via their ads are properly attributed. 52% of the apps from British publishers use the Install Referrer permission. Total 21,079 apps.
android.permission.VIBRATE makes it possible for app builders to give their apps control over the vibrating function of the devices they are running on. 48% of the apps from British publishers use the Vibration permission. Total 19,278 apps.
android.permission.RECEIVE_BOOT_COMPLETED gives apps the ability to start themselves as soon as the system it is running on has finished booting. It should be noted, however, that this can often slow down the phone start time. In addition, it can slow down the device generally by enabling the app to run constantly. 46% of the apps from British publishers use the Start At Boot Time permission. Total 18,788 apps.
App publishers can leverage android.permission.ACCESS_WIFI_STATE to enable their app to view information about Wi-Fi networking. This includes whether Wi-Fi is enabled and the names of the connected Wi-Fi devices. 43% of the apps from British publishers use the Wifi Information Access permission. Total 17,254 apps.
42matters tracks everything from app meta data, to rankings, to download estimates, to changes in meta information, to SDK usage, to App-ads.txt and more. If you would like to leverage our data into your own product, research or app industry analysis, it can be obtained via our API or File Dumps or our interactive App Market Explorer.
42matters tracks everything from app meta data, to rankings, to download estimates, to changes in meta information, to SDK usage, to App-ads.txt and more. If you would like to leverage our data into your own product, research or app industry analysis, it can be obtained via our API or File Dumps or our interactive App Market Explorer.
To use this feature you need to accept our "Functional Cookies" (or all our Cookies) as described in our Cookie Policy. To accept the "Functional Cookies" (or all our Cookies) please click here:
Cookie Settings