<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aayush Sarikhada on Medium]]></title>
        <description><![CDATA[Stories by Aayush Sarikhada on Medium]]></description>
        <link>https://medium.com/@ayushsarikhada?source=rss-7c11450245e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hpvmnYW3Th2tInw0Gm-DJQ.jpeg</url>
            <title>Stories by Aayush Sarikhada on Medium</title>
            <link>https://medium.com/@ayushsarikhada?source=rss-7c11450245e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:52:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ayushsarikhada/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Instructions vs Agent Skills: The Difference Most Developers Miss]]></title>
            <link>https://medium.com/simform-engineering/agent-instructions-vs-skills-the-difference-most-developers-miss-a0d854203f36?source=rss-7c11450245e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0d854203f36</guid>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[agent-skills]]></category>
            <category><![CDATA[github-copilot]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[vscode]]></category>
            <dc:creator><![CDATA[Aayush Sarikhada]]></dc:creator>
            <pubDate>Fri, 17 Apr 2026 09:13:00 GMT</pubDate>
            <atom:updated>2026-04-20T06:33:34.271Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Why understanding instructions and skills is essential for building reliable, production-ready AI agents</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*q3JpDzNY6jpM_tPr2RUAaw.jpeg" /><figcaption>Instructions vs Agent Skills: The Difference Most Developers Miss</figcaption></figure><p>Modern AI agents are not driven by prompts alone. They rely on structured layers such as instructions and skills. This article explains the distinction between these two concepts, showing how instructions define behaviour while skills define execution, supported by practical developer-focused examples.</p><blockquote><strong>Note:</strong> The concepts in this article are explained in the context of GitHub Copilot, primarily as used in VS Code and related agent workflows. While the core ideas apply broadly, implementation details may vary across environments such as CLI-based setups or other tools like Claude Code.</blockquote><p>Let’s start with a simple question. If a junior developer writes bad code, what do you fix first, <strong>the task you gave them</strong> or<strong> the way they think?</strong> Most experienced developers would choose to <strong>fix their thinking</strong>, because once that improves, everything else tends to follow. <strong>The same idea applies to AI.</strong></p><p>A lot of developers today say AI feels inconsistent. Sometimes it works well, sometimes it doesn’t. The common advice is to <em>“write better prompts</em><strong><em>.</em></strong><em>”</em> That helps, but only to a certain point.</p><p>The real issue goes deeper. Modern AI systems are not just driven by prompts. They rely on two key layers, <strong>instructions</strong> and <strong>skills</strong>, and understanding how these work together is what actually makes the difference.</p><p>To understand this properly, we need to break these layers down one by one.</p><h3><strong>First: What Are Instructions?</strong></h3><p>Instructions are persistent guidance that GitHub Copilot automatically includes in its context to shape how it behaves across tasks. They are not tied to a single prompt. Instead, they define coding standards, architectural decisions, and expectations for how the AI should operate.</p><p>In practice, instructions act as an always-on layer that influences every response unless something more specific overrides them.</p><h3>How Instructions Are Provided</h3><p>GitHub Copilot reads instructions from specific files and injects them into its context.</p><p>The most common sources are:</p><ol><li><strong>Repository-level instructions (Always Applied in every request)</strong></li></ol><p>.github/copilot-instructions.md</p><p>These apply broadly across the repository and define default behaviour.</p><p><strong>2. Scoped instructions (pattern-based)</strong></p><p>.github/instructions/*.instructions.md</p><p>These can include targeting rules like:</p><pre>---<br>applyTo: &quot;**/*.kt&quot;<br>---</pre><p>This allows instructions to apply only in specific contexts, such as certain languages or file types.</p><h3>What This Means in Practice</h3><ul><li>Some instructions are <strong>always applied globally</strong></li><li>Some are <strong>applied only when context matches</strong></li><li>All of them together shape how Copilot behaves before it even processes your prompt</li></ul><h3>Think of Instructions Like This</h3><p>Instructions are like telling a junior developer:</p><ul><li>“We follow MVVM here”</li><li>“Don’t break existing APIs”</li><li>“Write clean, modular code”</li><li>“Prefer coroutines over callbacks”</li></ul><p>You are not assigning a task. You are defining how work should be done across the system.</p><p><strong>Example (Instruction File)</strong></p><pre>---<br>description: &quot;Kotlin standards&quot;<br>---<br>- Use MVVM architecture<br>- Use coroutines<br>- Avoid modifying public APIs<br>- Prefer Flow over LiveData</pre><h3>What Instructions Do</h3><p>In practice, instructions shape the system in a few important ways:</p><p>They influence code structure, decision making, and consistency across outputs.At the same time, they<strong> do not</strong> execute tasks, define workflows, or call tools.</p><h3><strong>Now: What Are Skills?</strong></h3><p>This is where things get misunderstood.</p><p>Skills are not rules. They are: <strong>Reusable ways to complete a specific type of task</strong></p><p>They are closer to:</p><ul><li>Playbooks</li><li>Workflows</li><li>Procedures</li></ul><p><strong>Think of Skills Like This</strong></p><p>A senior tells a junior: <em>“Whenever you build a login feature, follow this flow…”</em></p><p><strong>What Skills Actually Are</strong></p><p>As per the GitHub Copilot official <a href="https://docs.github.com/en/copilot/concepts/agents/about-agent-skills">documentation</a>: Agent skills are not just a conceptual idea, they have a concrete, well-defined structure that your AI agent reads, loads, and acts on.</p><p>Agent <strong>skills</strong> are <strong>folders</strong> of <strong>instructions</strong>, <strong>scripts</strong>, and <strong>resources</strong> that Copilot can load when relevant to improve its performance in specialized tasks. The Agent Skills specification is an open standard, used across a range of AI systems, not just GitHub Copilot.</p><p><strong>Folder Structure</strong></p><p>Every skill lives inside its own named subdirectory. The folder name should be lowercase with hyphens for spaces.</p><pre>.github/<br>└── skills/<br>    └── app-testing/<br>        ├── SKILL.md              ← required (only source of truth)<br>        ├── scripts/              ← optional (better than loose files)<br>        │   └── example.sh<br>        ├── examples/             ← optional<br>        └── assets/               ← optional</pre><ul><li><strong>Important:</strong> The core file must always be named <strong>SKILL.md</strong>. No other filename will be recognized.</li></ul><p><strong>What Goes Inside SKILL.md</strong></p><p><strong>SKILL.md</strong> is a Markdown file with YAML frontmatter. It has two parts:</p><p><strong>1. YAML Frontmatter (metadata)</strong></p><pre>---<br>name: github-actions-failure-debugging # required - unique, lowercase, hyphenated<br>description: &gt; # required - tells Copilot WHEN to use this skill<br>Guide for debugging failing GitHub Actions workflows.<br>Use this when asked to debug failing GitHub Actions workflows.<br>license: MIT # optional - licensing info<br>---</pre><ul><li><strong>name</strong>: unique identifier, must match the folder name convention</li><li><strong>description</strong>: this is the trigger, Copilot reads descriptions to decide whether to load the skill for a given task</li></ul><p><strong>2. Markdown Body (the actual instructions)</strong></p><p>This is where you write the step-by-step workflow, guidelines, or procedures for the skill. Copilot injects the entire SKILL.md into its context when the skill is <strong>activated</strong>.</p><pre>---<br>frontmatter<br>---<br><br>To debug failing GitHub Actions workflows, follow this process:<br>1. Use `list_workflow_runs` to look up recent runs and their status<br>2. Use `summarize_job_log_failures` to get an AI summary of failed job logs<br>3. If needed, use `get_job_logs` or `get_workflow_run_logs` for full logs<br>4. Try to reproduce the failure in your own environment<br>5. Fix the issue before committing changesWhere to Store Skills</pre><p><strong>How Copilot Decides to Use a Skill</strong></p><p>Copilot doesn’t load all skills all the time. It reads your prompt, scans the <strong>description</strong> field of available skills, and decides which ones are relevant. When a skill is chosen, the full <strong>SKILL.md</strong>, along with any scripts or files in that skill’s folder is made available in the agent’s context.</p><p>This is why the <strong>description</strong> field is the most important line you’ll write. It’s not documentation for humans, it’s the activation trigger for the agent.</p><h3>Final Takeaway</h3><p>AI agents operate on two layers:</p><ul><li><strong>Instructions</strong> define behavior and are always active</li><li><strong>Skills</strong> define execution and are used only when needed</li></ul><p>Most issues developers face come from mixing these two up. The fix is simple:</p><ul><li>Use instructions (e.g., .github/copilot-instructions.md) to enforce standards</li><li>Use skills to define task-specific workflows</li></ul><p>Good instructions without skills lead to well-structured mistakes.<br>Good skills without instructions lead to inconsistent solutions.</p><p>You also don’t need to build everything from scratch. Community skill libraries are available, including <a href="https://github.com/anthropics/skills">Anthropic-maintained skills</a> and <a href="https://github.com/github/awesome-copilot/tree/main/skills">broader community collections</a>.</p><p>The difference between average and reliable AI systems isn’t better prompts, it’s understanding and separating these two layers.</p><p>If this changed how you think about AI agents, here’s how to go deeper:</p><ul><li><strong>Audit your current setup</strong> : do you have instructions defined? Are your skills documented as reusable workflows?</li><li><strong>Try it hands-on</strong> : set up a .github/copilot-instructions.md file and create your first skill under .github/skills/` for a task you repeat often</li><li><strong>Share your experience</strong> : drop a comment: are you currently using instructions, skills, both, or neither?</li></ul><p>&gt; <em>Found this useful? Share it with a developer who’s been blaming prompts for everything.</em>🙂</p><p><strong>References</strong></p><p>1. <a href="https://docs.github.com/en/copilot/concepts/agents/about-agent-skills"><strong>GitHub Docs — About Agent Skills</strong></a></p><p>2. <a href="https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/create-skills"><strong>GitHub Docs — Creating Agent Skills for GitHub Copilot</strong></a></p><p>3. <a href="https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/create-skills"><strong>GitHub Docs — Creating Agent Skills for GitHub Copilot CLI</strong></a></p><p>4. <a href="https://docs.github.com/en/copilot/reference/customization-cheat-sheet"><strong>GitHub Docs — Copilot Customization Cheat Sheet</strong></a></p><p>5. <a href="https://docs.github.com/en/copilot/how-tos/configure-custom-instructions/add-repository-instructions"><strong>GitHub Docs — Adding Repository Custom Instructions</strong></a></p><p>6. <a href="https://github.com/agentskills/agentskills"><strong>Agent Skills Open Standard</strong></a></p><p><strong>For more updates on the latest tools and technologies, follow the </strong><a href="https://medium.com/simform-engineering"><strong>Simform Engineering</strong></a><strong> blog.</strong></p><p><strong>Follow Us: </strong><a href="https://twitter.com/simform"><strong>X</strong></a><strong> | </strong><a href="https://www.linkedin.com/company/simform/"><strong>LinkedIn</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0d854203f36" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simform-engineering/agent-instructions-vs-skills-the-difference-most-developers-miss-a0d854203f36">Instructions vs Agent Skills: The Difference Most Developers Miss</a> was originally published in <a href="https://medium.com/simform-engineering">Simform Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android 16 Highlights: Everything You Need to Know]]></title>
            <link>https://medium.com/simform-engineering/android-16-highlights-everything-you-need-to-know-37eae5042d0f?source=rss-7c11450245e------2</link>
            <guid isPermaLink="false">https://medium.com/p/37eae5042d0f</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[now-in-android]]></category>
            <category><![CDATA[android-studio]]></category>
            <category><![CDATA[android-16]]></category>
            <category><![CDATA[android-16-features]]></category>
            <dc:creator><![CDATA[Aayush Sarikhada]]></dc:creator>
            <pubDate>Mon, 19 May 2025 05:59:45 GMT</pubDate>
            <atom:updated>2025-05-19T08:00:44.498Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XMoX62ViB9iG5hi0pmo2Wg.png" /></figure><p>Android 16 brings a host of important updates that improve app adaptability, privacy, security, and user experience across devices. Let us see a breakdown of these changes; which I have organised by category.</p><h3>App Adaptivity &amp; Cross-Device Experience</h3><ul><li><a href="https://developer.android.com/about/versions/16/behavior-changes-16#edge-to-edge"><strong>Mandatory Edge-to-Edge Design</strong></a><strong>:</strong> Apps targeting Android 16 must implement edge-to-edge layouts, ensuring immersive and modern user interfaces.</li><li><a href="https://developer.android.com/about/versions/16/behavior-changes-16#ignore-orientation"><strong>Orientation and Aspect Ratio Flexibility</strong></a><strong>:</strong> Restrictions on orientation and aspect ratios are ignored on large screens(screens larger that sw600dp), so apps must be responsive and flexible to different display sizes. However there are some exceptions for, 1. Games (based on the android:appCategory flag), 2. Users explicitly opting in to the app’s default behaviour in aspect ratio settings of the device and 3. Screens that are smaller than sw600dp. These <a href="https://developer.android.com/about/versions/16/behavior-changes-16#implementation-details">Manifest attributes</a> will be ignored for apps (not games) on large screens.</li><li><a href="https://developer.android.com/about/versions/16/behavior-changes-all#large-screens-form-factors"><strong>Virtual Device Overrides</strong></a>: A virtual device owner is a trusted app on your phone that creates a virtual version of the device to run apps, which are then displayed on other screens like computers, VR headsets, or car displays. In Android 16, these owners can modify app settings, such as screen orientation and size restrictions, for better display on external screens. This can impact your app’s UI, especially on large screens like car displays or Chromebooks, if the layout was designed for smaller, portrait screens. To ensure your app adapts well across all devices, it’s important to make it flexible for various screen sizes and orientations.</li></ul><h3>Privacy &amp; Security Enhancements</h3><ul><li><a href="https://developer.android.com/about/versions/16/features#privacy-sandbox"><strong>Privacy Sandbox Improvements</strong></a><strong>:</strong> Android 16 continues to reduce cross-app tracking by incorporating the latest version of the <strong>Privacy Sandbox on Android</strong>, part of their ongoing work to develop technologies where users know their privacy is protected.</li><li><a href="https://developer.android.com/privacy-and-security/local-network-permission"><strong>Local network protection</strong></a><strong>:</strong> Consider testing your app by <strong>opting in</strong> the upcoming Local Network Protection feature. It will give users more control over which apps can access devices on their local network in a future Android major release.</li><li><a href="https://developer.android.com/about/versions/16/behavior-changes-16#health-fitness"><strong>Granular Health and Fitness Permissions</strong></a><strong>: </strong>BODY_SENSORS permissions are moving to the granular permissions under android.permissions.health also used by <a href="https://developer.android.com/health-and-fitness/guides/health-connect">Health Connect</a>. Any API previously requiring BODY_SENSORS or BODY_SENSORS_BACKGROUND now requires the corresponding android.permissions.health permission. Additionally, Mobile apps that migrate to using READ_HEART_RATE and other granular permissions are also required to <a href="https://developer.android.com/health-and-fitness/guides/health-connect/develop/get-started#show-privacy-policy">declare</a> an activity that displays the app’s privacy policy, following the same guidelines as Health Connect.</li></ul><blockquote><strong>Important:</strong> Failure to provide the rationale for mobile apps will result in the permission being revoked.</blockquote><ul><li><strong>Improved security against Intent redirection attacks:</strong> Android 16 introduces default protections against Intent redirection attacks, enhancing app security with minimal developer effort. To opt-out of this by-default behaviour refer <a href="https://developer.android.com/about/versions/16/behavior-changes-all#opt-out"><strong>this</strong></a> link.</li><li><a href="https://developer.android.com/about/versions/16/features#key-sharing"><strong>New KeySharing API</strong></a><strong>: </strong>In Android 16 you can now share<strong> </strong>access to Android Keystore keys with other apps. The new <a href="https://developer.android.com/reference/android/security/keystore/KeyStoreManager">KeyStoreManager</a> class supports <strong>granting</strong> and <strong>revoking</strong> access to keys by app <a href="https://developer.android.com/reference/android/os/Process#myUid()">uid</a>, and includes an API for apps to access shared keys.</li><li><a href="https://developer.android.com/about/versions/16/features#secure-ranging"><strong>AES-256 Encryption for Wi-Fi location</strong></a><strong>:</strong> Android 16 adds support for robust security features in Wi-Fi location on supported devices with Wi-Fi 6’s 802.11az, allowing apps to mix higher accuracy, greater scalability, and dynamic scheduling of the protocol with security enhancements including AES-256-based encryption and protection against <a href="https://www.fortinet.com/resources/cyberglossary/man-in-the-middle-attack">MITM</a> attacks.</li><li><a href="https://developer.android.com/about/versions/16/behavior-changes-all#ordered-broadcast-priority"><strong>Ordered broadcast priority scope no longer global:</strong></a> In Android 16, broadcast delivery order using the android:priority attribute or IntentFilter#setPriority() across different processes will not be guaranteed. Broadcast priorities will only be respected within the same application process rather than across all processes. Your app may be affected if it relies on broadcast intent priorities across multiple processes or expects a specific delivery order between processes.</li></ul><h3>Performance &amp; battery</h3><ul><li><a href="https://developer.android.com/about/versions/16/features#system-triggered-profiling"><strong>System-triggered profiling</strong></a><strong>:</strong> Android 16 introduces system-triggered profiling to ProfilingManager. Apps can register interest in receiving traces for certain triggers such as cold start reportFullyDrawn or ANRs, and then the system starts and stops a trace on the app’s behalf. After the trace completes, the results are delivered to the app’s data directory.</li><li><strong>Start component in ApplicationStartInfo:</strong> To help optimise the startup flow, Android 16 adds ApplicationStartInfo#getStartComponent() in order to identify the type of component that triggered the app&#39;s start.</li><li><a href="https://developer.android.com/about/versions/16/features#feature-pending-job-reason-history"><strong>Better job introspection</strong></a><strong>:</strong> Android 16 introduces a new API <a href="https://developer.android.com/reference/android/app/job/JobScheduler#getPendingJobReasons%28int%29">JobScheduler#getPendingJobReasons(int)</a>, which will return multiple reasons why a job is pending, whether because of explicit constraints set by the developer or implicit constraints set by the system. It is recommend to use the API to debug why your jobs may not be executing.</li><li><a href="https://developer.android.com/about/versions/16/features#arr"><strong>Adaptive refresh rate</strong></a><strong>:</strong> Android 16 extends the developers to support Adaptive refresh rate (ARR), introduced in Android 15. Now Android 16 introduces <a href="https://developer.android.com/reference/android/view/Display#hasArrSupport%28%29">hasArrSupport()</a> and <a href="https://developer.android.com/reference/android/view/Display#getSuggestedFrameRate%28int%29">getSuggestedFrameRate(int)</a> while restoring <a href="https://developer.android.com/reference/android/view/Display#getSupportedRefreshRates%28%29">getSupportedRefreshRates()</a> to make it easier for your apps to take advantage of ARR. RecyclerView 1.4 internally supports ARR when it is settling from a fling or smooth scroll.</li></ul><h3>JobScheduler &amp; Background Task Changes</h3><ul><li><a href="https://developer.android.com/about/versions/16/behavior-changes-all#job-quota-opt"><strong>Stricter Job Quotas</strong></a><strong>:</strong> Background jobs, especially for apps in the foreground or active standby, are subject to stricter quota enforcement to improve battery life.</li><li><a href="https://developer.android.com/about/versions/16/behavior-changes-16#schedule-at-fixed-rate"><strong>Fixed-Rate Work Scheduling Optimisation</strong></a><strong>:</strong> Background work scheduling is optimised for battery efficiency, which may affect how frequently tasks run. Before targeting Android 16, if a scheduleAtFixedRate task was missed because the app was not in a valid lifecycle state, all missed tasks would run immediately once the app returned to a valid state. <strong>Starting with Android 16</strong>, only <strong>one</strong> missed execution will be run immediately when the app returns to a valid lifecycle.</li><li><strong>New Debugging API:</strong> New <a href="https://developer.android.com/about/versions/16/features#feature-pending-job-reason-history">JobScheduler#getPendingJobReasonsHistory</a> helps developers diagnose why jobs are not executing as expected. To debug why a job was stopped, it is recommend to log why your job was stopped by calling WorkInfo.getStopReason(). (for JobScheduler jobs, call JobParameters.getStopReason()).</li><li><a href="https://developer.android.com/reference/android/app/job/JobInfo.Builder#setImportantWhileForeground(boolean)">JobInfo#setImportantWhileForeground</a> is now fully <strong>deprecated</strong>.</li></ul><h3>Bluetooth &amp; Audio Improvements</h3><ul><li><a href="https://developer.android.com/about/versions/16/behavior-changes-all#improved-bond-loss-handling"><strong>Improved Bluetooth Bond Loss Handling</strong></a><strong>:</strong> Enhanced handling of Bluetooth bond loss requires updates to pairing logic to maintain stable connections.</li><li><a href="https://developer.android.com/about/versions/16/features#generic-ranging"><strong>New RagingManager</strong></a><strong>:</strong> Android 16 adds a new RangingManager to provide ways to determine the distance and angle of supported hardware between local device and remote device. It will help to better pinpoint the tracker’s distance and angle.</li></ul><h3>UI &amp; Accessibility Upgrades</h3><ul><li><a href="https://developer.android.com/about/versions/16/behavior-changes-16#predictive-back"><strong>Migration or opt-out required for predictive back</strong></a><strong>:</strong> Apps targeting Android 16 must support predictive back gestures to enhance navigation fluidity. Additionally, onBackPressed will not be called and KeyEvent.KEYCODE_BACK will not be dispatched anymore. (temporary opt-out available).</li><li><a href="https://developer.android.com/about/versions/16/behavior-changes-all#disruptive-a11y"><strong>Deprecation of announceForAccessibility()</strong></a><strong>:</strong> Developers should migrate to modern accessibility APIs for better compatibility.</li><li><a href="https://developer.android.com/about/versions/16/features#rich-haptics"><strong>Richer haptics</strong></a><strong>:</strong> Android 16 adds <a href="https://developer.android.com/reference/android/os/vibrator/package-summary">haptic APIs</a> that will let apps define the amplitude and frequency curves for a haptic effect while also abstracting away differences between device capabilities.</li><li><a href="https://developer.android.com/about/versions/16/features#lea-phone-input"><strong>Phone with microphone input for voice calls with LEA hearing aids</strong></a><strong>: </strong>You can now switch between the build-in microphones of hearing aids and the microphone on your phone for voice calls if you are using LE Audio hearing aids. Users can also adjust the volume of ambient sound that is picked up by the hearing aid’s microphone in Android 16.</li><li><a href="https://developer.android.com/about/versions/16/features#vertical-text"><strong>Vertical Text</strong></a><strong>: </strong>Android 16 also adds support for rendering and measuring text vertically to provide foundational vertical writing support for library developers. This is particularly useful for languages like Japanese, which commonly use vertical writing systems.</li><li><a href="https://android-developers.googleblog.com/2025/01/first-beta-android16.html#:~:text=Supplemental%20descriptions"><strong>Supplemental Descriptions</strong></a><br> Android 16 introduces setSupplementalDescription, allowing developers to add descriptive text to a ViewGroup without overriding content descriptions from its non-focusable child views. This helps preserve context (e.g., labeling a dropdown as &quot;Font Family&quot; while retaining the selected value like &quot;Roboto&quot;) for accessibility tools.</li><li><a href="https://developer.android.com/about/versions/16/behavior-changes-16#elegant-text-height"><strong>Elegant font APIs deprecated and disabled</strong></a><strong>: </strong>Android 16 is getting rid of the <strong>elegantTextHeight</strong> font setting introduced in Android 15. Its readability improvements are now the default standard, so the attribute will just be ignored. Best to double-check your text layouts, especially for different languages, to make sure everything still looks sharp.</li><li><a href="https://android-developers.googleblog.com/2025/01/first-beta-android16.html#:~:text=Required%20form%20fields"><strong>Required Form Fields</strong></a><br> A new method <a href="https://developer.android.com/reference/android/view/accessibility/AccessibilityNodeInfo#setFieldRequired(boolean)">setFieldRequired</a> in AccessibilityNodeInfo enables apps to mark input fields as required. This helps accessibility services identify and guide users through mandatory fields in forms, such as checkboxes for terms and conditions.</li><li><a href="https://developer.android.com/about/versions/16/features#outline-text"><strong>Outline Text for Accessibility</strong></a><strong>:</strong> Text outlining improves readability for users with low vision.</li></ul><h3>Camera updates and improvements</h3><ul><li><a href="https://developer.android.com/about/versions/16/features#apv"><strong>Advanced Professional Video (APV) Codec</strong></a><br>Android 16 introduces support for <a href="https://www.ietf.org/archive/id/draft-lim-apv-00.html">APV</a>, a codec for professional-grade video recording and editing. It offers perceptually lossless quality, high bitrates (up to several Gbps), support for 2K–8K resolutions, and efficient intra-frame-only encoding. Additional features include frame tiling, various chroma formats, multi-view support, and HDR10/10+ metadata. The APV 422–10 Profile (YUV 422, 10-bit, up to 2Gbps) is supported, with reference implementation via <a href="https://github.com/AcademySoftwareFoundation/openapv">OpenAPV</a>.</li><li><a href="https://developer.android.com/about/versions/16/features#night-mode-scene-detection"><strong>Night Mode Scene Detection</strong></a><br>A new EXTENSION_NIGHT_MODE_INDICATOR in Camera2&#39;s CaptureResult lets apps detect night scenes and trigger night mode camera sessions more reliably. This helps apps capture higher-quality low-light photos, enhancing in-app photo engagement.</li><li><a href="https://developer.android.com/about/versions/16/features#hybrid-auto-exposure"><strong>Hybrid Auto-Exposure</strong></a><br>Camera2 now supports hybrid AE modes, letting you manually control ISO or exposure time while AE handles the rest. This offers more flexibility than the current all-manual or all-auto approach.</li><li><a href="https://developer.android.com/about/versions/16/features#color-temperature-tint"><strong>Precise White Balance Controls</strong></a><br>Support for accurate white balance adjustments is added via <a href="https://developer.android.com/reference/android/hardware/camera2/CameraMetadata#COLOR_CORRECTION_MODE_CCT">COLOR_CORRECTION_MODE_CCT</a>, allowing fine-tuning of colour temperature and tint beyond preset AWB modes — ideal for professional video workflows.</li><li><a href="https://developer.android.com/about/versions/16/features#motion-photos"><strong>Motion Photo Intents</strong></a><br>New standard intents (ACTION_MOTION_PHOTO_CAPTURE and ACTION_MOTION_PHOTO_CAPTURE_SECURE) enable apps to request motion photo capture. Output can be directed via EXTRA_OUTPUT or setClipData. If ClipData isn’t set, the image will be auto-copied to a default location.</li><li><a href="https://developer.android.com/about/versions/16/features#ultra-hdr"><strong>UltraHDR Improvements</strong></a><br>Continued enhancements include support for HEIC encoding and new UltraHDR metadata aligned with the ISO 21496–1 draft standard.</li></ul><h3><a href="https://developer.android.com/about/versions/16/features#photo-picker-improvements">Photo picker Improvements</a></h3><ul><li><strong>Embedded Photo Picker: </strong><a href="https://developer.android.com/reference/android/widget/photopicker/package-summary">New APIs</a> now allow apps to embed the photo picker directly within their view hierarchy. This creates a more seamless and integrated user experience while maintaining process isolation, ensuring that users can select media without granting the app broad access permissions. To ensure maximum compatibility across different Android versions and to simplify implementation, it is recommended to use the upcoming Android Jetpack library for integrating the embedded photo picker.</li><li><strong>Cloud Search in Photo Picker: </strong><a href="https://developer.android.com/sdk/api_diff/b-dp2-incr/changes/pkg_android.provider">New APIs</a> will also introduce cloud search functionality within the Android photo picker, enabling users to search for media directly from their cloud media providers. This search capability will be available soon.</li></ul><h3><a href="https://developer.android.com/about/versions/16/features/progress-centric-notifications">Progress-Centric Notifications</a></h3><ul><li><strong>New Notification Style:</strong> Android 16 introduces progress-centric notifications designed to show real-time updates for ongoing tasks such as ride shares, deliveries, or navigation.</li><li><strong>Interactive and Informative:</strong> These notifications feature progress bars, status chips, and milestone indicators that keep users informed at a glance.</li><li><strong>Status Bar Integration:</strong> Progress-centric notifications also appear as chips in the status bar, providing persistent, glanceable updates without clutter.</li><li><strong>Developer APIs:</strong> New APIs allow developers to create these rich, dynamic notifications, improving user engagement and experience.</li></ul><h3>System &amp; Developer Platform Changes</h3><ul><li><a href="https://developer.android.com/about/versions/16/behavior-changes-all#16-kb-compatibility-mode"><strong>16KB Page Size Support</strong></a><strong>:</strong> Apps must support a 16KB memory page size for optimal performance, with a compatibility mode for older apps. Apps not built for 16 KB memory page size will trigger a <strong>warning dialog</strong>. Setting the android:pageSizeCompat property in the AndroidManifest.xml to enable the backwards compatibility mode will stop the display of the dialog.</li><li><a href="https://developer.android.com/about/versions/16/features#measurement-systems"><strong>Measurement System Customisation</strong></a><strong>:</strong> Users can globally switch between metric and imperial units.</li></ul><blockquote><strong>NOTE:</strong> Starting <strong>November 1st, 2025</strong>, all new apps and updates to existing apps submitted to Google Play and targeting <strong>Android 15+</strong> devices must support <strong>16 KB</strong> page sizes.</blockquote><p>You can refer the reported issues to stay informed about <a href="https://issuetracker.google.com/savedsearches/6900279">known issues</a> and their <a href="https://developer.android.com/about/versions/16/release-notes#top-resolved-beta3">fixes</a>, so you can adjust your app if needed.</p><h3>Conclusion</h3><p>Android 16 emphasises adaptability, privacy, and smoother user experiences. Developers should start testing and updating their apps to meet new requirements, while users can look forward to a more secure and flexible Android environment.</p><p><strong>Sources:</strong></p><ul><li><a href="https://developer.android.com/about/versions/16/behavior-changes-all">Android 16 Behavior Changes (All Apps)</a></li><li><a href="https://developer.android.com/about/versions/16/behavior-changes-16">Android 16 Behavior Changes (Targeting Android 16)</a></li><li><a href="https://developer.android.com/about/versions/16/features">Android 16 Features</a></li><li><a href="https://developer.android.com/about/versions/16/features/progress-centric-notifications">Progress-Centric Notifications</a></li><li><a href="https://android-developers.googleblog.com/2025/01/first-beta-android16.html">Android Developers Blog — First Beta</a></li><li><a href="https://android-developers.googleblog.com/2025/02/second-beta-android16.html">Android Developers Blog — Second Beta</a></li><li><a href="https://android-developers.googleblog.com/2025/03/the-third-beta-of-android-16.html">Android Developers Blog — Third Beta</a></li></ul><blockquote><strong>For more updates on the latest tools and technologies, follow the </strong><a href="https://medium.com/simform-engineering"><strong>Simform Engineering</strong></a><strong> blog.</strong></blockquote><blockquote><strong>Follow us: </strong><a href="https://twitter.com/simform"><strong>Twitter</strong></a><strong> | </strong><a href="https://www.linkedin.com/company/simform/"><strong>LinkedIn</strong></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37eae5042d0f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simform-engineering/android-16-highlights-everything-you-need-to-know-37eae5042d0f">Android 16 Highlights: Everything You Need to Know</a> was originally published in <a href="https://medium.com/simform-engineering">Simform Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>