-
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.
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.
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
Each shortlisted team must submit:
1οΈβ£ Public GitHub Repository-
Clear README with:
-
Project overview
-
Setup instructions
-
Explanation of how Gemini API is used
-
-
Fully functional and accessible web app
-
The problem
-
Your solution
-
How Gemini powers the system
β οΈ API keys must NOT be exposed in public repositories.
β οΈ Pre-built projects are not allowed.
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
-
π§ Effective Use of Gemini API
-
π Technical Implementation & Architecture
-
π¨ UI/UX & User Experience
-
π Innovation Depth
-
π Practical Relevance & Scalability
-
π€ Live Demo Performance
-
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.
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