It may be useful to have a recurring alarm primitive similar to setInterval.

[marcoscaceres]

Feedback from public-script-coord:
If you want a pretty API consider parsing cron patterns ( http://crontab.org/ ) like node's cron module does ( https://github.com/ncb000gt/node-cron#another-cron-example )

[mounirlamouri]

The cron syntax isn't that bad actually. We should have a look but maybe it could be done in a later version?

[marcoscaceres]

Sure, but I think we should first see how developers cope with dealing with working with dates. I would certainly would not want to use the nasty 1 * 1 0 whatever nasty-ass-unix-syntax(:tm:), but a JSON human friendly alternative that includes the timezones would be quite nice.

[mounirlamouri]

Do we agree that this is anyway something we should leave for later?

[marcoscaceres]

Not sure, tbh. Seems fairly fundamental. But I can also see a good argument for deferring.

[mounirlamouri]

Not sure, tbh. Seems fairly fundamental. But I can also see a good argument for deferring.

Application logic can take care of that pretty easily and the usage for that for the moment would be a calendar application. It doesn't seem to be huge enough to make it a priority to move the burden to the platform.

[marcoscaceres]

I'm willing to see how things work on the Moz side first with the Alarm API. @cdumez, it would be great if Tizen folks can also provide feedback with the Tizen equivalent.