[Clock][UX] Add timers functionality

Thanks for taking the time to report this bug. Timer was removed for the following reasons,
- The platform did not support notifying the user when the timer was over. As a result if the user set a timer for 15 mins and the screen turned off, the clock app was suspended and even if the timer was over, there would be no audible notification.

- The clock redesign was done in the end of July 2014 while RTM milestone was planned for October 2014 giving me about 2-3 months to rewrite the clock app. Since reaching the RTM milestone we have been focusing on bug fixes and been in maintenance mode.

I can get started on this when I get a design for the timer feature and also the platform supports waking up the device to notify the user. I am afraid I cannot give a ETA for this.

I am tracking the SDK + Indicator-datetime support at bug 1427714.

Thanks! I don't quite understand the "support notifying" issue, though; obviously it works for regular alarms, timers are the exact same thing? you calculate the time when it should ring, set up a new alarm (in the system, not the UI), and it shoudl work like an absolute-time alarm?

Well the issue with using the alarms backend for the timer use case is that,

1. They would appear in the indicator-datetime as an alarm. While we could filter out these special one-time alarms by tagging them as timers to ensure that they don't appear in the indicator it felt like a hack. Also the notifications shown for a timer would include the snooze button and show the actual time of the alarm say 10:30 AM rather than the timer duration 00:30 etc.

2. It also turns out the EDS is a convoluted mess and is not performant enough on the phone. So if you create a timer for 5 seconds, then by the time the alarms is added to the EDS backend followed by it appearing in the indicator-datetime, that 5 seconds would have already passed. At the moment, the SDK devs are creating a much simpler DBUS backend to fix these performance issues since using EDS for this purpose is an overkill.

Anyway the good news is that a simpler, clean API is in the works. Once that is done, the backend story would be much stronger IMO and also give 3rd party apps to create alarms and timers easily which at the moment is not possible since they require access to the EDS database which is restricted to the core apps like clock, calendar only.

Not implementing this will result in the same thing that happened with android: A ton of 3th party apps that implement core functionality with varying degrees of quality.

There are already a number of timer apps available, that all look very out-of-place on an ubuntu touch device...

https://uappexplorer.com/apps?q=timer

Waiting for UX design

Status changed to 'Confirmed' because the bug affects multiple users.

I have a UX request when setting the timer. In addition to setting the time remaining until it expires (as you'd expect), I'd like to also switch to the ability to setting the clock time that I want it to expire. This would be very similar to setting an alarm of course, but the alarm setting UI is geared towards persistent alarms, not ephemeral ones.

Example use case: there's a one-off thing I need to do at 2pm. I could set an alarm for 2pm by adding a new alarm, and then going in and deleting the alarm after it has rung but this is tedious. Alternatively I could calculate the time until 2pm myself and then quickly set a timer for that length of time. This way there is no alarm to delete after it has expired. I'd like to just go to the timer section and add a timer to ring at 2pm by toggling to an "ETA" display instead of "time remaining" and setting it from there.

@Robie, that's a great idea. I have appended it to the bug description to ensure we don't forget it.

A proposed lifecycle solution from bug #1502628:

I would like to be able to send a notification to the user after a set amount of time. Additionally, I would like the user to be able to respond to the notification with a couple of buttons (e.g. Yes/No or similar).

This could also be used by the clock app for the timer functionality.

Currently, this is only possible with the push notification service. But, as a developer, I do not want to implement the complex push notification service or have to run a server for this simple use case, and as a user, I do not want to depend on network connectivity for this functionality.

This could be solved with some kind of interface to anacron that can schedule a notification to appear at a specified time.

On Tue, Oct 13, 2015 at 01:30:57PM -0000, Sam Bull wrote:
> I would like to be able to send a notification to the user after a set
> amount of time. Additionally, I would like the user to be able to
> respond to the notification with a couple of buttons (e.g. Yes/No or
> similar).

+1. I had thought along the same lines but didn't know where to file it.
Thank you for noting it.

This would also enable, for example, an offline reminders app.

Exactly my usecase. I'm making a nagging reminders app, that will nag you more and more frequently till you complete a task.