Your Android application does not require that many permissions.

Your Android application does not require that many permissions.

 

 

The permissions of the Android system are a bit confusing from the user's perspective. Sometimes you only need to do some simple things (edit the contact information), but have applied for more permissions than your application needs (such as permission to access all contact information ).

It is hard to prevent users from saving your guard. If your application is still closed-source, you cannot verify whether your application is uploading its contact information to the application server. Even if you explain to the user why you applied for this permission, they may not trust you at last. Therefore, when I used to develop Android apps, I avoided using some tricks, because this will apply for additional permissions and users will not trust you.

After a period of practice, I realized that you do not have to apply for permissions when completing some operations.

For example, the Android system has the following permissions:android.permission.CALL_PHONE. You need this permission to allow you to call the dialer from your application, right? The code below is if you make a call, right?

 

Intentintent=newIntent(Intent.ACTION_CALL);intent.setData(Uri.parse(1234567890))startActivity(intent);

 

Error! This permission allows you to make a phone call without any user operation! That is to say, if my application uses this permission, I can call the harassing phone at three o'clock every morning without your knowledge.

In fact, the correct method is this-UseACTION_VIEWOrACTION_DIAL:

 

Intentintent=newIntent(Intent.ACTION_DIAL);intent.setData(Uri.parse(1234567890))startActivity(intent);

 

The beauty of this solution is that your application does not need to apply for permissions. Why don't I need permissions? Because the Intent you are using will start the dial and pre-dial the number you have set. Compared with the previous scheme, users still need to click "dial-up" to make a call. without the user's participation, the call will not be available. To be honest, this makes me feel very good. Now, the permissions applied by many applications are a bit confusing.

Another example: I wrote a Quick Map application for my wife. This application is mainly used to solve her problem with the existing navigation application. She only wants a contact list and a path to the location of these contacts.

Here, you may think that I need to apply for access to all the contact information to complete this application: Hahaha, you are wrong again! If you read my source code, you will know that I used it.ACTION_PICKThis Intent starts related applications to obtain the contact address:

 

Intentintent=newIntent(Intent.ACTION_PICK);intent.setType(StructuredPostal.CONTENT_TYPE);startActivityForResult(intent,1);

 

This means that my application does not need to apply for permissions, but does not need additional UIS. This improves the user experience of applications.

In my opinion, one of the coolest parts of the Android system is its Intent system. Because Intent means that I don't need to implement anything on my own. Every app registers the data fields it specializes in on Android, such as phone numbers, text messages, or contact information. If an application is needed to solve everything, the application will become very bloated.

Another advantage of the Android system is that I can use the permissions applied by other applications, so that my applications do not need to apply again. The above two points in the Android system can make your application simpler. The Dialer requires the permission to call the phone, but I only need a intent to call the phone. This is because the user trusts the dial that comes with Android, but does not trust my application.

The purpose of writing this blog is to read at least the official Intent documentation to see if you can complete your operations through other applications before you apply for permissions. If you want to learn more, you can take a look at this official document on permissions, which introduces more detailed permissions.

In short, using less permissions not only gives you more user trust, but also gives users a good user experience.

Source: Dan Lew I don't need your permission!