Dates

HackRice 12 will officially kick off at 8:00 PM on Friday, September 22, 2022 and end at 9:00 AM on Sunday 24, 2022.

Eligibility

To be eligible for prizes, your submission must adhere to the following rules:

  • Your project must be created by team members entirely between the Friday kick-off and Sunday deadline
  • Your project must be created by a team with at most 4 members
  • External Resources: Participants may use external resources (online resources, reference books, help from mentors, etc.), but the material of the submission must be created by team members alone.
  • Third Party Libraries and APIs: Third party libraries and APIs are permitted if they publicly available and free to use
  • No code created before hacking starts can be used, and use of such code will lead to disqualification
  • Hackers may only submit a project for a single track, but if they do so they are still considered for general prizes and company challenges
  • Hackers' projects can win multiple challenges, but only one prize can be won between the general prizes and the tracks

Project and Submission Requirements

Prior to the Devpost submission deadline (Sunday 9/24, 9:00 am), submit a 3-4 minute video to Devpost. We have included a recommended outline for your video submission.

30 seconds Intro

Project name, members, track/challenge, project purpose, technologies used

 

2 minutes Demo

Let’s see your project in action!

 

30 seconds Technical design and implementation

High-level overview of how you designed your code

 

30 seconds Impact

The real-world value of your project; how you’d improve it in the future

Prizes

1st Prize

iPad Mini

2nd Prize

GoTrax electric scooter

3rd Prize

Xbox Series S

Activism Winner

Airpod Pro Gen 2

First Timer Winner

Fitbit versa 4

Safety & Security Winner

Ruko Drone

Rice Design Challenge

Free merch

Chevron Challenge

1st Place – Bose QuietComfort 45 Bluetooth Wireless Noise Canceling Headphones

 

2nd Place - $100 Amazon Gift Cards

Data Science Challenge

JBL Flip 6

Judging Criteria

  • Relevance

    • If the solution was submitted under a track, how well does its mission and impact fit within the track?

    • If the solution was not submitted under a track, how relevant is it to real-world issues? 

      • How current are these issues? 

  • Originality/Creativity

    • Is the solution something unique? 

      • Never before seen?

    • Does the solution utilize a common technology/tool in a creative way?

  • Practicality/Impact

    • Does the solution achieve its mission?

    • Does the solution function as intended?

    • Does the solution have an impact on intended stakeholders? 

      • How diverse is this set of stakeholders?

    • Does the solution have a long life-time?

      • Is the solution easy to maintain?

    • Is the solution scalable?

  • User experience/Design

    • Does the solution look aesthetically pleasing?

    • Is usage of the solution intuitive? Easy to interact with?

  • Technical Rigor

    • How advanced are the technologies used?

    • How well are technologies integrated with each other?

    • How diverse is the set of technologies used?

    • How extensively are technologies implemented into the solution?

      • Are technologies used to their full potential?