Note
25-manna check-in. They used bar code reader to get number from bib number and SI unit to get card number. Then we had to wait 20 sec, apparenty the app connected to a (remote?) database and inserted data there. Makes me wonder was/is the whole system based on that approach, central database server and clients connecting there storing data there. And when something is wrong, server, database, network, power etc, one can't do anything but wait for system to become up and functional again.
I'd say there is room for improvements there, one can't expect all systems are up and running all the time and that there would be no hardware failures.
As a comparison, system used for Jukola is based on sort of separate standalone apps. You read barcode and card number and data gets stored to local file/database. You can immediately take next runner without having to wait for anything. A background process syncs data with other computers. If network is down you can still keep on checking in runners in and when network is back data gets synced. Same with every app and feature, download, printing, the wailing wall, commentators apps etc. There is no central server every app depends on, even if half of the computers burns and network is down the rest of the stations would still operate. And they also test it before the event by taking computers down, shutting down routers and unpluging network and power cables to make sure everything still works and data gets synced when network and power is back.
Thinking of 25-manna entry incomes one would think there is enough resources to get that done a bit better. Simple and obvious things mostly, no innovations or rocket science needed. Just saying.