Allarm subbornly keep going on for full 15 mins even if I'm obviously in activity (e.g. bicyle)

KiltedTim wrote:

I understand the underlying idea perfectly.

Here's the answer to the technical question: This is how it's designed to work. Full stop. If you don't like it, tell Apple and/or go buy something else that works the way you want it to.

You can argue your point all you like, but that will not alter reality.

---------------

I understand the underlying idea perfectly.

After everything you posted here you can't blame me (or anyone else for that matter) for having a hard time to really believe you actually understand the idea.

This is how it's designed to work. Full stop. This is how it's designed to work. Full stop. If you don't like it, tell Apple ...

Well, from the very beginning the whole idea was actually the feature request rather than whining, see the "=> As a possible solution, I would suggest keeping ..." at the bottom of my very first post.

I'm well aware of how the alarm works right now, the whole point of this is how things can be improved, not complaining ...

I actually already posted here, that I already created a feature request in Apple Product Feedback system, as suggested by another user Alancito (post here), who actually understood the idea literally immediately (no additional explanation or discussion was necessary, no arguing, just simple practical help advice on spot in her/his very first response).

First, based on your comment, it does not look like you really got the idea behind my first post above.

It literally does not matter, why I set the alarm(s) and or why I didn't /check them and switch allarm(s) off: there is plethora of trivial valid reasons:

• I could have simply set the alarm up by mistake,
• or could I set it up intentionally in the morning, and then something unexpected jumped in in meantime and I had to change plans in hurry - e.g. school called, that something happened with my kid, and I had to quickly go = there is not time to think about all small trivialities, like alarms I set hours ago ...

The most valid and frequent reason is this: Apple Clock app allows quite complex settings for alarm - e.g. one can configure alarm going off repeatedly each day, or repeatedly during particular subset of days in week, etc. ...

This means that these alarms are not configured as one-off, but rather configured to go off regularly based on the configured schedule, in which case, if for example you get unexpectedly stuck in the traffic congestion, the alarm will go off while you are still riding the motorcycle ...

Plus, remember, I WANT the alarm to go off, however, what I do NOT want is that alarm will be rumbling for full non-sensical 15 minutes, but instead only for 30 secs (the main point of my whining).

The main point here is, that products (like iPhone, Apple Watch, applications) are supposed to make life easier for users, with the aim to minimise suffering, and remove as much mundane and unnecessary tasks.

Why should users be overloaded by remembering and checking ALL the possible settings all over the place, just to avoid something that can be simply avoided automatically without bothering the user ...?

And on side note, as a reaction to your comment: Sorry to say this, no offence, but making comments that this is user error / mistake / laziness / or misunderstanding of the feature, without thinking it through first well is really not helpful.

I'm sorry, but you are simply missing the main point here, which was already summarised in my previous message:

"Plus, remember, I WANT the alarm to go off, however, what I do NOT want is that alarm will be rumbling for full non-sensical 15 minutes, but instead only for 30 secs (the main point of my whining)."

Also, you are calling my argument ridiculous, so please, just for a moment think whether you really considered perfectly normal real-life scenarios, which can just can make your arguments ridiculous:

• I have 2 kids, each has various trainings (e.g. karate, gymnastics, etc. ...) across the whole week (each day actually) + I have really busy professional life, where meetings running over or staying in work longer is a norm, rather than an exception.
• Given the intro in the point right above, I have created set of alarms (each day of week different set of periodically repeating alarms (= period is week)) which will go off before I need to take one kid in to that training, and the other one to the another training, and then, once trainings are over, I have set another set of alarms to go of before I need to pick kids from the trainings (again all alarms are configured for each day as periodically repeating). This is to make sure that I will be on time to pick kids from their activities, which can take anything from 1 to 3 hours depending on kind and a day ... (again I have busy professional life, where I work from home sometimes + I cook + I might even fall asleep = I need these alarms to go off in normal life)
• Also, I have set of important repeating meetings I need to set the (periodic repeating) alarm for to make sure I will be alerted when they are approaching, since I have tons of other less important meetings, and work, which tend to overrun ...

I have every reason to have as complex configuration of alarms as I need.

I have every reason to *NOT* touch/change my configuration of the alarms, or mess with it constantly, so I can be for 101% sure that the alarms are correctly configured for the next period/week without necessity to constantly re-check everything each time after I would be forced to change something.

All these arguments create potential for occurenco of normal real-life situations, when alarm will go off while I'm riding on motorcycle or bicycle - and I do that a lot, since I need to move around either ad-hoc (school calling unexpectedly), or simply getting stuck in traffic congestion way lonnger than anticipated, or staying in work or school a bit longer then planned/anticipated, etc. ...

So, after spelling out my arguments (practically spoon feeding), whose arguments are ridiculous?

You can't respond to the alarm when I'm riding on a motorcycle in dense traffic - leather sleves and gloves are completelly covering the Apple Watch ...

The similar situation applies for riding a bicycle - it is just nonsensical and dangerous to mess with Apple watch in dense traffic.

The question is: Why the alarm goes on for full 15 mins despite Apple products can perfectly detect that I'm in activity (and, btw, actually they are already well aware of that) since I'm having Apple Watch right on my wrist ...

Thanks - this is actually useful. Though I need to find suitable category for which to report the feature request, since they do not list the Clock app amongst apps you can report issue for. I will think of something.

I'm really sorry to say this, but what is actually ridiculous here is, that you are trying to "explain" something to me about the topic at hand, when at this point it became pretty clear, that you simply do not understand the underlying idea behind the topic itself ...

Honestly I'm not quite sure what is going on, perhaps you didn't really read what I wrote, or perhaps you don't even want to understand it ...

The Apple watch has sensors like accelerometer, gyroscope, GPS, compass, etc. ... , and it can pretty reliably automatically detect when you start an activity (walking, running, riding a bicycle, swimming, etc ...).

This auto-detection has been already working on Apple Watch for ages ...

Thus, again, responses like "The device is not psychic" are really way off the topic here, and it is hard to find any rational reason why such a response has been even brought up here, other than childish dissent ...