πŸš€ Geminathon The Summit Arc Starts Now.

🌟 About the Challenge

Welcome to Geminathon β€” a two-stage innovation challenge where bold ideas rise to the summit.

This is not just about building with AI.
It’s about building intelligently, responsibly, and impactfully with Gemini at the core.

Participants will first pitch their idea.
The best ideas will earn the opportunity to build live.

πŸ₯‡ Round 1 – The Ascent (Concept Screening)

Before you build, you must think.

In Round 1, teams will submit a Project Concept Presentation outlining their proposed web-based application powered by the Gemini API.

🎯 Your Mission (Round 1)
  • 🧠 Clearly define a real problem

  • 🌐 Propose a web-based solution

  • πŸ”‘ Show how Gemini API will be central to the system

  • πŸš€ Demonstrate innovation and feasibility

⚠️ No working prototype is required in Round 1.

Only shortlisted teams will advance to the final build stage.

πŸ“Š Round 1 Submission Requirements

Submit a 6–12 slide PPT/PDF including:

  • Problem Statement

  • Target Users

  • Proposed Web-Based Solution

  • Core Features

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

  • High-Level Architecture (optional)

  • Expected Impact & Scalability

Judging will focus on clarity, originality, and meaningful Gemini integration.

πŸ₯ˆ Round 2 – The Summit (Offline Hackathon)

πŸ“… Hackathon Date: 3 March

Shortlisted teams will build their project during the official hackathon timeline announced on the event day.

This is where ideas become working systems.

πŸ›  Round 2 Project Requirements

Projects must:

  • βœ… Be a functional web-based application

  • βœ… Integrate Gemini API as a core intelligence layer

  • βœ… Be developed during the hackathon period

  • βœ… Be demo-ready by the end of the event

Any tech stack is allowed.

If Gemini is not central to your system, it’s not summit-ready.

πŸ“¦ Final Submission Requirements (Round 2)

Each shortlisted team must submit:

1️⃣ Public GitHub Repository

Must include:

  • Project overview

  • Setup instructions

  • Clear explanation of how Gemini API is used

⚠️ API keys must NOT be exposed.

2️⃣ Live Deployment Link
  • Fully functional

  • Publicly accessible

  • Demo-ready

3️⃣ Project Description (150–300 words)

Include:

  • The problem

  • Your solution

  • How Gemini powers the system

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

  • Individuals or teams (as per event guidelines)

  • All skill levels welcome

  • Only Round 1 shortlisted teams may compete in Round 2

  • All participants must follow the code of conduct

Requirements

πŸ” ROUND 1 – PPT Submission Template

(Gemini-Centric Web Application Proposal)

🟦 Slide 1 β€” Cover Slide

Project Title
Tagline (1 powerful line)

Team Name
Team Members
Hackathon Name
β€œPowered by Gemini API”

🟦 Slide 2 β€” Problem Statement The Problem

Clearly define:

  • Who is affected?

  • What is broken?

  • Why existing solutions are insufficient?

Use:

  • 3–4 crisp bullet points

  • 1 short real-world example

  • Optional stat (if available)

Keep it sharp and focused.

🟦 Slide 3 β€” Why This Problem Matters

Explain impact:

  • Economic impact

  • Social impact

  • Developer pain

  • Productivity loss

  • Risk or inefficiency

Make judges feel urgency.

🟦 Slide 4 β€” Proposed Solution Our Solution

Describe:

  • What you are building (web-based platform)

  • What it does

  • Who it is for

  • How it solves the core problem

Keep it high-level.
Do NOT reveal advanced architecture.

🟦 Slide 5 β€” How Gemini Powers the Core Gemini as the Intelligence Engine

Explain clearly:

  • What Gemini analyzes

  • What it reasons about

  • What it generates

  • Why traditional systems cannot do this

Example framing:

Gemini interprets complex data, generates contextual insights, and provides explainable recommendations in real time.

Make Gemini central, not decorative.

🟦 Slide 6 β€” Key Features

List 4–6 major features.

Example structure:

  • AI-driven insight generation

  • Context-aware recommendations

  • Natural language query interface

  • Explainable outputs

  • Smart summarization

  • Predictive intelligence

Keep it crisp.

🟦 Slide 7 β€” Web Application Architecture (High-Level Only)

Simple diagram:

Frontend
↓
Backend
↓
Gemini API
↓
Database / External APIs

Do NOT show:

  • Internal pipelines

  • Automation engines

  • Deep ML stack

  • Advanced reasoning layers

Just show that it’s buildable.

🟦 Slide 8 β€” User Journey

Step-by-step flow:

  1. User logs in

  2. User uploads / inputs data

  3. System processes input

  4. Gemini generates insights

  5. User receives actionable output

Make it visual and clean.

🟦 Slide 9 β€” Innovation & Differentiation

Explain:

  • What makes this different?

  • Why is Gemini essential?

  • Why is this scalable?

  • Why is this future-proof?

Use phrases like:

  • Explainable AI

  • Context-aware intelligence

  • Decision-support automation

  • Scalable AI infrastructure

🟦 Slide 10 β€” Scalability & Future Scope

Short section:

  • Multi-industry expansion

  • API integrations

  • Enterprise deployment

  • Real-time automation

  • Global scale potential

Keep it visionary but believable.

🟦 Slide 11 β€” Feasibility for Hackathon

Convince judges you can deliver.

Include:

  • Tech stack (React / Node / Python / etc.)

  • Deployment plan (Vercel / Render / Firebase)

  • Gemini integration approach

  • MVP scope clearly defined

Make them confident.

🟦 Slide 12 β€” Expected Impact

Quantify if possible:

  • Time saved

  • Cost reduced

  • Risk minimized

  • Decision speed improved

  • Productivity enhanced

Keep it strong and optimistic.

🟦 Slide 13 β€” Why We Should Be Selected

Short punch section:

  • Real-world relevance

  • Strong Gemini integration

  • Scalable architecture

  • Demo-ready plan

  • High innovation potential

Close confidently.

πŸ“ PPT Design Guidelines (Very Important)

Keep:

  • 12–14 slides max

  • Clean UI

  • Dark theme or minimal white theme

  • Consistent fonts

  • Minimal text per slide

Avoid:

  • Huge paragraphs

  • Overly technical diagrams

  • Overpromising impossible features

  • Revealing Round 2 surprises

🎯 Round 1 Strategy

Your goal is:

Not to prove you built it.
But to prove you can build it.

Round 1 judges evaluate:

  • Clarity

  • Relevance

  • Innovation

  • Gemini usage

  • Feasibility

Round 2 offline =
That’s where you shock them with full architecture, deeper automation, and polished demo.

Hackathon Sponsors

Prizes

1 non-cash prize
Grand Winner
1 winner

To be declared

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

chandrayee kumar
Expert UST global,Caltech Grad

Debrath Banerjee

Debrath Banerjee
Senior Software Engineer at Walmart

Jeewan Singh
Senior Business Analyst ,Omnicom Group

Sajal Baisakhiya
Senior Principal Architect

Vijay Guntumadugu
azure lead data engineer

rajkumar kuppuswami

rajkumar kuppuswami
manager data analayst

Judging Criteria

  • 1. Innovation & Creativity (25%)
    - Originality of the idea - Unique problem-solving approach - Creative application of the Gemini API - Distinctiveness compared to other submissions
  • 2. Effective Use of Gemini API (25%)
    - Meaningful and central integration of Gemini - Depth of AI implementation (not just surface-level usage) - Smart prompt design and response handling - Clear explanation of how Gemini powers the solution
  • 3. Technical Implementation (20%)
    - Code quality and structure - Backend and frontend integration - Error handling and performance - Scalability and architecture decisions
  • 4. UI/UX & User Experience (15%)
    - Clean and intuitive interface - Ease of navigation - Visual consistency - Overall user experience
  • 5. Impact & Practical Relevance (15%)
    - Real-world applicability - Clarity of problem statement - Potential for scalability - Value created for users

Questions? Email the hackathon manager

Tell your friends

Hackathon sponsors

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.