On April 2, 2026, Google declared its intention to expand the 64-bit app requirement—already in place for Android phones for years—to the Wear OS ecosystem. Beginning in September 2026, all new Wear OS apps and app updates that include native code must offer both 32-bit and 64-bit versions when submitted to the Google Play Store. Otherwise, the new versions will not be accepted for upload to the Play Console. Nevertheless, the policy regarding 32-bit app support remains intact, meaning watches equipped with 32-bit processors or pre-installed with 32-bit Wear OS can continue to be used as usual. Google mentioned that the majority of Wear OS developers have already made the transition, with the vast majority of apps now featuring 64-bit versions. For those yet to adapt, the workload is typically minimal. Since many Wear OS apps are built on Kotlin and Java, which are non-native coding languages, developers can often adapt to 64-bit devices without modifying their existing code. However, it's crucial to note that some dependent libraries and SDKs may incorporate native code, necessitating thorough verification. Developers can utilize the APK Analyzer tool within the Android Studio IDE to ascertain whether their project contains native code or manually inspect it by checking if the lib folder includes .so files.