And to the question of why we have used Wifi P2P over Bluetooth. The only way to use bluetooth without pairing and manual authentification is insecure (using listenUsingInsecureRfcommWithServiceRecord() see link below) http://stackoverflow.com/questions/5885438/bluetooth-pairing-without-user-confirmation/5886544#5886544

Referring back to the question of the judges of the Q/A: The MAC address of the devices are hardcoded in order to provide a reliable solution on stage. During the 24-hours, we have explored the limitation of Wifi P2P and realized that the approach to make a fully scalable solution during the hackathon was not practical or reliable. Hence, we made a conscious decision to limit scalability in order to enhance reliability.

I don't think it'll work as a product, but it's cool offline p2p stuff, so I like that.

quick execution within 24 hours

As a technician, I am more curious to know how to ensure consistency more than the business.