WHAT IS GRYPHHACKS?
48 hours of programming, designing, networking, and learning! GryphHacks is the University of Guelph's official, student-run Hackathon! We welcome hackers of all skills and backgrounds from around the world, above the age of 14! This is a hybrid event!
From May 26-28, attend workshops and learn from industry professionals, amongst networking events, seminars, and mini-games with prizes & giveaways all throughout the weekend!
Join solo, or grab some friends to create a team of up to 4 people to submit your prototype that falls under one of our many categories! Applications are now officially closed, keep an eye on our socials for more information and sneak peaks of what's to come this amazing weekend at https://linktr.ee/gryphhacks!
|ACTIVITY||DATES AND TIME|
|Registration Opens||May 1st|
|Registration Closes||May 12th (Now May 19th!)|
|Opening Ceremony||May 26th @ 5:30PM|
|Hacking Starts||May 26th @ 5:30PM|
|Hacking Ends||May 28th @ 5:30PM|
|Public Voting Begins||May 28th @ 5:30PM|
|Judging Begins||May 28th @ 5:45PM|
|Judging Ends||May 28th @ 6:45PM|
|Public Voting Ends||May 28th @ 6:45PM|
|Closing Ceremony (Winners Announced)||May 28th @ 7:00PM|
**All times listed are in EST. This schedule is estimated and is subject to change.
Only participants who have registered through the application found on the GryphHacks website and have checked-in to the hackathon via the instructions specified in the main Discord server are permitted to submit their projects through Devpost. Any other submissions will not be judged.
This contest is open to any students or alumni, with any single team consisting of 1 to 4 individuals. Students must currently be attending either high school or university, as well as at least 14 years of age.
Cross-submissions of the same project to different hackathons running simultaneously as GryphHacks are not permitted and will result in immediate disqualification from GryphHacks.
All code written must be your own and written before project submissions end. External API or framework integrations are permitted. All code and supplementary materials MUST not have been designed ahead of the hackathon period. Please ensure your submission includes a link to your Github repo (must be public) and a complete devpost description.
It is REQUIRED to have a 1 - 3 minute video showcasing your project in your Devpost submission. This may be especially useful for the "People's Choice" category prize when other teams are checking out your project, as well as ensures that your project is properly showcased during judging.
Project submissions end Sunday, May 28th at 5:30 PM EST
$CAD850 in prizes
3D Printer with Removable Carborundum Glass Platform, and a Yeti Tumbler
Hoverboard with built-in speakers and 12km/h speed
Google Nest Mini + set of 2 Smart Bulbs
Best AI Hack
Decorative dulled Katana sword with sheath and mountable stand
Best UI/UX Hack
24oz Hydro Flask with thermal insulation
Best Themed Hack
HyperX CloudX Stinger 2 Core Gaming Headset
People's Choice Award
$50 Amazon gift card for each member of the winning team! Winners will be decided by the Devpost submission project with the most likes by the end of the Public Voting period in the above schedule.
Submitting to this hackathon could earn you:
Professor @ UofG
Professor @ UofG
Presentation & Design
Based off the devpost submission. How thorough and comprehensive is the project? Is the presentation/video easy to understand and highlights key features of the project? Does it have a neat and clean design? Is the UI/UX designed in an attractive way?
Does it answer a question? Does it solve a real-world problem? Is this an reimplementation of an existing solution or is it unique and original? Would others feel encouraged to use this?
Is it easy to manage/use for users? Is it easy to navigate, and fairly intuitive? Is the project functional? Does the project achieve the goals and accomplishments that were set out?
Is this project scalable and maintainable for the future? Is this a possible venture that can be expanded upon in the future? Does the project seem practical and viable? Does this fall under a reliable market that has long-term demand?
Is the project technically complex, considering the tools and technologies that were implemented? (Ex. What stack or frameworks they used). Does it seem remarkable that this was built over a weekend? How technically sophisticated was the solution?
Is the project accessible, and to what extent? Does it accurately implement measures to incorporate and improve accessibility in the project? Are there any accessibility features that target a specific demographic (Ex. Vision-Impaired, Hearing-Impaired)