Coding

Description

The Coding category invites participants to demonstrate their programming prowess and innovative problem-solving skills through the development of software solutions, algorithms, or applications. Open to individuals or teams of up to three participants, this category encourages participants to tackle real-world challenges by harnessing the power of code.

Projects can explore diverse domains, such as artificial intelligence, web and mobile applications, data science, cybersecurity, game development, and more. Participants are urged to embrace creativity, technical precision, and a collaborative or individual approach to present impactful solutions.

Themes

Artificial Intelligence and Machine Learning – Intelligent systems and predictive modelling.
Web and Mobile Applications – User-friendly platforms addressing everyday problems.
Data Science and Analytics – Insights from data to drive decisions.
Cybersecurity – Enhancing privacy and protection in the digital age.
Sustainable Tech Solutions – Coding for environmental and social impact.

Application Rules

Eligibility

Submissions are open to individuals or groups of up to three participants.
Submissions must include a complete solution and working prototype/demo. Incomplete submissions or those lacking functional results will not be accepted.

Code Repository

Submit the source code through a public GitHub repository or similar platform (GitHub, GitLab, Bitbucket, etc.).
The repository should be well-organised, include clear documentation (README), and provide instructions on how to run or use the code.
Ensure all necessary dependencies, libraries, or frameworks are specified.

Working Prototype/Demo

Provide a working prototype or demo of the software or application in an accessible format.
For web applications, a live demo or hosted website link should be provided (e.g., on platforms like GitHub Pages, Heroku, Netlify).
For mobile applications, submit an APK (Android) or IPA (iOS) file, or a link to a public test version (e.g., via TestFlight).
The demo should be functional and allow judges to interact with the software to experience its features.

Project Description

Submit a brief written description (300-500 words) explaining the project’s purpose, target audience, features, and the problem it solves.
Include details about the technical stack, frameworks, or languages used and any relevant challenges faced during development.

Judging Criteria

Creativity and Innovation (25%)

Originality: How unique and creative is the project? Does it introduce new concepts, ideas, or solutions that haven’t been explored in existing applications or technologies?
Problem-Solving: How effectively does the project address a real-world problem? Does it offer an innovative solution or new perspective in tackling the issue?
Technical Innovation: Does the project utilise advanced techniques or technologies (e.g., AI, machine learning, advanced algorithms, novel frameworks) to enhance its functionality?

Functionality and Technical Complexity (20%)

Working Prototype: Does the project demonstrate a fully functional, user-friendly prototype or demo? Is it free of major bugs or issues that hinder user experience?
Technical Sophistication: How complex is the code and overall architecture? Does the project showcase advanced technical skills (e.g., use of databases, API integration, multi-threading, or real-time functionalities)?
Quality of Code: Is the code well-written, efficient, and easy to understand? Are best coding practices, such as proper documentation, clean structure, and clear naming conventions, followed?

Usability and User Experience (20%)

Ease of Use: How intuitive is the user interface? Is the application easy to navigate and accessible for its intended audience?
Design and User Interface: How well-designed is the user interface (UI)? Is it aesthetically pleasing and functional, with clear navigation and appropriate visual elements?
Functionality: Does the software provide a seamless user experience without crashes or technical errors? Is the interaction smooth and logical?

Impact and Relevance (20%)

Real-World Application: How relevant is the project to real-world problems or current industry needs? Does it have the potential to be applied in practical settings?
Scalability and Future Potential: Does the solution have potential for growth or future development? How easily can it be scaled to accommodate a larger audience or extended functionality?
Social or Environmental Impact: Does the project have positive implications for society, the environment, or specific communities? Does it contribute to solving larger global issues (e.g., sustainability, education, healthcare)?

Technical Presentation and Documentation (15%)

Code Repository: Is the GitHub repository (or equivalent) well-organised and easy to navigate? Does it include clear, detailed documentation that explains how to use and contribute to the project?
Technical Documentation: Does the project include sufficient technical documentation (e.g., setup instructions, API documentation, system architecture)? Is it clear enough for someone else to understand and replicate the setup or code?
Project Description: Is the project description concise and clear? Does it effectively communicate the project’s purpose, key features, and challenges overcome during development?