<aside> 🧭 NAVIGATION

🎯 Problem Statement

🧑🏻‍⚖️ Judging Criteria

💻 Submission Requirements

🏆 Prizes

📚 Resources

🤝 Q&A with the Organizers

</aside>

<aside> ✅ Getting Started

🧩 Hacker Checklist

❓ FAQs

</aside>

<aside> 🔗 Community Channel and Links

🔮 Discourse

</aside>

🔙 Back to Home Page

Evaluation Criteria

1. Innovation

   • Originality and creativity of the solution.
   • How unique or out-of-the-box is the snap-in? Does it bring fresh ideas to the DevRev ecosystem?

2. Technical Complexity

   • The level of technical skill demonstrated in the development.
   • Does the solution involve advanced problem-solving, algorithms, or use of DevRev APIs in creative ways?

3. Usefulness to Businesses

   • Practicality and ease of adoption by businesses.
   • Is the snap-in solving a real problem?
   • How intuitive and easy is it for businesses to start using the snap-in with minimal onboarding?

4. Integration Quality

   • Code quality and production readiness of the snap-in.
   • Does it meet high standards for maintainability, scalability, and reliability?

   Key Focus Areas for Production Readiness:

   • Secrets Management: No hardcoding of sensitive information (e.g., API keys, tokens).
   • Customizability and Reusability:
     • No hardcoded values tied to specific customers or use cases.
     • Built to be reusable across different customer scenarios.
   • Packaging:
     • Snap-in can be directly installed and functions without requiring manual configuration.
     • Avoids dependency on the installer organization.
   • Endpoints:
     • Uses public or publicly configurable endpoints for seamless deployment.

5. Documentation (Detailed README)

   • A comprehensive README that explains:
     • Installation and setup instructions.
     • Usage guide with examples.
     • Customization details.
     • Limitations, if any.
   • The README should ensure users can understand and deploy the snap-in easily.

6. Video Submission/Presentation

   • A short (2–5 minute) video showcasing:
     • The problem the snap-in solves.
     • Key features and functionalities.
     • A quick walkthrough or demo of the working solution.

7. Working Demo in a DevRev Demo Org

   • The snap-in should be functional in a demo org for evaluation.
   • Judges should be able to interact with and test the snap-in without issues.

Tips for Participants

• Focus on Reusability: Think about how your snap-in can help multiple businesses, not just one specific use case.
• Think End-to-End: Aim to deliver a solution that’s not just functional but also easy to adopt, with no manual setup hurdles.
• Polish Your Presentation: A clear, concise, and engaging video or demo can make a big difference.
• Test Thoroughly: Ensure your snap-in is robust and works as expected in various scenarios.