Jump to a question:
To learn android development.
Experiencing frustration for the time it takes for clubs to share results after an evening time trial. It can be days later, by then interest in the results has faded.
Experiencing the faf of volunteering to time a time trial with stopwatches, notepads and calculators in the digital age.
No, android only i'm afraid. I have no current plans to develop an iPhone version but could be interested if someone wanted to contribute.
It can handle timing 1000 comfortably, however the results screen will struggle to display this many. This is an area I intend to optimize. Up to 300 should be OK for everything with some lag generating the screenshot of results.
No it is not. I originally started developing this to learn android and feel i should tidy up some code first. I definitely plan to open it at some point though. If you are interested and want to look or even contribute i would be very happy to discuss.
Coded in Kotlin using AndroidX architecture components. SQLight Database with Room, LiveData and Kotlin Coroutines, Dagger 2 for dependency injection, Material Design components for UI. Special thanks to:
Haruki Hasegawa for the awesome Advanced RecyclerView
Jake Wharton for Android Three Ten APB Backport and Timber