# Overview
# The constraint-driven brief
# Game design and mechanics The organizers split participants into eight mixed teams and handed out different-colored bandanas. The game included:
- 70 challenges across easy, medium, and hard difficulty tiers.
- 16 location-based tasks tied to Vilnius landmarks.
- Photo or video submissions as proof of completion.
- No fixed route — teams chose how to spend their two hours.
- Tie-break rules based on team color order.
The prize for the winning team was a hot-air balloon ride over nearby Trakai lakes, which raised the stakes and encouraged diverse team planning.
# Why they built a custom web app Existing scavenger-hunt apps either cost too much for a one-off event or couldn't match the organizers' rules. With 42 people submitting multimedia proofs and only two reviewers to process them in real time, a shared doc or chat would have been unworkable.
Gediminas used Hostinger's product tools to build a web app tailored to the event. It included five main sections: Scoreboard, Submit, Gallery, Rules, and an Admin dashboard protected by a password for adjudicating submissions and managing the game.
# Preparation that reduced rework
Key engineering decisions addressed field realities: a timer designed to avoid phone-clock discrepancies, clear submission states, and a tie-break rule. These choices kept the admin workload manageable during the two-hour rush of submissions.
# The kickoff and immediate effects The event kicked off at Hostinger HQ in Vilnius. Teams spread across the city, choosing their routes and completing challenges to earn points. The app allowed teams to upload proof and check live standings while the two reviewers processed submissions through the admin dashboard.
# Practical takeaways for planners
- Use device-based identification to avoid login friction in short outdoor games.
- Predefine tie-breaks and edge-case flows so adjudicators don't make on-the-spot rules.
- If you build a custom tool, design a narrow feature set: scoreboard, submission intake, gallery, rules, and a compact admin view are often enough.