A few weeks ago I was challenged to find a countdown clock for the Enterprise Mobility Forum. “No problem, this sort of thing must be common, we’ll just buy a good one.” Hah! Fat chance! I simply could not find a commercially available solution with the required features. I decided to go open-source. I knew that I would not find an ideal solution, but at least I could modify it as needed.
The clock I was looking for was to be the timekeeper for the day, counting down each event with a visual indicator showing that one-third of the time remained, and another to show in the last minute of each event. Three such clocks would be deployed, and these would be displayed on beautiful 40″ Samsung LED HD displays, each connected to a laptop, and synchonised. In addition to the countdown clock, each display would show an event (or timeslot) identifier.
The users, thankfully, were not geekish in any way and the application controls would need to be intuitive and the entire application would need to be contained in a single application file.
A web search returned a number of countdown clocks, but none that satisfied the criteria. Some that came close were web applications. And that got me thinking…
I have been dragging my feet a bit, and this would be the perfect excuse to properly get on the wagon. Imagine my delight when, at the very event for which I’d written the countdown clock — The Enterprise Mobility Forum, Cape Town 2012 — the consensus was that “the operating system is irrelevant” and “apart from highly technical power apps, all user apps will run in browsers”. I’d been punting this view since 2005 but, having lived through and wasted a great deal of effort with the largely toothless standards drives of the late eighties, I now knew better than to leap, and instead took the wait-and-see approach. At last!
A perfect match.
Next I’ll explain how I put the first version together. I hope to see you back soon.