<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Android on App Coding</title>
    <link>https://appcoding.com/tags/android/</link>
    <description>Recent content in Android on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 25 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/android/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Mobile Accessibility Is the Case Developers Keep Ignoring</title>
      <link>https://appcoding.com/2026/03/25/mobile-accessibility-is-the-case-developers-keep-ignoring/</link>
      <pubDate>Wed, 25 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/2026/03/25/mobile-accessibility-is-the-case-developers-keep-ignoring/</guid>
      <description>&lt;p&gt;The accessibility argument is made with sufficient frequency in developer conferences and engineering blog posts that it has acquired the character of something everyone agrees with and nobody acts on. Apps ship with missing accessibility labels, unlabeled buttons, broken VoiceOver navigation, and dynamic type support that was added for text elements but forgotten for layout constraints. The gap between the accessibility investment that development teams describe as important and the accessibility state of their shipped applications is among the widest in software development.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cross-Platform vs Native: The Honest Assessment Nobody Gives You</title>
      <link>https://appcoding.com/2026/03/04/cross-platform-vs-native-the-honest-assessment-nobody-gives-you/</link>
      <pubDate>Wed, 04 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/2026/03/04/cross-platform-vs-native-the-honest-assessment-nobody-gives-you/</guid>
      <description>&lt;p&gt;The cross-platform vs native debate has a quality problem: the people most qualified to give objective assessments have financial or professional stakes in one answer. Agency developers who charge by the hour prefer native because it doubles the billable work. Cross-platform framework vendors publish benchmark comparisons designed to minimize the gaps between their output and native. Native platform advocates at Apple and Google have obvious incentives to characterize cross-platform output as inferior.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Mobile Security: What Developers Consistently Get Wrong</title>
      <link>https://appcoding.com/2026/02/04/mobile-security-what-developers-consistently-get-wrong/</link>
      <pubDate>Wed, 04 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/2026/02/04/mobile-security-what-developers-consistently-get-wrong/</guid>
      <description>&lt;p&gt;Mobile security vulnerabilities cluster in a predictable set of categories. The same mistakes appear in security audits of consumer apps, enterprise apps, and fintech apps with equal regularity. The recurrence of the same errors across different teams and different organizations suggests that the failures are not primarily due to ignorance — most mobile developers are aware that security matters — but to a gap between security knowledge and the specific engineering practices that translate that knowledge into secure code.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Jetpack Compose Is Winning Android UI Development</title>
      <link>https://appcoding.com/2025/11/19/jetpack-compose-is-winning-android-ui-development/</link>
      <pubDate>Wed, 19 Nov 2025 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/2025/11/19/jetpack-compose-is-winning-android-ui-development/</guid>
      <description>&lt;p&gt;Google&amp;rsquo;s transition of Android UI development from the XML layout system to Jetpack Compose has been, by the standards of platform UI framework migrations, unusually smooth. Compose became stable in August 2021. By 2024, it was the recommended approach for new Android development. In 2026, the question for Android teams is no longer whether to adopt Compose but how to manage the migration of existing View-based codebases.&lt;/p&gt;&#xA;&lt;p&gt;The comparison with SwiftUI is instructive. Both frameworks launched within two years of each other, both represent declarative replacements for older imperative UI systems, and both have faced criticism for gaps between their initial capabilities and the full feature set of what they replaced. Compose has navigated this transition with fewer of the minimum-API-level constraints that limit SwiftUI&amp;rsquo;s adoption curve, because Android&amp;rsquo;s broader device compatibility requirements have historically pushed Google toward more conservative backward compatibility policies.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Swift vs Kotlin: The State of Native Mobile Development in 2026</title>
      <link>https://appcoding.com/2025/09/10/swift-vs-kotlin-the-state-of-native-mobile-development-in-2026/</link>
      <pubDate>Wed, 10 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/2025/09/10/swift-vs-kotlin-the-state-of-native-mobile-development-in-2026/</guid>
      <description>&lt;p&gt;The question of whether to build natively for iOS and Android or to abstract across both platforms with a cross-platform framework has occupied mobile development teams for more than a decade. The answer has not settled. What has settled is the character of native development itself — and in 2026, Swift and Kotlin have each reached a maturity that makes the native argument significantly stronger than it was five years ago.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
