πŸ“… Hackathon Format & Timeline πŸ₯‡ Round 1 – Concept Screening (Online Submission)
  • Teams must submit a Project Concept PPT

  • Shortlisted teams will advance to Round 2

  • No working prototype required in Round 1

πŸ“Œ Submission deadline will be announced by organizers.

πŸ₯ˆ Round 2 – Offline Hackathon (2 March)

Hackathon Date: 3 March
All shortlisted teams will build and submit their projects during the official hackathon timeline announced on the event day.

Projects must be developed during the offline hackathon hours.

πŸ‘₯ Eligibility
  • Open to all registered participants of Geminathon.

  • Participants may compete individually or in teams (as per event guidelines).

  • All skill levels are welcome β€” beginners to advanced developers.

  • Only shortlisted teams from Round 1 may participate in Round 2.

  • Teams must adhere to the event code of conduct.

πŸ›  Round 1 – PPT Submission Requirements

Teams must submit:

πŸ“Š 1. Project Concept Presentation (PDF or PPT)

6–12 slides including:

  • Problem Statement

  • Proposed Web-Based Solution

  • Target Users

  • Core Features

  • How Gemini API Will Be Used (must be central)

  • High-Level Architecture (optional but recommended)

  • Expected Impact

⚠️ No working prototype required in Round 1.
⚠️ Evaluation is based on clarity, innovation, and feasibility.

πŸš€ Round 2 – Project Development Requirements

Shortlisted teams must:

πŸ”Ή Project Requirements
  • Build a web-based application

  • Meaningfully integrate the Gemini API as a core component

  • Develop the project during the hackathon period

  • Use any tech stack

  • Deliver a functional, demo-ready product

πŸ“¦ Round 2 – Final Submission Requirements

Each shortlisted team must submit:

1️⃣ Public GitHub Repository
  • Clear README with:

    • Project overview

    • Setup instructions

    • Explanation of how Gemini API is used

2️⃣ Live Deployment Link
  • Fully functional and accessible web app

3️⃣ Project Description (150–300 words)
  • The problem

  • Your solution

  • How Gemini powers the system

⚠️ API keys must NOT be exposed in public repositories.
⚠️ Pre-built projects are not allowed.

πŸ† Prizes

Prize money and rewards will be announced soon.

Final winners will be selected after Round 2 demos and evaluations.

πŸ§‘β€βš–οΈ Judging Criteria πŸ₯‡ Round 1 Evaluation Criteria
  • πŸ’‘ Clarity of Problem Statement

  • πŸš€ Innovation & Originality

  • 🧠 Meaningful Gemini Integration Plan

  • πŸ›  Technical Feasibility

  • 🌍 Real-World Impact Potential

πŸ₯ˆ Round 2 Evaluation Criteria
  • 🧠 Effective Use of Gemini API

  • πŸ›  Technical Implementation & Architecture

  • 🎨 UI/UX & User Experience

  • πŸš€ Innovation Depth

  • 🌍 Practical Relevance & Scalability

  • 🎀 Live Demo Performance

βš–οΈ General Rules
  • All development must occur during the official hackathon timeline (Round 2).

  • Use of third-party libraries is allowed.

  • Use of pre-trained models is allowed.

  • Plagiarism or submission of pre-built projects will lead to disqualification.

  • Judges’ decisions will be final.

🎯 Strategic Implication of These Rules

This structure:

  • Filters serious teams early

  • Encourages well-thought-out AI integration

  • Prevents last-minute shallow Gemini add-ons

  • Ensures Round 2 has high-quality builds

  • Raises the overall competition standard