What to Build

Working prototypes are required for submission. Start by identifying and building your core, critical technology that makes your idea special. Follow this by building out the overall experience, demonstrating how a user might use the product. Think also about how this idea could be scalable past just a hackathon, and how it would work as a business.

What to Submit on Devpost

On Devpost, here are some suggestions for what to submit:

• Problem that you are trying to solve and its significance
• Inspiration for solution
• How the solution is special / novel / unique
• How the product is meant to be used
• The technologies or techniques used
• Key challenges
• The product as a business and/or at scale

You are also recommended to include photos, videos, animations where appropriate. If possible, a link to a demo is also recommended!

Judging Exhibition

The judging will be carried out via an exhibition that will take place on day 2. Each team will be given a table to setup a booth on, and the judges will come to your booth. The presentation format is entirely up to you. Engage the judge!

• Problem Understanding (20%)
  How clearly is the problem defined? Does the team demonstrate a deep understanding of the problem's context, stakeholders, and pain points? Did they select a meaningful and relevant problem to solve?
• Innovation & Creativity (20%)
  Is the solution novel or does it apply existing ideas in a clever way? Does it offer a unique approach compared to existing solutions? How creatively did the team address the constraints of the problem?
• Technical Execution (20%)
  Is the solution technically sound? Does it work as intended? How complete or functional is the prototype or MVP? How well is the code or system architected (if applicable)?
• Impact & Relevance (15%)
  How much potential does the solution have to make a real-world impact? Is the solution scalable or applicable to a broader audience or domain? Does it address root causes rather than symptoms?
• User Experience & Design (10%)
  Is the solution easy and intuitive to use? Is the interface clean and user-friendly? Has the team considered the needs of end-users?
• Feasibility & Viability (10%)
  Can the solution be realistically implemented? Are resources, cost, and logistics reasonably accounted for? Is there a sustainable plan for execution?
• Presentation & Communication (5%)
  Was the idea presented clearly and convincingly? Did the team effectively communicate their thought process, solution, and impact? Did they answer questions from judges well?