App MVP Rules

This rubric will be used to evaluate projects submitted to the hackathon. Judges will score each project across several categories, and the total score will determine the winners.

Scoring

Each category will be scored on a scale of 1 to 5:

  • 1 - Needs Improvement: Significant issues or minimal effort demonstrated.
  • 2 - Below Expectations: Does not fully meet the criteria.
  • 3 - Meets Expectations: Satisfies the basic requirements of the category.
  • 4 - Above Expectations: Demonstrates a strong understanding and execution of the criteria.
  • 5 - Exceptional: Outstanding work that significantly exceeds expectations.

Categories and Descriptions

1. Innovation & Originality

  • Description: How unique or novel is the idea? Does it offer a new solution or approach to a problem? Is there evidence of creative thinking?
  • Criteria:
    • Novelty of the concept.
    • Creativity of the implementation.
    • Potential to disrupt or significantly improve upon existing solutions.

2. Technical Execution

  • Description: How well was the project built? Is the code clean, well-organized, and functional? Does the project demonstrate technical proficiency and the use of appropriate technologies?
  • Criteria:
    • Functionality and stability of the application.
    • Appropriate use of technologies and tools.
    • Demonstration of technical skills.

3. User Experience (UX) & Design

  • Description: How easy and intuitive is the project to use? Is the interface visually appealing and well-designed? Does the project consider the user’s needs and create a positive interaction?
  • Criteria:
    • Ease of use and navigation.
    • Visual design and aesthetics.
    • Overall user satisfaction and engagement.
    • Accessibility considerations (if applicable).

4. Impact & Feasibility

  • Description: How significant is the potential impact of the project? Does it address a real problem? Is the app creative, playful or delightful?

  • Criteria:

    • Potential to solve a meaningful problem or delight the user.
    • Size and relevance of the target audience.
    • Potential for future development and scalability.

5. Presentation & Communication

  • Description: How effectively was the project presented? Was the problem, solution, and impact clearly articulated? Was the demonstration engaging and easy to understand?
  • Criteria:
    • Clarity and conciseness of the presentation.
    • Ability to answer questions confidently and knowledgeably.
    • Overall enthusiasm and passion for the project.

6. Team work

Short-form hackathon terms

The following terms apply to participation in this hackathon, Google I/O Extended Hackathon: Web, Mobile, Gaming and AI Focus (“Hackathon”). Entrants may create original solutions, prototypes, datasets, scripts, or other content, materials, discoveries or inventions (a “Submission”). The Hackathon is organized by GDG Central Florida in cooperation with GDG Ocala, GDG Tampa Bay, GDG Space Coast, GDG Cloud Boston, and GDG Miami.

Entrants retain ownership of all intellectual and industrial property rights (including moral rights) in and to Submissions. As a condition of submission, Entrant grants the Hackathon Organizer, its subsidiaries, agents and partner companies, a perpetual, irrevocable, worldwide, royalty-free, and non-exclusive license to use, reproduce, adapt, modify, publish, distribute, publicly perform, create a derivative work from, and publicly display the Submission. Entrants provide Submissions on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. Feel free to review longer form “guidelines and terms” at the end of this document.