64-bit for Wear OS: requirements from 2026

# Wear OS to Require 64-Bit Apps Starting September 2026

Google is introducing a requirement for 64-bit versions of apps for Wear OS starting September 15, 2026. New apps and updates with native code must include 64-bit libraries in addition to 32-bit ones. This will boost performance on smartwatches and align the platform with Google TV.

Support for 64-bit processors has existed since Android 5, but it's now becoming mandatory for Wear OS. Google Play will continue distributing 32-bit versions on compatible devices, while blocking incompatible uploads in the console.

Checking and Migrating Native Code

Developers need to analyze the APK or AAB for .so files in the lib folder. For ARM:

• 32-bit: lib/armeabi-v7a
• 64-bit: lib/arm64-v8a

For each 32-bit ABI, add the corresponding 64-bit one with identical functionality. Use APK Analyzer in Android Studio for inspection.

# Example lib structure in APK
lib/
├── armeabi-v7a/   # 32-bit ARM
│   └── libexample.so
└── arm64-v8a/     # 64-bit ARM
    └── libexample.so

Test in the Wear OS emulator. Pay attention to loaders like SoLoader and outdated OpenSSL—update them for 64-bit mode.

Steps to Prepare Your App

• Analyze dependencies and SDKs for native code.
• Compile 64-bit .so files for all supported ABIs.
• Verify functionality in a 64-bit emulator.
• Upload to Google Play with both versions.
• Monitor logs for native library loading errors.

Non-compliance will result in publication blocks. The 64-bit version must provide the same API and performance.

Key Points

• Starting September 15, 2026: new APK/AAB files with native code require 64-bit libraries.
• Google Play blocks incompatible files in the console but supports 32-bit on devices.
• Check lib/armeabi-v7a and lib/arm64-v8a in APK Analyzer.
• Update SoLoader and OpenSSL for stability.
• Test in Wear OS emulator for verification.

Wear OS Update Context

The requirement is synced with changes in Google TV. Earlier in 2025, they added Gemini, Circle to Search, and AI Mode for training. These features are optimized for 64-bit, accelerating the migration.

Mid- and senior-level developers will appreciate the focus on ABI compatibility: avoid partial 64-bit support to prevent losing 32-bit devices. Full duality is key—lib for arm64-v8a + armeabi-v7a, x86_64 + x86 (if needed).

— Editorial Team