Hi Apple Team,
I hope you are doing well. I am reaching out regarding the upcoming watchOS architecture requirements announced in your official communication.
According to the notice, beginning April 2026, watchOS apps uploaded to App Store Connect must include the arm64 architecture and be built with the watchOS 26 SDK. zoom current watchOS app, however, only supports arm64_32, and the app size is already over 60 MB in its current form.
If we add support for both arm64_32 and arm64, the binary will almost certainly exceed the 75 MB app size limit, and potentially violate the size constraints for each architecture slice as well. This raises practical concerns about how a dual-architecture watchOS app can remain within the required size limits.
Could you please advise whether Apple has any recommended approach or best practice for this scenario? For example:
Does Apple suggest that developers transition to arm64-only and drop support for arm64_32 devices?
Are there any exceptions, additional guidelines, or alternative mechanisms for handling apps that exceed the size limit when including both architectures?
Are there recommended techniques specifically for watchOS to reduce binary size when supporting multiple architectures?
Any guidance would be greatly appreciated, as we want to ensure our watchOS app remains compliant with the new requirements while continuing to deliver a reliable experience for our users.
Thank you very much for your support, and we look forward to your advice.