OK, so we live in the bring-your-own-device (BYOD) era and everyone should take responsibility for their own phones. But if you work in IT, it might be timely to send a reminder email to everyone this afternoon pointing out that the onset of daylight saving may play havoc with their alarms.
Picture: Marcus Hansson
At 0200 on Sunday morning, clocks go forward an hour in most Australian states (except WA, which is already so far away no-one else minds, and Queensland, which needs to take a long hard look at itself). While the loss of an hour's sleep is less of an issue given the Labour Day public holiday in many states, people who do have to work (or be somewhere) on Sunday morning might not want to trust their smartphone alarms to perform properly.
In theory, there should be no problem, but in the past we have seen some notable bugs. In particular, iOS 4 developed an unusual bug where recurring alarms failed to work. Apple's response at the time was churlish, essentially telling users to put up with it until it was fixed. We haven't seen similar reports for iOS 7, but given that product isn't bug-free, caution (and a backup clock) are advised, no matter what platform you use.