Meta tags:
description=Android has released many individual privacy features over the past few releases, and we are excited for you to adopt them in your apps! This codelab will seek to tie individual privacy features together and show the developer how they can learn about their app’s access to private user data and adopt privacy best practices in an existing, running app.;

Headings (most frequently used words):

android, your, what, you, ll, best, practice, request, to, privacy, and, learn, up, permissions, in, add, logic, permission, location, access, use, more, codelab, stay, organized, with, collections, save, categorize, content, based, on, preferences, intro, build, need, why, is, important, set, environment, context, camera, reduce, app, minimize, of, storage, recommended, data, audit, apis, debug, builds, wrapping, find, our, reference, code, optional, discover, devices, releases, documentation, downloads, support,

Text of the page (most frequently used words):
the (268), and (69), app (61), that (56), for (51), android (45), user (41), location (41), you (40), #permissions (40), #camera (39), data (39), permission (38), access (34), this (33), your (30), request (29), privacy (26), code (26), let (26), with (24), users (24), when (22), screen (21), are (20), add (20), can (19), photo (19), following (19), our (18), will (18), all (17), todo (17), step (17), now (17), best (16), launch (16), apps (15), log (15), codelab (14), from (14), have (14), block (13), screens (12), need (12), should (12), them (12), practices (11), logic (11), register (11), private (11), their (11), access_fine_location (11), isgranted (11), photolog (10), these (10), only (10), use (10), access_coarse_location (10), api (9), check (9), other (9), picker (9), context (9), why (9), also (9), first (9), how (9), viewmodel (9), change (9), explanation (9), before (9), developers (8), more (8), thumb (8), many (8), see (8), experience (8), callback (8), after (8), else (8), ahead (8), accesses (8), not (8), way (7), audit (7), apis (7), what (7), val (7), appopsmanager (7), system (7), which (7), time (7), one (7), grant (7), shouldshowrequestpermissionrationale (7), dialog (7), route (7), showexplanationdialogforcamerapermission (7), home (7), research (6), studio (6), out (6), using (6), storage (6), requesting (6), features (6), build (6), just (6), but (6), methods (6), photos (6), instead (6), feature (6), requestlocationpermissions (6), granted (6), false (6), has (6), down (5), page (5), about (5), existing (5), important (5), dataaccessauditlistener (5), since (5), object (5), override (5), accessed (5), create (5), both (5), over (5), allows (5), file (5), remove (5), adding (5), device (5), doesn (5), line (5), set (5), case (5), onpermissionchange (5), there (5), coarse (5), activityresultcontracts (5), requestpermission (5), activitycompat (5), showexplanationdialogforlocationpermission (5), true (5), navigate (5), run (5), git (5), get (4), google (4), its (4), above (4), already (4), take (4), photolog_start (4), implement (4), results (4), want (4), start (4), onasyncnoted (4), asyncnotedappop (4), emoji (4), two (4), into (4), don (4), requires (4), longer (4), replace (4), rememberlauncherforactivityresult (4), activityresult (4), like (4), practice (4), next (4), currently (4), show (4), explain (4), state (4), getactivity (4), click (4), again (4), delete (4), navcontroller (4), requestcamerapermission (4), rationale (4), requests (4), license (3), documentation (3), download (3), devices (3), media (3), information (3), samples (3), content (3), learn (3), look (3), folder (3), improvements (3), reducing (3), key (3), version (3), onopnotedcallback (3), here (3), track (3), fun (3), var (3), three (3), was (3), expect (3), called (3), once (3), calls (3), require (3), library (3), where (3), accessing (3), help (3), provide (3), such (3), know (3), even (3), manifest (3), much (3), internal (3), without (3), done (3), section (3), install (3), denoted (3), onconfirm (3), arrayof (3), approximate (3), enough (3), increase (3), needs (3), interacting (3), immediately (3), try (3), denied (3), prompt (3), added (3), shows (3), may (3), canaddphoto (3), hascameraaccess (3), well (3), better (3), asking (3), they (3), because (3), project (3), starter (3), compose (3), architecture (3), save (3), new (3), 한국어 (2), 日本語 (2), tiếng (2), việt (2), português (2), brasil (2), polski (2), indonesia (2), français (2), español (2), américa (2), latina (2), deutsch (2), english (2), news (2), platform (2), play (2), support (2), report (2), bug (2), reference (2), guide (2), releases (2), linkedin (2), youtube (2), understand (2), too (2), licensed (2), under (2), java (2), covered (2), instructions (2), photolog_end (2), improved (2), were (2), introduced (2), recap (2), version_codes (2), class (2), then (2), possible (2), purposes (2), logging (2), integrate (2), onnoted (2), syncnotedappop (2), onselfnoted (2), ud83d (2), operation (2), kind (2), instance (2), through (2), adopt (2), determine (2), places (2), asynchronous (2), happens (2), own (2), example (2), invokes (2), binding (2), typically (2), occurs (2), invoked (2), different (2), auditing (2), including (2), sdks (2), dependencies (2), therefore (2), transparency (2), introduces (2), did (2), come (2), used (2), point (2), legacy (2), grid (2), needed (2), anymore (2), provides (2), pickimage (2), below (2), note (2), represents (2), limit (2), max_log_photos_limit (2), pickmultiplevisualmedia (2), activityresultcontract (2), entire (2), uninstall (2), uistate (2), haslocationaccess (2), list (2), locationexplanationdialog (2), current (2), activity (2), result (2), fact (2), going (2), city (2), however (2), estimate (2), precise (2), additional (2), sensitive (2), reduce (2), rates (2), fetchlocation (2), remember (2), mutablestateof (2), ondismiss (2), coroutinescope (2), snackbarhoststate (2), showsnackbar (2), disabled (2), due (2), same (2), icon (2), clicks (2), helps (2), ability (2), handling (2), button (2), functionalities (2), previously (2), whether (2), running (2), approve (2), right (2), verify (2), navigating (2), hasn (2), yet (2), working (2), based (2), buttons (2), startnavigation (2), having (2), until (2), make (2), together (2), improve (2), trust (2), likely (2), essential (2), environment (2), emulator (2), installed (2), command (2), directly (2), enhancing (2), control (2), concerns (2), pew (2), institute (2), found (2), being (2), collected (2), main (2), familiarity (2), jetpack (2), preserving (2), shown (2), logs (2), subscribe, tips, email, manage, cookies, brand, guidelines, products, cloud, firebase, chrome, join, studies, ndk, guides, downloads, cars, chromeos, wear, large, health, fitness, machine, learning, gaming, discover, podcasts, blog, source, security, enterprise, connect, community, follow, androiddev, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, missing, missingtheinformationineed, complicated, steps, toocomplicatedtoomanysteps, date, outofdate, issue, samplescodeissue, otherdown, except, otherwise, noted, details, registered, trademark, oracle, affiliates, site, policies, apache, creative, commons, attribution, landing, haven, solution, followed, closely, identical, find, optional, hope, enjoyed, journey, learned, concepts, along, implemented, enhance, implementing, explored, wrapping, sdk_int, getsystemservice, setonopnotedcallback, mainexecutor, created, early, tracking, requiresapi, console, reporting, systems, sync, self, opstr_coarse_location, uddfa, opstr_camera, udcf8, async, particular, contain, addition, info, something, special, map, listener, walk, applies, mainly, activate, another, relatively, resource, intensive, invoke, respective, passes, uid, noteop, quite, unlikely, callbacks, synchronous, ways, basics, works, targeting, dependent, sdk, difficult, included, perform, specific, actions, printing, each, events, big, lots, collaborators, future, makes, hard, lingering, around, still, accountable, recommended, debug, builds, containing, entry, behind, lines, permissionless, nicer, maintenance, pickvisualmediarequest, pickvisualmedia, imageonly, showing, launching, max, chose, onphotopickerselect, addlogscreen, present, relies, intent, older, action_open_document, tool, select, files, needing, backported, updates, common, work, stored, pick, desired, images, videos, often, pickers, broad, pictures, maintain, independent, minimize, uses, name, forget, copy, lastly, method, addlogviewmodel, instances, item, requestlocationspermissions, edit, function, parameter, reflect, requestmultiplepermissions, definitely, remind, memory, graphic, visualize, range, centered, downtown, los, angeles, california, within, square, kilometers, precision, encourage, whose, review, actively, engaging, quick, provided, controls, clear, choice, share, less, accurate, selecting, most, dashboard, leverage, believes, acceptance, decreases, odds, permanent, denial, confusion, dropout, summary, benefits, resetting, necessary, fetch, populate, exact, behavior, implementation, detail, subject, denying, notice, continue, any, further, interruptions, avoid, denials, preserves, ready, congrats, finished, while, pressing, deny, opening, album, complete, between, itself, calling, returns, display, cameraexplanationdialog, explains, yes, recommends, potentially, opt, preserve, opportune, congratulations, than, tried, trigger, execute, denies, inform, been, accepts, reached, number, evaluate, begin, order, contract, reset, able, press, nothing, fix, finally, permissionsscreen, composable, permissionscreen, navhost, checks, allowing, move, mentioned, enabling, interact, permissionmanager, hasallpermissions, forces, defined, mainactivity, say, enable, surprise, wait, recommendations, probably, guessed, process, jump, proceed, receives, prompts, multiple, confuses, cause, lose, worst, optimal, model, runtime, unlocking, great, significant, impact, means, successfully, configuration, later, open, directory, setup, link, clone, https, github, com, simply, type, terminal, executes, correctly, started, quickly, prepared, cover, related, amount, sense, enhancements, address, shared, saw, earlier, demonstrating, improving, grow, base, concern, significantly, impacting, peoples, decisions, services, study, half, adults, decided, product, service, worried, people, wary, americans, feel, little, companies, frustration, knowing, happening, beyond, direct, worry, profiles, targeted, advertisement, sold, parties, seems, removing, survey, conducted, introduction, tutorial, components, suggested, nice, latest, stable, protects, care, enhances, implements, listed, doing, progress, deficiencies, upon, browse, displays, asks, proceeding, sample, memories, past, few, becoming, increasingly, intro, categorize, preferences, stay, organized, collections, sign, skip,

Text of the page (random words):
droid studio nice to have familiarity with the following architecture components viewmodel and the architecture suggested in the guide to app architecture familiarity with jetpack compose for an introduction to compose check out the jetpack compose tutorial 2 why is privacy important research shows that people are wary about their privacy a survey conducted by the pew research institute found that 84 of americans feel that they have little to no control over the data collected by them by companies and apps their main point of frustration is not knowing what is happening to their data beyond the direct use for example they worry that the data is used for other purposes such as to create profiles for targeted advertisement or even sold to other parties and once the data is out there there seems to be no way of removing it this concern for privacy is already significantly impacting peoples decisions about which services or apps to use in fact that same pew research institute study found that over half 52 of us adults decided not to use a product or service because of privacy concerns such as being worried about how much data is being collected about them therefore enhancing and demonstrating your app s privacy is essential to improving the experience of your apps for your users and research shows that it likely can help you grow your user base as well many of the features and best practices that we will cover in this codelab are directly related to reducing the amount of data that your app accesses or enhancing your users sense of control over their private data both of these enhancements directly address the concerns that users shared in the research we saw earlier 3 set up your environment to get you started as quickly as possible we have prepared a starter project for you to build on in this step you will download the code for the entire codelab including the starter project and then run the starter app on your emulator or device if you have git installed you can simply run the command below to check whether git is installed type git version the terminal or command line and verify that it executes correctly git clone https github com android privacy codelab if you do not have git you can click the link to download all the code for this codelab to setup the codelab open the project in the photolog_start directory in android studio run the photolog_start run configuration on a device or emulator running android 12 s or later you should see a screen asking you to grant permissions to run the app this means you have successfully set up the environment 4 best practice request permissions in context many of you know that runtime permissions are essential to unlocking many key functionalities that are important to having a great user experience but did you know that when and how your app requests the permissions also has a significant impact on user experience let s take a look at how the photolog_start app requests permissions to show you why it doesn t have an optimal permissions model right after launch the user immediately receives permission prompts asking them to grant multiple permissions this likely confuses users and may cause them to lose trust in our app or uninstall it in the worst case the app doesn t let users proceed until all permissions are granted users may not trust our app enough on launch to grant access to all of this sensitive information as you probably guessed the list above represents the set of improvements we will make together to improve the app s permission request process let s jump into it we can see that android s best practice recommendations say that we should request permissions in context the first time the users start interacting with a feature this is because if an app requests permission to enable a feature that the user is already interacting with the request doesn t come as a surprise for users this results in a better user experience in the photolog app we should wait until the first time users click on the camera or location buttons before we request permissions first let s remove the permissions screen that forces users to approve all permissions before going to the home page this logic is currently defined in mainactivity kt so let s navigate there val startnavigation if permissionmanager hasallpermissions screens home route else screens permissions route it checks if the user has granted all of the permissions before allowing them to move to the home page as mentioned before that is not following our best practices for user experience let s change it to the following code enabling users to interact with our app without having all permissions granted val startnavigation screens home route now that we no longer need the permissions screen anymore we can also delete this line from navhost composable screens permissions route permissionscreen navcontroller next remove this line from the screens class object permissions screens permissions finally we can delete the permissionsscreen kt file as well now delete and re install your app which is one way to reset the previously granted permissions you should be able to go to the home screen immediately now but when you press the camera or location buttons in the add log screen nothing happens because the app no longer has the logic to request permissions from the user let s fix that add logic to request camera permission we will begin with the camera permission based on the code samples we see in the requesting permissions documentation we ll want to register the permissions callback first in order to use the requestpermission contract let s evaluate the logic we need if the user accepts the permission we ll want to register the permission with the viewmodel and also navigate to the camera screen if the user hasn t yet reached the limit for the number of photos already added if the user denies the permission we can inform them that the feature is not working since the permission has been denied to execute this logic we can add this code block to todo step 1 register activityresult to request camera permission val requestcamerapermission rememberlauncherforactivityresult activityresultcontracts requestpermission isgranted if isgranted viewmodel onpermissionchange camera isgranted canaddphoto navcontroller navigate screens camera route else coroutinescope launch snackbarhoststate showsnackbar camera currently disabled due to denied permission now we want to verify that the app has the camera permission before navigating to the camera screen and to request the permission if the user hasn t granted it yet to implement this logic we can add the following code block to todo step 2 check request for camera permission before navigating to the camera screen canaddphoto when state hascameraaccess navcontroller navigate screens camera route todo step 4 trigger rationale screen for camera if needed else requestcamerapermission launch camera now try running the app again and click on the camera icon in the add log screen you should see a dialog that requests the camera permission congratulations this is much better than asking users to approve all the permissions before they ve even tried out the app right but can we do better yes we can check if the system recommends that we show a rationale to explain why our app needs access to the camera this helps to potentially increase opt in rates for the permission and also preserve your apps ability to request the permission again at a more opportune time to do that let s build a rationale screen that explains why our app needs access to the user s camera do this by adding the following code block to todo step 3 add explanation dialog for camera permission var showexplanationdialogforcamerapermission by remember mutablestateof false if showexplanationdialogforcamerapermission cameraexplanationdialog onconfirm requestcamerapermission launch camera showexplanationdialogforcamerapermission false ondismiss showexplanationdialogforcamerapermission false now that we have the dialog itself we just have to check whether we should show the rationale before requesting the camera permission we do this by calling activitycompat s shouldshowrequestpermissionrationale api if it returns true we just have to set showexplanationdialogforcamerapermission to true as well to display the explanation dialog let s add the following code block between the state hascameraaccess case and the else case or where the following todo was previously added in the instructions todo step 4 add explanation dialog for camera permission activitycompat shouldshowrequestpermissionrationale context getactivity camera showexplanationdialogforcamerapermission true your complete logic for the camera button should now look like this canaddphoto when state hascameraaccess navcontroller navigate screens camera route activitycompat shouldshowrequestpermissionrationale context getactivity camera showexplanationdialogforcamerapermission true else requestcamerapermission launch camera congrats we ve finished handling the camera permission while following all of android s best practices go ahead delete re install the app once again and try pressing the camera button from the add log page if you deny the permission the app doesn t block you from using the other functionalities like opening the photo album however the next time you click on the camera icon after denying the permission you should see the explanation prompt that we just added notice that the system permission prompt only shows up after the user clicks continue on the explanation prompt and if the user clicks not now we let them use the app without any further interruptions this helps the app avoid additional permission denials from the user and preserves our ability to request the permission again at a different time when the user may be more ready to grant it note the exact behavior of shouldshowrequestpermissionrationale api is an internal implementation detail and is subject to change add logic to request location permission now let s do the same for location we can first register the activityresult for the location permissions by adding the following code block to todo step 5 register activityresult to request location permissions val requestlocationpermissions rememberlauncherforactivityresult activityresultcontracts requestpermission isgranted if isgranted viewmodel onpermissionchange access_coarse_location isgranted viewmodel onpermissionchange access_fine_location isgranted viewmodel fetchlocation else coroutinescope launch snackbarhoststate showsnackbar location currently disabled due to denied permission after that we can go ahead and add the explanation dialog for location permissions by adding the following code block to todo step 6 add explanation dialog for location permissions var showexplanationdialogforlocationpermission by remember mutablestateof false if showexplanationdialogforlocationpermission locationexplanationdialog onconfirm todo step 10 change location request to only request coarse location requestlocationpermissions launch arrayof access_coarse_location access_fine_location showexplanationdialogforlocationpermission false ondismiss showexplanationdialogforlocationpermission false next let s go ahead and check explain if necessary and request the location permissions if the permission is granted we can fetch the location and populate the photo log let s go ahead and add the following code block to todo step 7 check request and explain location permissions when state haslocationaccess viewmodel fetchlocation activitycompat shouldshowrequestpermissionrationale context getactivity access_coarse_location activitycompat shouldshowrequestpermissionrationale context getactivity access_fine_location showexplanationdialogforlocationpermission true else requestlocationpermissions launch arrayof access_coarse_location access_fine_location and there you have it we are done with the permissions section of this codelab go ahead and try resetting your app and see the results summary of how we ve improved the user experience and the benefits for your app request permissions in context when users are interacting with the feature instead of immediately after app launch reduce confusion and user dropout create explanation screens to explain to users why our app needs access to permissions increase transparency for users leverage the shouldshowrequestpermissionrationale api to determine when the system believes your app should show an explanation screen increase permission acceptance rates decreases odds of permanent permission denial 5 best practice reduce your app s location access location is one of the most sensitive permissions and that s why android features it in the privacy dashboard as a quick recap in android 12 we ve provided users with additional controls for location users now have a clear choice to share less accurate location data to apps by selecting approximate location instead of precise location when apps request location access approximate location provides the app with an estimate of the user s location within 3 square kilometers which should be enough precision for many of your app s features we encourage all developers whose apps need location access to review your use case and only request access_fine_location if the user is actively engaging with a feature that requires their precise location graphic to visualize coarse location estimate range centered in downtown los angeles california approximate location access is definitely enough for our photolog app as we only need the user s city to remind them where the memory is from however the app is currently requesting both access_coarse_location and access_fine_location from the user let s change that first we ll need to edit the activity result for location and provide the activityresultcontracts requestpermission function as a parameter instead of activityresultcontracts requestmultiplepermissions to reflect the fact that we are only going to request access_coarse_location let s replace the current requestlocationspermissions object denoted by todo step 8 change activity result to only request coarse location with the following code block instead val requestlocationpermissions rememberlauncherforactivityresult activityresultcontracts requestpermission isgranted if isgranted viewmodel onpermissionchange access_coarse_location isgranted next we will change the launch methods to only request access_coarse_location instead of both location permissions let s replace requestlocationpermissions launch arrayof access_coarse_location access_fine_location with requestlocationpermissions launch access_coarse_location there are two instances of the launch methods in photolog we ll need to change one is in the onconfirm logic in the locationexplanationdialog denoted by todo step 9 change location request to only request coarse location and one in the location list item denoted by todo step 10 change location request to o...