Key Dates (Save them on your calendars 📅):

1 Nov - 24 Nov: Register for the Coding Challenge and start hacking!

5 Nov: Submission opens at 1200 (GMT +8)

25 Nov: Submission closes - remember to submit your projects before 1200 (GMT +8)

25 Nov - 29 Nov: Judging period

30 Nov: Winners announcement. All winners will receive an email notifying them of their win.

You will need to submit a link to your GitHub repository. Make sure to follow the guidelines below to ensure your GitHub repository has all the necessary information and stands out! Here's what you’ll need:

📂 GitHub Repository Link

Submit a link to your GitHub repository containing all your project files. Ensure that the repository is well-organized. 💡Your last commit should fall within the submission timeframe to demonstrate active work and up-to-date development efforts.

🎥 Stand Out!

Make your project pop with a 1-minute video (or shorter) showcasing its key features.

✨ Tip: Focus on what makes your project unique and functional. Embed the video link directly in your README.md or share a YouTube link.

📝 Clear Documentation

A solid README.md helps users quickly understand your project. Make sure to include:

• A detailed explanation of your project’s workflow (from input to output) and how different modalities interact.

• Step-by-step installation guide: Include all necessary instructions, covering third-party APIs, dependencies, or frameworks used. This ensures anyone (especially the judge) can set up and run the project locally without a hitch.

• Screenshots or GIFs: Add visuals to demonstrate your app in action, giving reviewers a preview of the experience.

• Deploy Your App Live (Optional): Take it to the next level by deploying your project on a live server and linking it in the README.md. A live demo not only makes your submission more engaging but also allows users to quickly explore your app!

⚠️ Important: Missing documentation, unclear instructions, or incomplete project files may result in a lower evaluation score, so double-check everything before submitting!

💡 Tie Breaker! (Optional)

If your project competes closely with others, you can gain an edge by showcasing technical optimizations and performance improvements. Here’s how:

• Performance Metrics: 🚀 Provide measurable data like response time, query speed, or memory usage. Include code snippets where you optimized performance (e.g., API handling, better data structures). Highlight the impact of these optimizations in your README.md.
• Accuracy Metrics: 📊 Show how your project achieves better results, especially when working with multimodal inputs. Point out where you improved accuracy (e.g., refined embedding strategies, smarter data processing). Please explain how you measured success and the effect it had on results.
• Creative Optimizations: 🛠 Document any additional improvements, such as custom APIs, reduced latency, or novel ways of handling modality transitions (e.g., smoother voice-to-text recognition). Provide code examples and describe the improvements in your README.md.

Including these enhancements boosts your chances of winning and demonstrates your ability to assess and refine your work for better technical performance. Make sure to highlight these efforts clearly in your README.md to maximize your impact!

1/Innovation & Creativity (10%)

How original and creative is the project? Did the team experiment with innovative ways to combine different modalities like text, speech, and images? Does the project push the boundaries of multimodal GenAI and show fresh, out-of-the-box thinking?

2/Usability and User Interface (25%)

How intuitive and user-friendly is the app? Is the interface smooth and accessible for users with varying technical skills? Does it clearly demonstrate how different modes of interaction (e.g., text-to-speech, image search) work together in a coherent flow?

3/Quality of Documentation (25%)

Does the documentation effectively describe what the application does, the problem it solves and how it works?

4/Code Quality and Organization (10%)

Does your code follow best practices and standards for Next.js and Gemini? Is it well-formatted, self-documenting, and does it contain code documentation?

5/Functionality and Reliability (30%)

Does the application work as intended? Are errors effectively handled so that it won’t mess up the user experience?

🌟 A total of USD$700 worth of prizes is up for grabs 🌟

To be rewarded with a prize, become one of the top 5 winners!

• 1st Place will get USD$250 reward.
• 2nd Place will get USD$180 reward.
• 3rd Place will get USD$130 reward.
• 4th Place will get USD$80 reward.
• 5th Place will get USD$60 reward.