If you build apps for Wear OS, Google just handed you another deadline.
The company says that beginning September 15, 2026, apps for its smartwatch platform that include native code must support both 32-bit and 64-bit architectures. Any new apps or updates that fail to meet that requirement will be rejected from the Play Console.
In other words, if your app still ships only with 32-bit native libraries, you will not be able to upload updates anymore.
Google has been moving the broader Android ecosystem toward 64-bit for years, so this is not coming completely out of nowhere. Smartphones went through the same transition starting back in 2019. Now the company is extending that policy to watches running Wear OS.
SEE ALSO: Google clamps down on Android developers with mandatory verification
To be clear, Google is not killing 32-bit support entirely. Existing 32-bit Wear OS devices will still receive compatible apps through Google Play. The change mainly affects developers submitting new apps or updates that contain native code.
Still, it is one more box developers must check before publishing.
Google says the transition should be fairly painless for many developers. If an app is written entirely in Kotlin or Java, there may be nothing to change. The catch is that native code can sneak into an app through third party libraries or SDKs. Developers who never touched native code themselves could still end up shipping it without realizing it.
Because of that, Google recommends inspecting app packages using Android Studio’s APK Analyzer. If you see .so files inside the lib folder, that means native code is present. For ARM hardware, 32-bit libraries typically appear in lib/armeabi-v7a while the 64-bit versions live in lib/arm64-v8a.
The goal is simple. If an app supports a 32-bit architecture, the matching 64-bit build should also be included.
Developers may also need to update third party SDKs. If a dependency only provides 32-bit binaries, it will have to be replaced or updated with a version that supports 64-bit architectures.
Testing will matter too. Google suggests verifying behavior on the Wear OS emulator running a 64-bit system image. Since apps submitted to Google Play already need to target Wear OS 4 or newer, many developers are likely testing in environments that are already 64-bit only.
From a user perspective, this change will mostly happen behind the scenes. But underneath it all, Wear OS is following the same path Android phones took years ago as Google slowly pushes its platforms toward a fully 64-bit future.
Whether smartwatch apps suddenly feel faster because of it is another question. But one thing is certain. If developers want their apps to stay on Google Play, they will need to make the shift.
