# consent

Published articles for consent.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## From Permissions to Sessions: Rethinking Location Access in Android 17

DevFeed: [From Permissions to Sessions: Rethinking Location Access in Android 17](<https://devfeed.tech/articles/from-permissions-to-sessions-rethinking-location-access-in-android-17-25982.md>)

Original publisher: [Read original article](<https://proandroiddev.com/from-permissions-to-sessions-rethinking-location-access-in-android-17-5a13124b777d?source=rss-711ab22c5c77------2>)

Author: Nav Singh

Published: 2026-09-03T18:18:32Z

Content type: tutorial

Language: en

Sources: [Stories by Nav Singh 🇨🇦 on Medium](<https://devfeed.tech/sources/stories-by-nav-singh-on-medium.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [ui](<https://devfeed.tech/topics/ui.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [android-permissions](<https://devfeed.tech/tags/android-permissions.md>), [android17](<https://devfeed.tech/tags/android17.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [branding](<https://devfeed.tech/tags/branding.md>), [consent](<https://devfeed.tech/tags/consent.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [layout](<https://devfeed.tech/tags/layout.md>), [permissions](<https://devfeed.tech/tags/permissions.md>)

### AI overview

A tutorial on implementing Android 17's system-rendered Location Button in Jetpack Compose applications. It explains session-only precise location access, the USE_LOCATION_BUTTON permission, the required Jetpack library, fallback rendering, and UI customization.

### Source excerpt

Image generated using Gemini In this article, we will learn how to implement the new 📍Location button introduced in Android 17 in Jetpack Compose-based Android applications. Android 17 adds a system-rendered 📍Location Button that we can drop into the layout via a Jetpack library, and tapping it gives the app precise location for that session only, gated by a new USE_LOCATION_BUTTON permission. What the feature is Android now exposes a system-owned, standard location button that we can embed in our UI instead of designing a custom control. When the user taps it, the system handles the permission flow, then grants the app precise location for the current session only, rather than long-lived access. How it changes permissions Instead of immediately requesting ACCESS_FINE_LOCATION (and maybe ACCESS_COARSE_LOCATION) at runtime, we declare the new USE_LOCATION_BUTTON permission to host the button. <!-- Standard Coarse and Fine Location Permissions + onlyForLocationButton --> <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" /> <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" android:usesPermissionFlags="onlyForLocationButton"/> <!-- Required system permission for rendering the LocationButton --> <uses-permission android:name="android.permission.USE_LOCATION_BUTTON" />Developer benefits Less custom permission boilerplate: We lean on system UX and the Jetpack library for the hardest parts of location consent. [versions] locationbuttonCompose = "1.0.0-alpha01" [libraries] androidx-locationbutton-compose = { group = "androidx.core.locationbutton", name = "locationbutton-compose", version.ref = "locationbuttonCompose" } Higher trust and clarity for users: the control looks and behaves consistently across apps, and session-only precise access is easier to understand than broader access. Implementation As we all know, Android development is now Compose-first, so we will implement it using the LocationButton composable provided by th

## The Label as Contract: Consent and Priority as the Whole Queue

DevFeed: [The Label as Contract: Consent and Priority as the Whole Queue](<https://devfeed.tech/articles/the-label-as-contract-consent-and-priority-as-the-whole-queue-34107.md>)

Original publisher: [Read original article](<https://philipptheserver.com/posts/label-as-contract/>)

Author: Philipp Lehmann (philipp.lehmann@gruppe.ai)

Published: 2026-07-28T07:00:00Z

Content type: tutorial

Language: en

Sources: [Philipp Lehmann](<https://devfeed.tech/sources/philipp-lehmann.md>)

Topics: [issue tracker](<https://devfeed.tech/topics/issue-tracker.md>), [audit trail](<https://devfeed.tech/topics/audit-trail.md>), [coding](<https://devfeed.tech/topics/coding.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [audit-trail](<https://devfeed.tech/tags/audit-trail.md>), [consent](<https://devfeed.tech/tags/consent.md>), [fifo](<https://devfeed.tech/tags/fifo.md>), [issue-tracker](<https://devfeed.tech/tags/issue-tracker.md>), [priority](<https://devfeed.tech/tags/priority.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

The article argues that an autonomous coding agent should act only on issues carrying a specific human-applied label. Free-form issue content is unauthenticated and cannot establish consent or priority; label actions provide an independent audit trail, and priority should be derived from label transitions.

### Source excerpt

agent-ready label as the only consent gate for a coding agent: FIFO order by label time and a re-read-then-swap claim so two runs never share an issue.

## SCIN: A new resource for representative dermatology images

DevFeed: [SCIN: A new resource for representative dermatology images](<https://devfeed.tech/articles/scin-a-new-resource-for-representative-dermatology-images-28562.md>)

Original publisher: [Read original article](<http://blog.research.google/2024/03/scin-new-resource-for-representative.html>)

Author: Google AI (noreply@blogger.com)

Published: 2024-03-19T15:00:00Z

Content type: article

Language: en

Sources: [Google Research](<https://devfeed.tech/sources/google-research.md>)

Topics: [datasets](<https://devfeed.tech/topics/datasets.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [consent](<https://devfeed.tech/tags/consent.md>), [crowd-sourcing](<https://devfeed.tech/tags/crowd-sourcing.md>), [dataset](<https://devfeed.tech/tags/dataset.md>), [datasets](<https://devfeed.tech/tags/datasets.md>), [developers](<https://devfeed.tech/tags/developers.md>), [diversity](<https://devfeed.tech/tags/diversity.md>), [google](<https://devfeed.tech/tags/google.md>), [health](<https://devfeed.tech/tags/health.md>), [open](<https://devfeed.tech/tags/open.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [research](<https://devfeed.tech/tags/research.md>)

### AI overview

Google Research Health is releasing the Skin Condition Image Network (SCIN), an open-access dermatology image dataset created with Stanford Medicine physicians. It contains over 10,000 voluntarily contributed images covering skin, nail, and hair conditions across various skin tones and body parts, with retrospective dermatologist labels and contributor-provided metadata.

### Source excerpt

Posted by Pooja Rao, Research Scientist, Google Research Health datasets play a crucial role in research and medical education, but it can be challenging to create a dataset that represents the real world. For example, dermatology conditions are diverse in their appearance and severity and manifest differently across skin tones. Yet, existing dermatology image datasets often lack representation of everyday conditions (like rashes, allergies and infections) and skew towards lighter skin tones. Furthermore, race and ethnicity information is frequently missing, hindering our ability to assess disparities or create solutions. To address these limitations, we are releasing the Skin Condition Image Network (SCIN) dataset in collaboration with physicians at Stanford Medicine. We designed SCIN to reflect the broad range of concerns that people search for online, supplementing the types of conditions typically found in clinical datasets. It contains images across various skin tones and body parts, helping to ensure that future AI tools work effectively for all. We've made the SCIN dataset freely available as an open-access resource for researchers, educators, and developers, and have taken careful steps to protect contributor privacy. Example set of images and metadata from the SCIN dataset. Dataset composition The SCIN dataset currently contains over 10,000 images of skin, nail, or hair conditions, directly contributed by individuals experiencing them. All contributions were made voluntarily with informed consent by individuals in the US, under an institutional-review board approved study. To provide context for retrospective dermatologist labeling, contributors were asked to take images both close-up and from slightly further away. They were given the option to self-report demographic information and tanning propensity (self-reported Fitzpatrick Skin Type, i.e., sFST), and to describe the texture, duration and symptoms related to their concern. One to three dermatologists

## Understanding Android Permissions and Runtime Permission Requests

DevFeed: [Understanding Android Permissions and Runtime Permission Requests](<https://devfeed.tech/articles/mastering-android-permissions-27898.md>)

Original publisher: [Read original article](<https://clevertap.com/blog/understanding-android-permissions/>)

Author: Darshan Pania

Published: 2018-07-11T07:00:55Z

Content type: tutorial

Language: en

Sources: [CleverTap](<https://devfeed.tech/sources/clevertap.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [App](<https://devfeed.tech/topics/app.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-permissions](<https://devfeed.tech/tags/android-permissions.md>), [clevertap](<https://devfeed.tech/tags/clevertap.md>), [consent](<https://devfeed.tech/tags/consent.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [mobile-marketing](<https://devfeed.tech/tags/mobile-marketing.md>), [mobile-marketing-technology-engineering-android](<https://devfeed.tech/tags/mobile-marketing-technology-engineering-android.md>), [permission](<https://devfeed.tech/tags/permission.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [technology](<https://devfeed.tech/tags/technology.md>)

### AI overview

This tutorial explains Android permissions, contrasts pre-Marshmallow install-time permissions with runtime permissions, and distinguishes normal from dangerous permissions.

### Source excerpt

The official meaning of the word permission means allowing someone to do a particular thing - it is consent or The post Mastering Android Permissions first appeared on CleverTap.

## When bureaucracy hits the web: the cookie law

DevFeed: [When bureaucracy hits the web: the cookie law](<https://devfeed.tech/articles/when-bureaucracy-hits-the-web-the-cookie-law-27107.md>)

Original publisher: [Read original article](<https://andrea.corbellini.name/2015/09/22/cookie-law/>)

Author: andreacorbellini

Published: 2015-09-22T18:35:00Z

Content type: opinion

Language: en

Sources: [Andrea Corbellini](<https://devfeed.tech/sources/andrea-corbellini.md>)

Topics: [Cookies](<https://devfeed.tech/topics/cookies.md>), [Web](<https://devfeed.tech/topics/web.md>), [Google Analytics](<https://devfeed.tech/topics/google-analytics.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [consent](<https://devfeed.tech/tags/consent.md>), [cookie-law](<https://devfeed.tech/tags/cookie-law.md>), [eu](<https://devfeed.tech/tags/eu.md>), [google-analytics](<https://devfeed.tech/tags/google-analytics.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [third-party](<https://devfeed.tech/tags/third-party.md>)

### AI overview

A personal commentary on the EU cookie law argues that compliance can require intrusive banners, privacy policies, and consent mechanisms. The author describes removing cookies and third-party features from maintained websites, while retaining Google Analytics, social sharing buttons, and Disqus on the blog under the author's stated interpretation of the rules.

### Source excerpt

For a few years now, every first of April I hoped to read between the news something on the lines of "the cookie law was a joke, sorry for that". You know, bureaucracy is slow, and it's reasonable to think that it takes time for them to reveal jokes. Yet, many firsts of April have passed, and no such announcement has been made ...