🛡️ Arraba Hack – Official Rules

Spirit of the Competition

Arraba Hack is more than a competition — it’s an opportunity to grow, collaborate, and have fun. Whether you’re here to win or just learn something new, keep the hacker spirit alive by helping others, staying curious, and building awesome things together.

General Rules

• All participants must follow our Code of Conduct.
• The hackathon is open to students and professionals. Organizers, mentors, and sponsors cannot compete.
• Teams should consist of active participants (we recommend 2–5 members).
• Work on projects should begin during the event. You may brainstorm ideas in advance, but no pre-written code is allowed.
• Reuse of open-source libraries or frameworks is encouraged — just no copy-paste of previous full projects.
• Once hacking ends, only bug fixes (not new features) are allowed before demos.
• Organizers reserve the right to disqualify any team for rule violations or unethical behavior.

Digital Submissions

• Submit a slides presentation showing what you built.
• Your code must be public and submitted via GitHub.
• The slides presentation must mention "Arraba Hack" clearly at the start.
• Projects must be new work — no reused codebases.
• All team members must be properly registered for the event.

Judging Criteria

• Innovation & Technical Depth: How impressive or challenging is the tech? Did you use creative techniques or advanced integrations?
• Design & User Experience: Is the solution intuitive, visually appealing, and user‑friendly?
• Completion & Functionality: Does your prototype function as intended? How complete is the MVP?
• Business Potential & Scalability: Is there a clear market fit and business model? Can the idea grow or scale sustainably?
• Pitch Quality & Communication: How effectively did you present the problem, solution, and value proposition?

While code quality isn’t scored directly, impactful solutions with clear growth potential and strong communication will stand out.