Google Gets Serious About Smartwatches: Apps Without A 64-Bit Version Will Be Blocked In Six Months

Google announced a new requirement for the smartwatch ecosystem, and starting September 15, 2026, all new apps and updates to existing ones for Wear OS will have to include a 64-bit version alongside the 32-bit one. If a developer fails to meet this condition, their app will be blocked from Google Play. For its part, Google itself introduced a similar requirement for mobile Android back in 2019, and in 2024 released fully 64-bit Android 14. For Android TV and Google TV, the same rule goes into effect as early as August 2026.

Starting September 15, developers are required to provide 64-bit versions of their app code — meaning if an app uses C/C++ or other languages that compile to machine code, you'll need to build it for the arm64-v8a (64-bit) architecture in addition to the existing 32-bit version for armeabi-v7a. Google isn't dropping support for 32-bit devices, and the app store will still deliver 32-bit versions to older watches that don't have a 64-bit processor, but new builds and updates must include both variants. Earlier, OS users got the ability to create personalized watch faces.

In the official Google blog, they cite several reasons for these changes. First, 64-bit architecture delivers a performance boost and lays the groundwork for future innovations; plus, it's required for modern memory tagging technologies, which improves security. Another argument is support for more than 4GB of RAM — while that much memory seems overkill for smartwatches right now, Google is looking ahead: active adoption of on-device AI models on wearables will need big resources. 32-bit systems simply can't see beyond 4GB of RAM.

Right now, smartwatch owners probably won't notice the changes. Google Play, which recently received a major update, will keep serving 32-bit versions to older models, so they won't be left without updates, but going forward, the transition will allow for more complex and secure apps on newer devices. Watchmakers that have so far been releasing models with 32-bit chips will face a choice: either move to 64-bit processors or lose compatibility with future versions of Wear OS. Google has already made it clear which direction the platform is heading.

For developers, the main headache is not forgetting about libraries. If some old SDK still only exists in 32-bit form, you'll have to find a replacement or convince its authors to release a 64-bit version. There's time to do that until mid-September.

Do you use Wear OS smartwatches? Do you think you'll notice a difference after the ecosystem switches to 64-bit apps? Share your thoughts in the comments.