-
The hackathon is open to developers, designers, students, and independent creators who meet the eligibility requirements published on the event's Devpost page.
-
This is a strictly solo hackathon. Each participant must develop and submit their project individually.
-
Teams and collaborative project submissions are not permitted.
-
Each participant may submit one project under one theme.
-
Participants must register and submit their projects through the official Devpost hackathon page.
-
Participation must comply with applicable laws, Devpost's Terms of Service, and these rules.
Participants must choose one of the following seven themes:
-
Tech for a Fictional Island
-
The Reverse Hackathon
-
Grandma-Proof
-
Alien Onboarding
-
Ghost Town Rescue
-
City as a Game
-
Smallest Possible Product (SPP)
Projects must meaningfully address the selected theme's scenario, constraints, and requirements.
Participants have creative freedom in how they interpret the challenge. No particular application type, framework, or programming language is required.
Projects that do not demonstrate a clear connection to their selected theme may be considered ineligible.
3. Project Development-
Substantial development of the submitted project must occur during the official hackathon period.
-
Participants may use existing open-source libraries, frameworks, development tools, and publicly available resources.
-
Previously developed personal projects may serve as a foundation, but the work submitted for judging must demonstrate substantial new development during the hackathon.
-
Participants must clearly disclose significant pre-existing components.
-
Projects must include a functioning implementation of their core concept.
-
Purely conceptual submissions, static mockups, or slide presentations without working functionality are not eligible.
Special Exception: Participants in the Ghost Town Rescue theme must begin with the legacy repository provided by the organizers. Their work will be evaluated based on the repairs, improvements, and recovery achieved during the event.
4. AI Tools and External ResourcesAI-assisted development is permitted.
Participants may use AI coding assistants, generative AI tools, APIs, third-party libraries, and other development resources.
However:
-
Participants remain responsible for understanding, integrating, testing, and explaining their submissions.
-
AI-generated code and other third-party resources must comply with applicable licenses and usage rights.
-
Participants must disclose significant use of AI tools and external resources in their project description.
-
Submitting another person's completed project as your own is prohibited.
-
AI-generated output alone, without meaningful participant implementation or integration, is insufficient.
AI is a tool, not a substitute for demonstrating your own work.
5. Submission RequirementsAll projects must be submitted through Devpost before the official deadline.
Each submission must include:
-
A project name and description.
-
The selected hackathon theme.
-
An explanation of the problem, approach, and technical implementation.
-
A link to an accessible source code repository with setup instructions.
-
A 2–5 minute demonstration video showing the project functioning.
-
Evidence of compliance with any additional theme-specific requirements.
-
Acknowledgment of significant third-party resources and AI tools used.
A live demonstration link is encouraged but not mandatory.
Participants are responsible for ensuring that submitted links remain accessible during the judging period.
Incomplete or inaccessible submissions may be excluded from judging.
6. Theme-Specific RulesIn addition to the general requirements, participants must satisfy their selected theme's constraints.
Tech for a Fictional Island: Incorporate at least two of the fictional nation's unique constraints into the solution.
The Reverse Hackathon: Demonstrate at least three intentionally violated UX principles. The application must remain functional, and deliberately frustrating interactions must not cause actual harm.
Grandma-Proof: Conduct usability testing with at least one real older adult and document feedback and subsequent improvements.
Alien Onboarding: Create an interactive learning experience that introduces a concept without relying on assumed background knowledge.
Ghost Town Rescue: Work from the organizer-provided repository, document defects, and demonstrate functional repairs and verification.
City as a Game: Establish meaningful interaction between a real-world physical environment and a digital experience.
Smallest Possible Product: Build exactly one primary feature on one screen. Additional unrelated features or interfaces violate the theme's constraints.
7. Originality and Intellectual Property-
Submissions must represent the participant's own original contribution.
-
Plagiarism, unauthorized copying, and misrepresentation of ownership are prohibited.
-
Participants must have appropriate rights or permissions to use third-party code, images, datasets, and other resources.
-
Participants retain ownership of the original intellectual property they create, subject to any third-party licenses or rights.
-
Organizers do not claim ownership of participants' projects.
By entering, participants permit the organizers to display and reference their submitted project names, descriptions, screenshots, and demonstration materials for hackathon judging, announcements, and event promotion, subject to applicable law.
8. Fair Play and ConductAll participants are expected to demonstrate honesty, professionalism, and respect.
The following are prohibited:
-
Plagiarism or presenting someone else's work as your own.
-
Undisclosed collaboration on a solo submission.
-
Deliberately misrepresenting functionality, results, or development contributions.
-
Harassment, discrimination, threats, or abusive behavior.
-
Attempts to manipulate judging or interfere with other participants.
-
Unauthorized access to systems, accounts, or data.
-
Projects that intentionally cause harm, compromise privacy, or violate applicable laws.
Participants must obtain appropriate consent when conducting user testing, collecting information, or recording other individuals.
9. Judging and EvaluationEligible submissions will be evaluated according to the judging criteria published on the hackathon's Devpost page.
Judges may consider originality, technical execution, functionality, adherence to the selected theme, and the quality of the submitted demonstration.
Different themes emphasize different skills. Judges should consider the particular objectives and constraints of each theme rather than rewarding technical complexity alone.
Judging decisions will be made according to the published criteria and applicable official rules.
10. Deadlines and Disqualification-
All submissions must be finalized before the deadline displayed on the official Devpost page.
-
Participants are responsible for submitting their projects on time.
-
Late submissions will not be accepted unless an official extension is announced.
-
Organizers may disqualify submissions that violate the published rules or eligibility requirements.
-
Any disqualification decision must be based on consistently applied rules and documented grounds.
We are committed to providing a welcoming, inclusive, and respectful environment for all participants.
Harassment, discrimination, intimidation, bullying, and abusive conduct will not be tolerated, whether during in-person activities or through online event channels.
Participants must respect others' identities, backgrounds, experience levels, and intellectual property.
Concerns about misconduct should be reported privately through the official organizer contact channel.
Organizers may take proportionate action, including warnings, removal from event activities, or disqualification, in response to violations.
12. Organizer CommunicationsOfficial announcements, clarifications, and event updates will be communicated through the hackathon's Devpost page or designated organizer channels.
Participants are responsible for reviewing these communications.
Organizers will aim to apply the published rules consistently and avoid changes that unfairly disadvantage participants.
Any necessary amendments will be communicated to registered participants.
By submitting a project, participants acknowledge that they have read and agree to follow the published hackathon rules.
Build independently. Compete fairly. Respect others.