Rules & Regulations

You must treat all team members, competitors, judges, coaches, volunteers, etc., with respect and courtesy.

The team size can be 2-4 people.

The final prize money is to be shared between all team members.

Teams should be made up exclusively of students or people who are not organizers, volunteers, judges, sponsors, or any other privileged position at the event.

All team members should be present at the event. Leaving the venue for some time to hack elsewhere is fine.

Teams can, of course, gain advice and support from organizers, volunteers, sponsors, and others.

Most of the work on a project should be done during the hackathon.

Teams can use an idea they had before the event.

Teams can work on ideas that have already been done. Hacks do not have to be “innovative.” If somebody wants to work on a common vision, they should be allowed to do so and be judged on their hack's quality.

Teams can use libraries, frameworks, or open-source code in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.

For designing User Interfaces, teams must use NativeBase as the sole third-party UI Component Library.

Teams must stop hacking once the time is up. Debugging and minor fixes are permitted post-deadline, but significant changes or feature additions are prohibited.

Teams can be disqualified at organizer discretion for rule violations, code of conduct breaches, or unsporting behavior.

We are strictly against plagiarism; any occurrence of such a case will result in the disqualification of the involved team.