The Africa Hack

Dates and Timings

Hackathon Begins: Monday 3d Feb (10:00AM WAT)

In-Person Hack Space begins: Friday 7th Feb (10:00AM WAT)

Submission Period: Friday 7th Feb - Sunday 9th Feb ("Submission Period").

Judging Period: Sunday 9th Feb (4:00 PM  WAT) - Sunday 9th Feb (6:30 PM WAT)

Winners Announced:  On or around Sunday 9th Feb (7:00PM WAT)

Eligibility

• Individuals who are at least the age of majority where they reside as of the time of entry (“Eligible Individuals”);
• Teams of Eligible Individuals (“Teams”); and
• Organisations (including corporations, not-for-profit corporations and other nonprofit organizations, limited liability companies, partnerships, and other legal entities) that exist and have been organized or incorporated at the time of entry. (the above are collectively, “Entrants”) An Eligible Individual may join more than one Team or Organization and an Eligible Individual who is part of a Team or Organization may also enter the Hackathon on an individual basis. If a Team or Organization is entering the Hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. By entering a Submission on behalf of a Team or Organization you represent and warrant that you are the Representative authorized to act on behalf of your Team or Organization.

Hackathon Requirements

Entrants may enter by visiting https://the-africa-hack.devpost.com/rules (“Hackathon Website”) and following the below steps:

• Register for the Hackathon on the Hackathon Website by clicking the “Join Hackathon” button. To complete registration, sign up to create a free Devpost account, or log in with an existing Devpost account. This will enable you to receive important updates and to create your Submission.
• Registration of in-person access is required. In Person Hackathon Sign Up Here

Project Requirements

What to Create: Entrants must create or update a working software application and/or UI/UX design according to the non-technical tracks.

• Functionality: The Project must be capable of being successfully installed and running consistently on the platform for which it is intended and must function as depicted in the video and/or expressed in the text description.
• Platforms: A submitted Project must run on the platform for which it is intended and which is specified in the Submission Requirements.
• New only: Projects must be newly created by the Entrant
• Third-Party Integrations: If a Project integrates any third-party SDK, APIs and/or data, Entrant must be authorized to use them in accordance with any terms and conditions or licensing requirements of the tool.

Submission Requirements

• Include a Project built with the required developer tools that meets the above Project Requirements.
• Identify which track or Sponsor Prizes your Project is being submitted for (optional).
• Include a text description/deck that should explain the features and functionality of your Project.
• Include a URL to your code repository. Provide access by making it public.
• Include links from the relevant explorer to your contracts. Contracts must be verified and publicly readable.
• Include a demonstration video of your Project. The video portion of the Submission:
  • should be less than three (3) minutes. Judges are not required to watch beyond three minutes
  • should include footage that shows the Project functioning on the device for which it was built
  • must be uploaded to and made publicly visible on YouTube or Vimeo and a link to the video must be provided on the Submission form on the Hackathon Website
  • must not include third party trademarks, or copyrighted music or other material unless the Entrant has permission to use such material.

Prizes

Flow Gaming Track

Judging Criteria and Winner Selection

Eligible Submissions will be evaluated by a panel of judges selected by the Sponsor (the “Judges”). Judges may be employees of the Sponsor or third parties, may or may not be listed individually on the Hackathon Website, and may change before or during the Judging Period. Judging may take place in one or more rounds with one or more panels of Judges, at the discretion of the Sponsor.

Stage One) The first stage will determine via pass/fail whether the ideas meet a baseline level of viability, in that the Project reasonably fits the theme and reasonably applies the required APIs/SDKs featured in the Hackathon.

Stage Two) All Submissions that pass Stage One will be evaluated in Stage Two based on the following equally weighted criteria (the “Judging Criteria”): Entries will be judged on the following equally weighted criteria, and according to the sole and absolute discretion of the judges:

• Technological Implementation Does the project demonstrate quality software development? How is the quality of the code?
• Design Is the user experience and design of the project well thought out? Is there a balanced blend of frontend and backend in the software?
• Potential Impact How big of an impact could the project have on the target community? How big of an impact could it have beyond the target community?
• Quality of the Idea How creative and unique is the project? Does the concept exist already? If so, how much does the project improve on it?

The scores from the Judges will determine the potential winners of the applicable prizes. The Entrant(s) that are eligible for a Prize, and whose Submissions earn the highest overall scores based on the applicable Judging Criteria, will become potential winners of that Prize. Tie Breaking For each Prize listed below, if two or more Submissions are tied, the tied Submission with the highest score in the first applicable criterion listed above will be considered the higher scoring Submission. In the event any ties remain, this process will be repeated, as needed, by comparing the tied Submissions’ scores on the next applicable criterion. If two or more Submissions are tied on all applicable criteria, the panel of Judges will vote on the tied Submissions.