Competition day puts everything from the workshops into practice. Your team receives a challenge, plans a solution, builds a working web application, and presents the final result.
SEE HOW IT WORKSTeams receive the official application challenge and requirements.
Understand the requirements, divide responsibilities, design the solution, and decide how the application will work.
Turn the plan into a functional web application.
Respond to new information or requirements introduced during the competition.
Finalize the application and submit the required project materials before the deadline.
Demonstrate the finished application and explain the team's engineering decisions.
Teams will receive a web application challenge on competition day. You will be responsible for interpreting the requirements and deciding how to implement the solution.
There is no required team structure. Teams decide how to divide the work based on their strengths and strategy.
Whether you pair program on a single monitor, split strictly into frontend and backend, or have one person write tests while another builds UI—the process is entirely up to you.
Real software projects rarely stay exactly as planned. During the WebForge, teams should be prepared to adapt.
Projects are scored out of 100 points across seven categories.
Does the application meet the provided requirements and function correctly?
How effectively were authentication, persistent data, application logic, GitHub, and deployment implemented?
Is the application intuitive, coherent, responsive, and easy to use?
How effectively did the team debug problems and respond to the unexpected requirement change?
Can the team clearly demonstrate and explain its solution?
Can the team explain its Excalidraw diagram and how the major parts of the system interact?
Has the application been deployed correctly, connected to a domain, prepared for search discovery, and evaluated with PageSpeed Insights?
A working production URL, the GitHub repository, the final application, the Excalidraw system plan, and evidence that the team tested and measured the result.
Judges may navigate the deployed application, test core requirements, review authentication and persistent data, inspect responsive behavior, and ask the team to explain implementation decisions.
Present the problem, demonstrate the main user journey, explain the system, show how the change request was handled, and identify one challenge the team investigated.
Before submission, confirm required tasks are complete, team roles are clear, accounts and access work, materials are ready, dependencies are resolved, and the final production build has been verified.
The submitted version at the official deadline is the version evaluated. Judges apply the same published 100-point rubric to every team.
The workshops give you the tools. Competition day tests what you can do with them.
"You will not know exactly what you are building until the challenge drops."