924474 - [Clock] Feature: When an alarm fires long past the target time, make the UI more obvious that it's an old alarm

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Clock, defect)

Description

[Jason Smith [:jsmith]]

Build: 1.2 Hamachi 10/2/2013

STR

1. Create an alarm to go off in 5 minutes
2. Turn the phone off
3. Wait about an hour later
4. Power the phone on again

Expected

The phone powers on without the alarm going off.

Actual

The phone powers on with the alarm going off on startup. A bit annoying, as the alarm is no longer relevant if the power was off when the alarm would have fired.

Comment 1

[Dylan Oliver [:doliver]]

I'd argue that it's more useful to know that you missed an alarm than to ignore it altogether and would support a WONTFIX resolution.

ni? to UX for comment.

Comment 2

[Juwei Huang[:juwei]]

Attachment: Alarm time out_20140115.pdf

I both agree with Jason and Dylan. It seems like too bothersome for users to still see the notification after such a long time, yet we couldn't dismiss the alarm automatically otherwise users might thought the alarm never ring.
I have an idea that we probably can have a banner on lockscreen to indicate users that the alarm has been expired after the clock time out. This design will not occupied all of the lock screen, so it won't annoy users. And also, the banner provides enough information that the alarm ringing before.
I attached a draft spec for it, if there's any further concern please let me know :)

Comment 4

[Juwei Huang[:juwei]]

Attachment: Alarm time out_20140123.pdf

Just have an internal review with UX team, the previous attachment would be more like a compromise solution since we haven't support opening application via lockscreen, the notification would be less functional and hard to call attention.
Here's the new flow:
Once the alarm went off after 15 minutes, the alarm would be expired along with the notification" Alarm expired", then tap on OK to close the page.
This flow can sort of decrease the awkward feeling of showing an on-going alarm when power on the device 2 hours afterward. The previous flow can be the backup version once we got advance function on lockscreen.

Comment 5

[Dylan Oliver [:doliver]]

[priority] --> tracking-b2g:+ conversion

Comment 6

[Dylan Oliver [:doliver]]

Removing tracking+, will prioritize along with features

Comment 7

[David Ross]

Experiencing this issue under nightly builds (most recently 20150316160204). Noticed also happened on previous nigthly too. 

Set an alarm for just after midday at 9pm last night. Restart the phone this morning at 6am and the midday alarm is going off during the blue Firefox OS splashscreen. Have to wait many long moments before alarm can be turned off.

Comment 8

[BMO Automation]

Firefox OS is not being worked on