Blarsen,
This is along the lines of what I was thinking...I was really wondering if you had thoughts about apps for wearables...specifically those l that integrate with a smart phone.
My thinking is that a "legit" official's watch runs anywhere from $100-$300 bucks. If one could build an app with sport-specific timing features, and make it available on hardware/OS platforms that are in the mainstream marketplace, would it be able to find some level of adoption?
This is mostly what I meant by "hardware platform" I haven't yet found a smartwatch that I feel would be a good choice. I would think you need:
at least a few physical buttons for actions that need to be performed by feel alone (starting/stopping play or game clock)
A touchscreen for more complex input (scores, fouls, timeouts, etc.)
an e-ink screen screen (both for battery life and for visibility in high light situations)
A replaceable battery (so you can carry spares)
You could somehow include integration with existing equipment (FB play clock/ BB shot clocks, Ready-Ref etc.) or the Precision Timing System being used in the NCAA tourney this year, (see link below).
I suspect this would require a lot of reverse engineering and customization for each installation. It would be really nice, but realistically it won't happen in the near future. It would be much easier to give the eco a device like the one the officials use then ask him/her to make the scoreboard match. We don't allow play clocks here in California, so I'm not familiar enough with their operation to determine how easily they could be integrated.
I guess my question is more along the lines of: would officials be interested in buying an app for a phone or wearable that they already own as opposed to buying a watch/timer for a specific sport?
One concern around this model is that these devices are new enough that there is no standard interface that can be used to control them all. This means that any application would need to be written explicitly for each and every model of wearable that is supported. Worse yet it must be rewritten for each combination of wearable and phone, and in a different language for each phone, so most of the code cannot be re-used
The comments about using electronics in poor weather conditions are certainly valid concerns, and I think that is why I am leaning towards wearable tech that is designed to be worn under those conditions moreso than a smart phone.
This is one of the reasons I'm thinking of a smaller kindle. I frequently use my kindle for recipes and I just drop it in a ziploc bag: it is totally waterproof, the plastic is thin enough that the capacitive touchscreen still works, and it doesn't generate enough heat to require ventilation. Add to that the fact that my battery last for weeks (admittedly I don't use it 24/7, but still...) between charges with the radio on and months with the radio off.
Plus it's actually possible for me to prototype a hardware platform at this scale. I don't have access to the equipment necessary to prototype and test something as small as a watch.
Precision Timing System link (couldnt find a link for the one in the recent Referee Magazine):
http://www.nytimes.com/2015/03/20/sports/ncaabasketball/shrill-to-ncaa-tournament-referees-its-symphonic.html?_r=0
Thoughts?