Dates

Starts: Wednesday April 23, 6:30 pm
Deadline: April 29 at 11 am

Project and Submission Requirements

All SWECCathon projects must meet the following requirements:

  1. Original Work: All submitted projects must be original work created during the hackathon period (April 23-29, 2025). You may plan and brainstorm before the event, but all code and assets must be created during the official hackathon period.
  2. Team Size: Teams may consist of 1-4 members. All team members must be registered for the hackathon.
  3. Technology: You may use any programming languages, frameworks, libraries, or APIs. Open-source resources and pre-existing frameworks are permitted, but the core functionality and implementation must be your original work.
  4. Code Repository: All code must be hosted in a public repository (GitHub, GitLab, etc.) with clear documentation.

To be considered for judging, your submission must include:

  1. Complete Devpost Submission: Fill out all required fields in the Devpost submission form.
  2. Project Description: A clear description of your project, including:
    • The problem you're solving
    • Your solution approach
    • Technologies used
    • Challenges faced
    • Future improvements
  3. Demo Video: A 2-4 minute video demonstrating your project in action and explaining key features.
  4. Source Code: Link to your public code repository if applicable.
  5. Screenshots: Images showcasing different aspects of your project.
  6. Working Demo: If applicable, provide a link to a working demo or installation instructions.
  7. Track Selection: Indicate which track(s) you're submitting to, if any.

Prizes

Prizes will be awarded to the top teams across several categories!
More details announced during the event.

Judging Criteria and Winner Selection

Each project will be evaluated on the following:

  1. Innovation & Creativity – Is the idea original or cleverly reimagined?
  2. Technical Difficulty – Did the team tackle technical challenges thoughtfully?
  3. User Experience & Design – Is it intuitive and well-designed?
  4. Impact – Does the project solve a meaningful problem?
  5. Presentation & Completeness – Is the submission polished and easy to understand?