About this event
A welcome note
Welcome to CoDE-2017 Summit Online Hackathon! In the 21st century, new technologies give us better tools to improve our society. Our society is changing and along with there are exciting developments in Computer Science and UX Design - yet some population might not be able to fully enjoy the improvements.The CoDE hackathon will focus on breaking down current barriers that the Society faces and how can we positively use technology to make everyone enjoy its benefits.
This online hackathon will challenge you to step out of your comfort zone, leave preconceived notions behind, then build and pitch a product/service that uses technology in order to make our society more integrated.
Register for Online Hackathon by filling in the form below:
Email email@example.com with any questions or concerns.
Schedule for the day is not published
Schedule for the day is not published
Teams Teams can be anywhere from two to five members. All members must be a builder (a Developer or Designer). To qualify for a team member, you should be residing in one of the countries of So...
Teams can be anywhere from two to five members. All members must be a builder (a Developer or Designer). To qualify for a team member, you should be residing in one of the countries of Southeast Asia or China. A team leader should be assigned. This team leader should be the contact point for communications. The working prototype should be only Software based - should be able to work on at least one of these: Smartphones / Computers / Tablets.
You need to submit two items before the deadline. a video about the submission a working prototype names of Technologies and Tools used to create the working prototype
All materials submitted in connection with the Hackathon must be in English or, if not in English, the Maker must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted. Video:
The video portion of the submission should include:
What problem does it solve Demonstration of working prototype - functionality and benefit How would you plan to scale it in real life
This video: a. Duration should not exceed six (6) minutes; b. must include footage that clearly explains the Application’s features and functionality c. must not be uploaded to YouTube, Vimeo, or Youku before submission; d. must not include third party trademarks or copyrighted music or other material unless the Maker has permission to use such material.
Code, Design, SFX, Music, etc To ensure a level field for all contestants, all code, design, art, music, SFX, and assets must be created during the duration of the Hackathon. We want to ensure that all participants start off on the same footing and we also want to preserve the true spirit of a hackathon. You are, however, free to make plans, create wireframes, and brainstorm prior to the announcement of topic.
The only exception to this rule would include material that is freely available to the public. Some examples of this would be: public domain images, creative commons music, open source libraries. We take this rule very seriously for the sake of all members attending the event. Failure to comply may result in the offending team's disqualification.
APIs, Services, and Open Source (optional)
The exception to the above rule is that you are encouraged to use 3rd party services, open APIs, open source projects, libraries, and frameworks.
There are three categories for participation: Drone (for Professionals), Spaceship (for tertiary students) and, Open categories (for non-professional or non-tertiary students)
Teams will be judged on these four criteria. Judges will weigh the criteria equally.
Potential Impact: The extent to which the app can impact individuals, businesses, or communities. Does your prototype help solve a problem or pain point for your users?
Quality of the Idea: Creativity, novelty, and originality of the product. Does your product proposal solve your users' problems in a unique way?
Design: Did the team put thought into the user experience (user-friendly, ease-of-use)? How aesthetically pleasing is the interface?
Function: Does the hack/solution work? Did the team achieve they wanted?