Lines Matching full:your
43 In many cases, you can choose between two ways for your app to perform a
44 task. You can have your app ask for permission to perform the operation
50 For example, suppose your app needs to be able to take pictures with the
51 device camera. Your app can request the {@link
52 android.Manifest.permission#CAMERA CAMERA} permission, which allows your app
53 to access the camera directly. Your app would then use the camera APIs to
54 control the camera and take a picture. This approach gives your app full
56 into your app.
65 the picture to your app's {@link
81 <li>Your app has full control over the user experience when you perform the
82 operation. However, such broad control adds to the complexity of your task,
87 install time (depending on the user's Android version). After that, your app
90 on), your app becomes unable to perform the operation at all.
122 user may decide not to install your app at all. For these reasons, you should
123 minimize the number of permissions your app needs.
127 Quite often your app can avoid requesting a permission by using an
128 <em>intent</em> instead. If a feature is not a core part of your app's
137 grant your app its permissions while they are running the app. If you
139 overwhelm the user and cause them to quit your app. Instead, you should ask
144 In some cases, one or more permissions might be absolutely essential to your
157 If your app provides a tutorial, it may make sense to request the app's
166 requestPermissions()} says what permission your app wants, but doesn't say
168 explain to the user why your app wants the permissions before calling
187 photography app's tutorial could demonstrate its "share photos with your
201 result, you'll have to test your app under a wider range of conditions. Prior
202 to Android 6.0, you could reasonably assume that if your app is running at
213 <li>Identify your app?s current permissions and the related code paths.
245 <li>Analyze your app for services that use permissions.
