Articles in this section

Android App Permissions

Kyle Springer
  • Updated
Follow

Overview

Android requires users to view and accept access to certain permissions which that app has access to on the users device. These permissions are set by the Play Store based on features inside of the app and cannot be removed or changed by Mobile Roadie. Users either accept all of the terms or they will not have access to download the app which can be a bit unsettling from the brief descriptions provided by the Play Store. Below are each of the App Permissions and the services or features associated with that permission.

 

Android Permissions

  1. ACCESS_FINE_LOCATION

    1. Allows an app to access precise location from location sources such as GPS, cell towers, and Wi-Fi.

    2. Used to determine users location for all of our location based features (Geo-fencing, Fan wall, Interactive map)

  2. ACCESS_COARSE_LOCATION

    1. Allows an app to access approximate location derived from network location sources such as cell towers and Wi-Fi.

    2. Used to determine users location for all of our location based features (Geo-fencing, Fan wall, Interactive map)

  3. ACCESS_LOCATION_EXTRA_COMMANDS

    1. Allows an application to access extra location provider commands

    2. Used to determine users location for all of our location based features (Geo-fencing, Fan wall, Interactive map)

  4. ACCESS_NETWORK_STATE

    1. Allows applications to access information about networks

    2. Allows us to determine if user has network connectivity, used in every section of our app

  5. ACCESS_WIFI_STATE

    1. Allows applications to access information about Wi-Fi networks

    2. Used to determine if user has internet connectivity if they are not connected to a cell network (tablets, etc)

  6. CAMERA

    1. Required to be able to access the camera device.

    2. Allows the user take pictures directly from the app to post to the fan wall, and for photocards

  7. GET_ACCOUNTS

    1. Allows access to the list of accounts in the Accounts Service

    2. Used to pre-populate the users primary email for mailing list, onboarding, and golden ticket forms. Nothing is sent to the user without their consent, it is simply used as an “auto-complete.”

  8. INTERNET

    1. Allows applications to open network sockets.

    2. Allows us to access the internet to pull in all of the apps data (images, user content, etc), since this is all stored on a central server, and not with the app itself.

  9. FLASHLIGHT

    1. Allows access to the flashlight

    2. Gives users the ability to have flash functionality with any pictures they take in photocards, fanwall, or gallery

  10. READ_PHONE_STATE

    1. Allows read only access to phone state

    2. Gives us the ability to pause the app when you receive or make a phone call

  11. RECEIVE_BOOT_COMPLETED

    1. Allows an application to receive the ACTION_BOOT_COMPLETED that is broadcast after the system finishes booting

    2. Gives us the ability to determine if the phone is finished booting up before we start any background processes

  12. VIBRATE

    1. Allows access to the vibrator

    2. Used for haptic feedback, NOTE: if you disable the vibrator in your phones settings, we will respect that setting.

  13. WAKE_LOCK

    1. Allows using PowerManager WakeLocks to keep processor from sleeping or screen from dimming

    2. Used to prevent music from stopping when the phone sleeps, so the user can continue listening to music while turning their screen off and preserve battery life.

  14. READ_CALENDAR

    1. Allows an application to read the user's calendar data

    2. Used in our events (tour) section. If a user selects that they are going to an event, we provide them with the option to mark their calendar

  15. WRITE_CALENDAR

    1. Allows an application to write (but not read) the user's calendar data

    2. Used in our events (tour) section. If a user selects that they are going to an event, we provide them with the option to mark their calendar

  16. WRITE_EXTERNAL_STORAGE

    1. Allows an application to write to external storage

    2. Gives us the ability to store cache in the devices external storage

  17. com.android.vending.BILLING

    1. In-app Billing on Google Play provides a straightforward, simple interface for sending In-app Billing requests and managing In-app Billing transactions using Google Play

    2. This allows our clients to offer in-app purchases for premium content, for instance Rolling Stones has a locked section with premium content that the user can choose to unlock for a small fee.

  18. GET_TASKS

    1. Allows an application to get information about the currently or recently running tasks

    2. Used to determine if our app is currently being sent to the background or foreground

  1. com.google.android.c2dm.permission.RECEIVE

    1. Allows the app to receive messages (push notifications) from the cms at the clients discretion 

  1. RECORD_AUDIO

    1. Allows an application to record audio

    2. If the application uses Sonic Notify, the Sonic Notify api uses this permission to listen for audio signals to display premium content. The signals are broadcast in certain public events (concerts, etc) 

  1. CALL_PHONE - for apps using Mocean only

    1. Allows an application to initiate a phone call without going through the Dialer user interface for the user to confirm the call being placed

    2. If the application uses the MOcean ad network, this allows the user to initiate a phone call directly from an ad

  2. SEND_SMS - for apps using Mocean only

    1. Allows an application to send SMS messages

    2. If the application uses the MOcean ad network, this allows the user to initiate a sms message directly from an ad

Related articles

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk