I don’t use alarms all that often, but when I do, it’s on the watch (which I wear while sleeping.) I haven’t noticed the problem you’re describing. I just tap the control and it seems to work almost every time for me, even on the smaller watch. Maybe once or twice it’s opened the alarm settings.
But I’ll agree that the control could be better.
Works fine as long as someone else isn’t trying to sleep while I have a chat with a very-perky Siri about the alarm-setting topic. :) And honestly, I’m not looking for a workaround. Something that worked is now broken, and needs to be fixed.
I’ve sometimes also gotten lucky by keeping my finger on the control for some indeterminate length of time. The whole thing seems to be random, dumb luck.
In general, I’m a big user of both Siri and Alexa. Most of our lighting is now automated in the main part of our smallish ranch-style house. Amazon has done a superb job of adding skills to tie up various manufacturers’ control hubs. We use Lutron Casetá devices for most of the lighting, a Chamberlain hub for our garage door, and some miscellaneous WiFi plugs for on/off lamps. Amazon integrates them all in the Alexa app so they become one seamless array.
I could do the same thing with Siri and the Homekit automations, but haven’t bothered because until xOS 8 I don’t think Siri was good or deep enough to merit a shift. At home Siri has been a handy cooking timer, a short-term forecast delivery system, and an occasional control for (yes) alarms and similar stuff. It also has been handy for quick numeric conversions.
In the truck, on the other hand, Siri and CarPlay are an amazing augmentation. I don’t mind using my voice at all for controlling maps, music, podcasts, or having texts read to me. It makes my longish commutes safer—not just for me but for other users of the road.
But at night, with my spouse already asleep and my vigilant Shelties ready to stand guard at any odd sound, using Siri to set alarms is a non-starter. That’s doubly true when the main method for setting alarms is acting all version-buggy.
I wonder if a newer watch is more sensitive? On my Apple Watch series 5, I have no issue clicking the on/off toggle, even late at night when my eyes are tired.
I’m wondering if it could also be viewing angle.
On my iPhone, for example, I find that the actual location you need to tap on a small object is slightly below the object. I think iOS is compensating for the fact that people usually hold phones at an angle, not perpendicular to their line of sight. Which means that if you are looking straight-down at it (or if it’s on a table and you’re looking from the top or a side), you may need to tap in a non-intuitive location.
If WatchOS is doing the same thing, then maybe tapping a small distance below the button will work better.
Possibly. The issue cropped up with a new version of WatchOS; it is possible that it was tested more against later models. I weigh that against the fact that while my Series 3 is now several years old, it is one of the three models that Apple is selling (Series 3, Series 7, and the Series “SE”). So I would think that if there were a tweak in the interface that they would test it against a model that is currently shipping.
Good thought, but I’ve checked that out thoroughly, in the daytime, when I’m not trying to be done with Apple tasks for the day. Any spot on or near the toggle results in the unwanted behavior.
One additional bit of information: the expected behavior is for the panel containing information for the existing alarm to highlight when it is being tapped (resembling a button push). The expected behavior for the toggle switch is for it to change state (sliding the round “slider” to the right and exposing a green underlay). Tapping the toggle switch is highlighting the entire panel.
I recognize that from HyperCard days, when I got sloppy defining a button region.
This inspired me to experiment. Now I can get it to work nearly every time. Try this: touch lightly and move 2 mm (1/2 inch) horizontal to the left and back again and let go. I have success with moving a bit more than that too. “Lightly” seems to be important as well as movement.
If it works, you get no sign before you let go, but if the alarm time is dimmed to show that you have triggered the “Edit Alarm” menu, you can move upward and out to the right with your finger to abort.
I have not tested this in bed yet. The concentration required to get this to work seems a poor fit for that stage of the day.
I have the Apple Watch Series 4 (GPS) 40mm case. Maybe the 44mm case is more forgiving?
I have the 44mm Series 4 (GPS & Cellular) and nothing you outlined works for me.
I have had some random luck with a light touch; also with a heavy touch, a short touch, a long touch. Your observation about needing to concentrate to get this to work pretty much captures why this is an issue.
The Apple Watch is a masterpiece of engineers sweating the small details, so I’m sure that it’s not Apple’s intention to make its users have to think about how and where and how hard they are tapping to make a basic function happen. Whether it’s a basic model or one of the designer showcase models, they’re all based on the same body, electronics, display, and software.
Just before I purchased my watch, I reviewed an Android-based watch with some kind of mineral name attached to it. (Rock? Bone? Fossil? I don’t remember.) What I do remember is how attractive and solid the watch body was, and how putrid and inscrutable the interface was. It got hot if I tried to look anything up on the display, and the battery barely carried it through a day.
Apple’s practice of letting others make a run at a new market, then introducing what the product should have been all along, is on display with the Watch. That’s why I hate to see small annoyances like this creep into the interface.
Lol! Good guess. Turns out I was right the third time. Fossil.
A super light tap works for me on my 40mm Series 6.
Matt, I do the same thing and now have the same exact problem on my Apple Watch (Series 4). Because I assumed it was just me, I hadn’t thought about filing a report to Apple… maybe I’ll do that now.
Thanks for writing about it.
I use mine for wake up alarms but they’re always on. I don’t turn them off. I wear my watch to bed and charge it during the day when I’m inactive and pinned to my desk anyway.
I also use different alarms for different days so I’m not turning anything on or off regularly. I do turn rare alarms on manually.
I just checked. I see what you mean but I have no trouble whatsoever hitting the toggle instead of the whole-alarm-button. Mine’s a much later model but not the latest.
I bet there’s a use case that Apple doesn’t see as frequently, even though it makes sense for a software engineer.
I am a little confused by what you seem to be describing. On my Watch, the Alarms app saves every defined alarm, but when one is active (i.e. set to make a sound at a given time), the sound can only be stopped by turning it off.
You said you wear yours to bed. I am completely unfamiliar with the “Sleep” app; is that what you use to schedule alarms? And even there, how do you keep your alarm from continuing to sound off once you’re awake?
I’m just trying to make sense of something that sounds counterintuitive to how alarms tend to work, as I’ve never seen an option to set a recurring alarm on the Watch.
On the watch, the alarms have “stop”, (can’t remember what it’s actually called), and, optionally, “snooze” buttons while they are ringing. If you stop it one day, it’ll stop ringing that day but will still ring again the next day for which it’s active. If you snooze it, it’ll ring again in 9 min, (I think), up to some limit that I’ve never explored. (Traditional digital clocks typically ring for an hour, then stop).
Yeah, if you snooze it, then want to turn it completely off, you’d probably have to disable the alarm. I stopped using snooze a long time ago. For me, it just makes it harder to wake up. If you wait for the next snooze to ring and then hit “stop”, it’ll be done ringing for the day but will ring on the next active day.
I do use the sleep app, but that just has a time setting for sleep “focus” combined with an extra alarm. I was using the alarms to wake myself long before the sleep app showed up.
Thanks for that description. The “stop” behavior you describe is different than what I’ve experienced all this time. Tapping “Stop” (or swiping down from the top of the watch face, which is much, much easier) stops the alarm for the day, and tapping “Snooze” keeps it active but sounds again at 9 minutes.
I think the difference is you may have set up a schedule in the Sleep app, so your alarms recur on that schedule. I do not have such a thing set up (I like to sleep, but there’s only so much about my life that I want to hand over to Apple…or maybe there’s so little that I haven’t!). So when I “Stop” an alarm, the Watch remembers that alarm but it is now inactive unless and until I turn it on again. Since my schedule is just irregular enough that I’m never really sure which of 3 or 4 alarms I want to set for the next day, I activate the one I want at night.
Alarms have an optional repeat setting that can be set to never (default), every day, weekdays, weekends, or any of the individual days of the week.
Ah, I see that in the settings dialog. I’ve been so irritated about being brought there against my will that I’ve been completely ignoring what’s there! The only other thing I’ve ever needed to with an park is delete it. As explained above recurring alarms make no sense for my particular situation.
Thanks Doug!