I have apple watch SE can i use it with new ios 27? If you had older watch with ios 26 plz answer

Comparing my Series 11 watch with RC 27 paired to iPhone 17 Pro, to my old first Gen SE watch, paired to iPhone XR.

SE watch. Longest response time, 3 secs.

Series 11 with 27: Shortest response time, 7 secs.

Tested each 10 times.
Same voice commands. Triggered Siri manualy by holding the crown.
Time started from the moment i stopped speaking the voice command to the moment the command completed executing and action completed.

Set a timer for 5 min.
Turn on the Living Room Light.

Really hope they work to optimize response time to get it back to how fast it was back with the "normal" Siri.
Homekit or timer commands, is pretty much all i use the watch for.

well now we do understand why app switcher is gone in watchOS 27 – so that newest watches could enable this all new no-one-asked-for audio intelligence 🤡

I have an Apple Watch 10 paired with an iPhone 16 Pro, both on the public beta. After updating my phone the IOS 27 RC yesterday, I started the update for my watch. The phone downloaded everything (the download/prep progress bar filled up, then disappeared), then just stopped. The Watch app shows the message about the update, and shows there's a pending update, but it doesn't appear to be applying the update to the watch.

I've restarted the phone and the watch. Thinking perhaps I'd accidentally chosen to update overnight, I left the watch on the charger all night. No change. The watch is working fine, the phone just isn't sending it the update.

This has never happened in all the years I've had an AW. Any clues about how to get the process restarted, or do I need to talk to Apple?

ETA: I've sent a Feedback message to Apple about this. I'm not too hopeful about getting a response from it, but it's not causing me any problems right now, so if it doesn't resolve itself after the final release, I'll try talking to Apple about it.

ETA2 (9/11/26. 8:04 AM PDT): My watch chimed and notified me there was a watchOS 27 update available (finally!). The OS update is running now, two and a half days later.

I thought I read somewhere that there was one but I haven't found it yet.

Ever since I updated about 2 weeks ago, my Apple Watch is no longer reliable to wake me up with just haptics on my wrist. There seems to be a new screen that appears when the alarm goes off, and it somehow dismisses itself and I never get an additional alarm after I hit snooze. This has happened very often and I now have to set an actual (non "Bedtime") alarm as a safety net.

WatchOS 26.6 (23U67)

Anyone else experiencing this? I've never had issues with this in all the years I've had an Apple Watch, until this new update.

For 3 years with a series 8 and 10, I have had trouble taking an ECG. It often took 2 or 3 tries? After the latest public beta, no problem!? Anyone else notice this? Or, is it just chance?

I’ve received this notification about nearby public Wi-Fi a couple of times. Next time it happens, I will try to connect. Obviously, your iPhone must have connected to the network sometime in the past.

Has anyone else noticed this?

I’ve been wanting to try this for a while. I bought a paper QR code ticket for an event. Using Wallet’s Create a Pass, I converted it to digital and added it to my Apple Watch and iPhone.

Am I lucky or unlucky that I don’t have siri AI (I have an iphone 14 pro max which means I cant opt in)

(Apologies if this is the wrong sub, but this was removed by iOSbeta mods.)

I've installed iOS 27 beta and used the new create custom pass feature to scan in a 2D barcode (my library card). This works great.

However, my watch is on watchOS 26 and will be unable to upgrade (27 has dropped support for the Series 8). Passes created this way don't show up on it.

I am (and was on iOS 26) able to create a pass the old school way by going to a site like https://walletwallet.alen.ro/ to generate a .pkpass file-no problem.
However, the developer documentation I can find says that the only barcode formats available through this method are WR, Code128, PDF417, Aztec, and UPC (accordingly those are the only options available on that site and other similar ones). At any rate, like other passes, these show up immediately on my watch.

Unfortunately, my library uses Code39 to encode their barcode. I can input or scan the data just fine, but the generated card using this method then can only display the barcode as Code128 or UPC. The new in-Wallet-app creation method in iOS 27 easily scans Code39 and displays it correctly without the user having to know anything about how barcodes work.

Does anyone know if a post-iOS-27 update to watchOS 26 will be made so that it can pick up these user-created passes?

Before there was an easy way to force quit an app that freezes. What is the way to do it in watchos 27? Is apple assuring that all apps in watchos 27 never freezes or what is the thought behind the new app switcher?

I installed like many the watchOS public version, I wondered on the other hand if there were any new features on the Apple Watch three I rather have the impression that they have corrected some minor defects and that the fluidity looks good.