Google Mandates 64-Bit Support for Wear OS Apps by September 2026
Google has announced a new requirement for all Wear OS applications to support 64-bit architectures, aligning the platform with previous mandates for mobile devices and Google TV. Effective September 15, 2026, Google Play will block the upload of any new apps or updates containing native code that do not include 64-bit versions alongside their 32-bit counterparts. This initiative aims to leverage performance improvements offered by 64-bit CPUs, ensuring faster and richer user experiences while laying the groundwork for future innovation. Although Google has supported 64-bit processors since Android 5, this formalizes the requirement for the Wear OS ecosystem. Developers are urged to assess their applications using tools like the APK Analyzer in Android Studio to check for native code dependencies, such as .so files. While many apps written purely in Kotlin or Java may not require changes, those utilizing third-party SDKs must verify compliance. Google notes that most developers have already adopted this standard, expecting minimal effort for remaining adjustments. Importantly, support for existing 32-bit devices will continue, ensuring no disruption for current users while pushing the ecosystem toward modern architectural standards.
Wire timeline
Google Mandates 64-Bit Support for Wear OS Apps by September 2026
Google has announced a new requirement for all Wear OS applications to support 64-bit architectures, aligning the platform with previous mandates for mobile devices and Google TV. Effective September 15, 2026, Google Play will block the upload of any new apps or updates containing native code that do not include 64-bit versions alongside their 32-bit counterparts. This initiative aims to leverage performance improvements offered by 64-bit CPUs, ensuring faster and richer user experiences while laying the groundwork for future innovation. Although Google has supported 64-bit processors since Android 5, this formalizes the requirement for the Wear OS ecosystem. Developers are urged to assess their applications using tools like the APK Analyzer in Android Studio to check for native code dependencies, such as .so files. While many apps written purely in Kotlin or Java may not require changes, those utilizing third-party SDKs must verify compliance. Google notes that most developers have already adopted this standard, expecting minimal effort for remaining adjustments. Importantly, support for existing 32-bit devices will continue, ensuring no disruption for current users while pushing the ecosystem toward modern architectural standards.
Android Developers Blog