Team Projects

Project Development

  • No development may start before the actual date and time of the event. Any teams that violate this rule will be automatically disqualified. The first line of code should be written on or after Thursday, January 16, 2021, at 8 pm after the team has registered. However, we encourage you to brainstorm ideas and create wireframes/mockups.
  • Any software development tools, IDE, and/or programming language can be used for the event. If a team member uses a purchased tool licensed to him or her and the license is not transferable to other members, the member’s team must choose one available to all developer teams.
  • To ensure a level field for all contestants, all code must be created only during the hackathon. You are permitted to use publicly developed and openly licensed API’s and SDKs for your project.
  • You will only be able to use a pre-public release of a product in developing your project if you bring at least one extra version that can be used by other teams in the Hackathon and provide any user support needed to teams using the device.
  • Project design/assets can be created prior to the start date of the hackathon. All assets should conform to the Creative Commons License agreement standard or are freely available and you have permission or license to use them. Proof of permission must be given upon request.
  • Assets, SDKs, APIs or other tools or components available under a trial license may be used.
  • A team can submit only one entry for the hackathon. Participation at the hackathon is subjected on a “per-team” basis meaning you are not allowed to be on more than one team at the event.
  • Any intellectual property developed during and within the scope of the hackathon must be open source and licensed under one of the licenses referenced in https://opensource.org/licenses.
  • The license selected by the team must be clearly listed in code (page per page) or a generic page announcing the license the application adheres to. The public code used inside your application should also list the licenses the code is subjected to.
  • A team can use multiple licenses in the application. For example, the public code used could be licensed under the Apache license agreement whereas the code written by the team for the application licensed under the MIT license agreement.
  • A team may not code applications that violate the code of conduct. For example, racially insensitive ideas for an application will automatically be disqualified.

Project Requirements

  • Participants must use BlinkSky APIs to build software applications that involve digital payments.  The Hackathon team will supply entrants sandbox accounts to BlinkSky’s API.
  • Applications should be either web or mobile based.
  • Participants must be able to allow the Hackathon judges to use and test their team applications and provide instructions on how to use the application.
  • All applications and descriptions of the applications must be in English.
  • Each Hackathon team should designate a team lead or representative who enters the submission for the team.

Project Submission

  • All teams should have a team name and be registered with Devpost.
  • Each team should designate a team representative who submits the team’s submission.
  • The Devpost team page listing should have the following:
    • The Devpost team page listing should have the following:
    • The team lead must list a mobile phone number on the teams DevPost page (after judging is complete the number may be removed)
    • All team members will be listed with brief biographies.
    • Short abstract of the project
    • The hackathon theme (See https://realityvirtuallyhack.com/about/) and category if applicable
    • The development tools used to build the project
    • SDKs used in the project
    • APIs used in the project
    • Any assets used in the project
    • Any libraries used in the project
    • Any components not created at the hackathon
    • A link to a video of a screen capture of the application on Youtube.
  • All projects should be submitted to publicly visible code repository with a README explaining the project before judging begins on Saturday August 1, 2021 at 1:00 pm EDT.
  • When development ends at least one member from each team will meet with the judging team for a brief review of their submission and to confirm that the team’s Devpost page has been correctly updated.

Intellectual Property

  • All eligible Submissions remain the intellectual property of the individuals that submitted them. By entering the Hackathon, the entrants agree that the sponsors will have a perpetual, non-exclusive, fully paid license to use the entry for judging the entry.
  • Entrants agree that the Sponsors will have full rights to promote Submissions and use the name, likeness and images of all teams and associated individuals contributing to Submissions.
  • Entrants agree that Submissions and their content are not copyrighted or bound by other 3rd party agreements, intellectual property rights or any other rights unless those rights are held by the entrants.
  • Entrants agree that intellectual property rights of the Sponsors remain with the Sponsors.

Judging Criteria

  • Innovation
    We will look at innovations presented by the application and its associated presentation. Entries should show new ways to send digital payments using the APIs in the BlinkSky platform
  • UI/UX Design
    We will look at the solution and judge its look, feel and overall design. Designs should show how they make digital payments desirable and even fun.
  • Business Potential
    How will your solution attract users with the goal to generate new business?
  • Impact
    How will your solution improve people’s lives, in economic terms, in satisfaction terms and in overall terms?

BlinkSky

BlinkSky, Inc. 2021.  All rights reserved.