I repurpose old Android mobile phones (from the KitKat/Lollipop era) to use as alarm clocks in my 3 young kids' rooms. After a while, it gets pretty tiresome syncing up the alarm clocks (eg. when the next day is a public holiday and you want to disable the alarm just for that day so that everyone can get a bit more sleep).
I thought it would be pretty cool if I could update all the alarm clocks remotely from a webapp. I couldn't find any alarm clock app that can be remotely controlled on the app store, so I decided to implement my own.
For the webapp, I repurposed another project of mine called Shopping Buddy. This turned out to be relatively easy, because it basically involved stripping away features like bookmarks and history, and trying not to break things along the way. It was done pretty quickly, and I called it Wakey Wakey.
The production site can be found at:
The Github repository can be found at:
Screenshots:
Now I needed an Android app that can talk to the backend, download the alarm schedule and basically function as an alarm clock.
For a humble alarm clock app, this turned out to be more difficult than I imagine. Unlike a normal app, an alarm clock needs to do a lot of platform-native stuff, including:
- running periodically in the background to schedule alarms
- activate the alarm, even if the application is not in the foreground, or the phone is asleep
- setup everything again after a reboot etc.
I initially turned to Javascript-based app development frameworks such as Cordova, which will require platform-specific plugins to implement the above functions. But there was no single plugin that provides all the necessary functions, and the ones available seem to be old and buggy, which will require a lot of tweaking and debugging before they might even be fit-for-purpose. So given the options available, it seems most sensible to go fully native instead.
I downloaded Android Studio 4.0 and pulled in code from a few alarm clock apps from GitHub, including the one from ASOP KitKat. I wanted to target SDK level 19, because I wanted the app to work with Android versions as low as 4.0. It came together slowly. I had prior experience on Android development with Java, and it was every bit as laborious as I remembered, nothing like the brevity and levity one feels when developing with a higher level language like Javascript.
The UI is extremely plain and simple. The client will turn the volume up to maximum, so the alarms will ring even if the phone has been accidentally muted or airplane mode has been switched on (yeah, I can't remember how many times my kids have done that to me).
Once an alarm goes off, it will continue for 10 minutes, or until the alarm is remotely disabled on the webapp. The code is actually there to dismiss the alarm by touching the screen, but I have commented it out!
Replication happens in the background to a local database, so the alarm clock will function even if wifi is down (provided the changes have already been replicated to the local instance before the network went down).
The Android client APK can be downloaded at:
The Github repository can be found at:
Screenshots:
Comments
Post a Comment