Alarm API in Connect IQ 1.2

In the Garmin announcement about the version 1.2 of Connect IQ, they mention an alarms feature.

Watch APIs
...
Finally, we have opened up an alarm feature, giving you the ability to set an alarm for the future that will alert the user to come back into your app. Imagine setting your parking meter time and location, then getting an alert when you need to walk back to get your car or pay for more parking.



http://developer.garmin.com/index.php/blog/post/announcing-connect-iq-1.2/


I've been looking at the API documentation with 1.2.1 and though I might just be blind I'm not seeing anything I would expect is related to this alarm functionality. Am I missing something or has this not included in this version of the SDK? A forum search turned up nothing. Thanks!
  • It was part of the 1.2.0 SDK public beta, but didn't make it into the final 1.2.1 SDK release. I did tinker with it a bit.

    The functionality in the beta wasn't really alarm support per-se, it was a notification system that allowed your app or widget to schedule a wakeup event (not available to watch faces). When you created the notification object instance, you gave it a notification time, a display message, and a dictionary of properties. You scheduled that notification with the system, and when that time passed your app would be started (if it wasn't running) and the AppBase.onEvent() handler would get invoked with that dictionary and the message would be displayed as a toast.

    I'm not sure why it didn't make it into the final release, but it does appear that some artifacts of the implementation were left behind. Specifically the AppBase.onEvent() callback did not get removed.

    Travis
  • Thanks for the response Travis. I was thinking of using it with my kitchen timer app to have the app timer continue running in the background and then re-open and alert the user when their timer finished. Hopefully we'll hear from Garmin whether or not this is in their future plans.
  • Former Member
    Former Member over 9 years ago
    The feature definitely isn't permanently cut, it just wasn't ready for prime-time when the 1.2.0 cutoff came around. I am not sure what plans are for bringing it in are at this point. I think it is possible it will come in with a 1.2.x update, but it may have to wait for the next major release.
  • The feature definitely isn't permanently cut, it just wasn't ready for prime-time when the 1.2.0 cutoff came around. I am not sure what plans are for bringing it in are at this point. I think it is possible it will come in with a 1.2.x update, but it may have to wait for the next major release.


    Gotcha, thank you for the update Brian!