Problem Statement

DevSoc projects are designed to meet the unique needs of UNSW students, leveraging technology to enhance their university experience. Our mission is to identify gaps in student life that can be streamlined or improved through innovative technological solutions. 

Your Task: Create a game OR gamify some mechanism to improve the health or productivity of students. You may choose to leverage DevSoc’s Flagship Projects as a point of inspiration. Our projects are available here: https://devsoc.app/our-projects. ;

DevSoc has created an API that contains UNSW data that our current projects use including room bookings, classes and courses. The documentation is available here: https://github.com/devsoc-unsw/graphql-api?tab=readme-ov-file.

Requirements

WHAT TO BUILD
Whatever you'd like, as long as it addresses the problem statement! There is no restriction on what form your project should be like and what technologies are used to build it. See the rules for a more detailed breakdown. 

WHAT TO SUBMIT
Your code on a public repository, screenshots of your project and a brief description of what it does on the DevPost.

A 3 minute pitch video describing your project and how it addresses the problem statement.

Hackathon Sponsors

Prizes

$370 in prizes
First Place
$150 in cash
1 winner

Runner Up
$100 in cash
1 winner

People’s Choice Award
$60 in cash
1 winner

Most Creative Project Award
$60 in cash
1 winner

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

Devsoc Events

Devsoc Events

Judging Criteria

  • Innovation and Creativity (25%)
    Originality: Is the idea novel and unique? Has it been done before? Creativity: Does the solution approach the problem in an innovative way? Impact: Does the project have the potential to make a significant impact or change?
  • Technical Complexity and Completeness (20%)
    Error Handling:Are there bugs? Are edge cases considered? Implementation:How well is the technology implemented? Functionality:Does the project function as intended? Are all features implemented properly? Is it responsive?
  • User Experience and Design (20%)
    Usability: Is the project easy to use and navigate? Is the user interface intuitive? Aesthetics: How visually appealing is the design? Is the design cohesive and professional? Accessibility: Is the project accessible to users of varying abilities?
  • Practicality and Feasibility (15%)
    Feasibility:Can the project be realistically implemented? Are the resources required available? Scalability:Can the solution be scaled up? Does it handle increasing amounts of work well?
  • Presentation and Pitch (10%)
    Clarity: Is the presentation clear and concise? Does it effectively communicate the project? Engagement: Does the pitch video engage the audience and judges? Q&A: How well does the team respond to questions?
  • Team Collaboration (10%)
    Teamwork: How well did the team work together? Did they utilise each member's strengths? Contribution: Did all team members contribute significantly to the project? Communication: How effectively did the team communicate during the hackathon?

Questions? Email the hackathon manager

Tell your friends

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.