
Patty Turner
The timekeeper function doesn't just register when you hit the stopwatch button but registers a click from anywhere on the bottom half of the screen. If you hold your phone by the edges (which everyone does), you run the risk of counting multiple fantom runners, especially when you're wearing mittens or gloves. It should give us a safe border on the edges of the screen. That would save a lot of time for the run director and the timekeeper when they have to clean up the results after a run.
3 people found this review helpful

A Google user
Very simple to use! I have just downloaded the app to my Samsung S10, and admittedly have only played with it (not used in real world), but seems incredibly straightforward. I like the fact it suggests flight mode is enabled- reduce the risk of interruption during timing. The scanner works in portrait or landscape and the barcode does not need to be perfectly aligned. I might just volunteer for timing roles now, rather than avoiding it!!
24 people found this review helpful

Chris Esterhuyse
It would appear with the Android version, that the scan area isn't zoomed/adjusted to the part of the screen that is being used, and the whole camera view is instead showing. This is what I believe is causing all the complaints. The scanner part itself isn't functioning correctly on Android - it's not about the individual cameras on each brand and model. Fix the scanner part of the app itself. ALSO, include some token support area. The ability to edit a field to add the position number if that doesn't want to scan, or manually add the A number and a position. For that matter, include incident reporting as well, it can be submitted to the webFMS the same way as the results.
14 people found this review helpful