Why the Google Clock Timer Annoys Me

Foreword

This webpage contains 19 MP4 videos that sum up to 6.5 Mb in total. I tried to compress these videos down as much as possible, but that didn’t work too well.

This post is an overkill, waste of time, and really has zero reason to be this unnecessarily elaborate. However, considering the amount of effort sunk in (see Sunk Cost Fallacy), this page has to exist.

To go the extra mile, I’ve decided to write some code in my absolute, most favorite-est language of all time: JavaScript ¹. Since the videos occupy a good chunk of vertical space, I’ve created a few buttons to hide/unhide all videos, hide individual videos, and unhide individual videos.

To toggle visiblity of all videos: Click Here. Currently: [Unhidden]. You can individually hide/unhide videos after unhiding/hiding all of them.

<rant>

Around late 2020 / early 2021, I found out about Google Clock [1], an Android application with a Spotify integration that let the user set an alarm sound from their Spotify playlist. In order to wake up to Death Metal, Lo-fi Beats, Indie Rock, Jazz Fusion, or Math Rock from my Spotify playlist(s), I downloaded the app to try and see if it would work. After 2½ minutes of testing, I noticed that it… did not work.

I should have uninstalled the app an moved on, but I kept it around and started using it despite having a perfectly-functioning, already-installed clock app . However, upon using Google Clock, I discovered something infuriating - the input method to set timers. The pre-installed clock application on my phone was OnePlus Clock [2] and the input method to set timers was something I never paid any attention to before - the sign of a good design. On the other hand, the method to enter and change hours, seconds, or minutes in Google Clock was horrendously vexatious.

Let’s begin to delve down this path of superfluous insanity by comparing interfaces first. Figure 1 shows the interface of the OnePlus Clock timer and Figure 2 shows the interface of the Google Clock timer. For the rest of this ramblings post, I will be referring to Google Clock timer as GC and OnePlus Clock timer as OPC.

Figure 1: The interface of OnePlus Clock. To hide the image: Click Here

Figure 2: The interface of Google Clock. To hide the image: Click Here

One of the first differences that we note is that GC has an extra “00” button. The usage and benefits of this button is not explored in this ramblings post (see Nuances).

Setting a Timer

Next, we take a look at how a timer of 12 hours, 34 minutes, and 56 seconds can be set on both apps. GC has only one way to send this as an input - from right to left, similar to how one would enter the transaction amount on a debit/credit card machine. This is shown in Figure 3.

Figure 3: Setting a timer of 12 hours, 34 minutes, and 56 seconds in Google Clock. To hide the video: Click Here

The OPC also allows setting a timer the same way, so for the sake of saving a couple-hundred kilobytes, it isn’t included as a video here. The other method to set a timer in the OPC is to by individually tap the hours field, minutes field, and seconds field. I refer to the tapping of the fields as “focusing”. This is shown in Figure 4.

Figure 4: Setting a timer of 12 hours, 34 minutes, and 56 seconds in OnePlus Clock by "focusing" fields. To hide the video: Click Here

Let’s compare both methods by number of taps to set a timer for 12 hours, 34 minutes, and 56 seconds. This is in Table 1. Since setting a timer in OPC can be done in two ways (Figure 3 & Figure 4):

• OPC method (1) will be used to refer to as the method to set a timer as shown in Figure 3 (exactly the same as GC).
• OPC method (2) will be used to refer to as the method to set a timer as shown in Figure 4

Table 1: Number of taps for setting a timer of 12 hours, 34 minutes, and 56 seconds on Google Clock and OnePlus Clock using method (1) and method (2)

Let’s compare the amount of taps it takes to change individual digits. We will now take a look at six comparisions in total with a base timer set to 12 hours, 34 minutes, and 56 seconds:

• 12 hours -> 22 hours (tens digit in the hours field)
• 12 hours -> 13 hours (ones digit in the hours field)
• 34 minutes -> 44 minutes (tens digit in the minutes field)
• 34 minutes -> 35 minutes (ones digit in the minutes field)
• 56 minutes -> 66 seconds (tens digit in the seconds field)
• 56 minutes -> 57 seconds (ones digit in the seconds field)

Before we begin, it must be noted that there are two ways to erase digits in GC as well as in OPC. The user can either hold down the backspace button to clear out (Figure 5) the entire timer or tap the backspace button individually to delete one digit at a time in reverse (Figure 6). Depending on which digit is to be changed, the user can choose either method to employ in order to efficiently reset and set that particular digit - this is explored in the upcoming section. Long-holding the backspace method will be referred to as Clear[LONGHOLD] and individually tapping the backspace button will be referred to as Clear[TAPTAP]. Additionally, I have decided to define long-holding the backspace button as 1.5 taps as it requires a slightly longer activation period compared to the simple tap.

With the OPC timer, included in the count of the taps is the “focus” tap as mentioned before for focusing the desired time field for which the numbers are to be changed. In Figure 7, changing a timer of 12 hours, 34 minutes, and 56 seconds to 22 hours, 34 minutes, and 56 seconds requires 5 taps: 1 focus tap to focus on the hours field + 2 taps to clear the field of its tens digit + 2 taps to set the new value.

The main intent of the upcoming section is to compare the three methods - Clear[LONGHOLD], Clear[TAPTAP], and by focusing the field.

Figure 5: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 12 hours, 35 minutes, and 56 seconds by long-holding the backspace button in Google Clock - Clear[LONGHOLD]. To hide the video: Click Here

Figure 6: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 12 hours, 35 minutes, and 56 seconds by individually tapping the backspace button until the ones digit of 34 has been cleared in Google Clock - Clear[TAPTAP]. To hide the video: Click Here

Figure 7: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 22 hours, 35 minutes, and 56 seconds with an initial "focus" tap in One Plus Clock. To hide the video: Click Here

Changing Digits:

- 12 hours, 34 minutes, and 56 seconds -> 22 hours, 34 minutes, and 56 seconds

GC: By using Clear[LONGHOLD], the user uses 7.5 taps to reset and set the timer (1.5 taps for Clear[LONGHOLD] + 6 taps to set the new timer). On the other hand, using Clear[TAPTAP] results in the user using 12 taps (6 taps for Clear[TAPTAP] + 6 taps to set the new timer). Clear[LONGHOLD] is shown in Figure 8.

OPC: The user uses 5 taps (1 focus tap + 2 backspace taps + 2 taps to set the tens digit). This is shown in Figure 7 (above).

Figure 8: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 22 hours, 35 minutes, and 56 seconds by using Clear[LONGHOLD] in Google Clock. To hide the video: Click Here

- 12 hours, 34 minutes, and 56 seconds -> 13 hours, 34 minutes, and 56 seconds

GC: By using Clear[LONGHOLD], the user uses 7.5 taps to reset and set the timer (1.5 taps for Clear[LONGHOLD] + 6 taps to set the new timer). On the other hand, using Clear[TAPTAP] results in the user using 10 taps (5 taps for Clear[TAPTAP] + 5 taps to set the new timer). Clear[LONGHOLD] is shown in Figure 9.

OPC: The user uses 3 taps (1 focus tap + 1 backspace tap + 1 tap to set the ones digit). This is shown in Figure 10.

Figure 9: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 13 hours, 34 minutes, and 56 seconds by using Clear[LONGHOLD] in Google Clock. To hide the video: Click Here

Figure 10: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 13 hours, 34 minutes, and 56 seconds in the OnePlus Clock. To hide the video: Click Here

- 12 hours, 34 minutes, and 56 seconds -> 12 hours, 44 minutes, and 56 seconds

GC: By using Clear[LONGHOLD], the user uses 7.5 taps to reset and set the timer (1.5 taps for Clear[LONGHOLD] + 6 taps to set the new timer). On the other hand, using Clear[TAPTAP] results in the user using 8 taps (4 taps for Clear[TAPTAP] + 4 taps to set the new timer). Clear[LONGHOLD] is shown in Figure 11.

OPC: The user uses 5 taps (1 focus tap + 2 backspace taps + 2 taps to set the tens digit). This is shown in Figure 12.

Figure 11: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 12 hours, 44 minutes, and 56 seconds by using Clear[LONGHOLD] in Google Clock. To hide the video: Click Here

Figure 12: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 12 hours, 44 minutes, and 56 seconds in the OnePlus Clock. To hide the video: Click Here

- 12 hours, 34 minutes, and 56 seconds -> 12 hours, 35 minutes, and 56 seconds

GC: By using Clear[LONGHOLD], the user uses 7.5 taps to reset and set the timer (1.5 taps for Clear[LONGHOLD] + 6 taps to set the new timer). On the other hand, using Clear[TAPTAP] results in the user using 6 taps (3 taps for Clear[TAPTAP] + 3 taps to set the new timer). Clear[TAPTAP] is shown in Figure 13.

OPC: The user uses 3 taps (1 focus tap + 1 backspace tap + 1 tap to set the ones digit). This is shown in Figure 14.

Figure 13: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 12 hours, 35 minutes, and 56 seconds by using Clear[TAPTAP] in Google Clock. To hide the video: Click Here

Figure 14: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 12 hours, 35 minutes, and 56 seconds in the OnePlus Clock. To hide the video: Click Here

- 12 hours, 34 minutes, and 56 seconds -> 12 hours, 34 minutes, and 66 seconds

GC: By using Clear[LONGHOLD], the user uses 7.5 taps to reset and set the timer (1.5 taps for Clear[LONGHOLD] + 6 taps to set the new timer). On the other hand, using Clear[TAPTAP] results in the user using 4 taps (2 taps for Clear[TAPTAP] + 2 taps to set the new timer). Clear[TAPTAP] is shown in Figure 15.

OPC: The user uses 5 taps (1 focus tap + 2 backspace taps + 2 taps to set the tens digit). This is shown in Figure 16.

Figure 15: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 12 hours, 34 minutes, and 66 seconds by using Clear[TAPTAP] in Google Clock. To hide the video: Click Here

Figure 16: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 12 hours, 34 minutes, and 66 seconds in the OnePlus Clock. To hide the video: Click Here

- 12 hours, 34 minutes, and 56 seconds -> 12 hours, 34 minutes, and 57 seconds

GC: By using Clear[LONGHOLD], the user uses 7.5 taps to reset and set the timer (1.5 taps for Clear[LONGHOLD] + 6 taps to set the new timer). On the other hand, using Clear[TAPTAP] results in the user using 2 taps (1 tap for Clear[TAPTAP] + 1 tap to set the new timer). Clear[TAPTAP] is shown in Figure 17.

OPC: The user uses 3 taps (1 focus tap + 1 backspace tap + 1 tap to set the ones digit). This is shown in Figure 18.

Figure 17: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 12 hours, 34 minutes, and 57 seconds by using Clear[TAPTAP] in Google Clock. To hide the video: Click Here

Figure 18: Changing a timer of 12 hours, 34 minutes, and 56 seconds to 12 hours, 34 minutes, and 57 seconds in the OnePlus Clock. To hide the video: Click Here

- Results in a Table

A summary of the above-results are displayed in Table 2. In the case of each cell in the GC row, the first number specifies the amount of taps required to set the digit by using Clear[LONGHOLD] while the second number specifies the amount of taps required to set the digit by using Clear[TAPTAP]. Between these two numbers, the number that is underlined is the fewer number of taps.

The green cells are the “winners” - the digit of that column would require fewer taps to be changed by using the clock app of that row.

Table 2: Number of taps for changing a digit of a timer set to 12 hours, 34 minutes, and 56 seconds. Each column represents the digit of the timer to be changed.

Nuances

There are a few points that I have decided to omit for the sake of keeping this ramblings post short ². These are:

• The usage of the “00” button offered by Google Clock is not explored. Including it would more effort and analysis into timers that have “00” in them - as complete fields (12 hours, 34 minutes, 00 seconds), between two fields (10 hours, 04 minutes, 56 seconds), and/or as a combination of the previous two (10 hours, 04 minutes, 00 seconds). I have, hence, decided to omit it to preserve my sanity.
• Every method to set, reset, and change a timer in Google Clock is also available in One Plus Clock. As is mentioned in the previous point, the only key difference is the “00” button.

Conclusion

In Table 1, both Google Clock and One Plus Clock have methods to set a timer by using 6 taps. This requires a timer to be set by sending inputs from right to left. The One Plus Clock also allows a timer to be set by individually selecting the hours, minutes, and seconds field; however, this requires 9 taps in total.

In Table 2, One Plus Clock requires fewer number of taps to set both digits of the hours field as well as both digits of the minutes field by using a method to select the field and then alter the digits. When it comes to the seconds field, the method to change the timer by using the backspace button for the entire timer requires fewer taps. Since the One Plus Clock also has this feature, it would be tempting to conclude that the One Plus Clock wins overall. However, in my observations (n=1) ³, once a user tends to stick to the “focus”-ing method, it becomes hard for them to switch over to the setting / clearing of inputs as described in the previous paragraph.

- Informal Conclusion

I don’t know what else to conclude. When I fisrt started writing this post (Jan/24/2023), I thought that it would take around one to two days to write this entire thing; it turns out procrastination was my unexpected friend and I finished writing this two and a half whole months later. But, uh, Google get your stuff together and let me individually set the timer fields. That’s pretty much it, lol.

</rant>

Footnotes

¹ This is a joke. I hate JavaScript. ↩

² And for keeping my sanity. ↩

³ The n=1 person is me. Well… I guess that it undermines the study. ↩

References

[1] https://play.google.com/store/apps/details?id=com.google.android.deskclock

[2] https://www.apkmirror.com/apk/oneplus-ltd/oneplus-clock/