Ages 15–18 · Grades 9–12 · Computer Science

ChallengeForge

An entry lands on your desk. Does it clear the bar?

A student app showcase hands a judge a tiny finished app and a rubric. To ship your own work you have to learn to read it the way a judge will. Here, an entry lands on your desk: read what it actually is, decide whether it clears the bar — and if not, which pillar it breaks — then reveal the verdict and the concrete fix.

The five pillars are generic judging criteria, not any one contest’s rules — student app contests change their rules every year, so always check the official current rules. Runs on your device — nothing leaves it.

Loading the judging lab…

A case · you decide

Dev's entry versus the rubric

Dev, 17 — submitting a small app to a student showcase that judges each entry in three minutes

The idea in play: a rubric is read before you build the demo — the judge scores what the rubric names, in the time they actually have.

Dev's app tracks the bus home and has a beautiful settings screen with seven themes. The showcase rubric has four lines: a clear problem, it works without explanation, it is accessible, and you can explain one design choice. Judges get three minutes.

Makers tend to show what they are proudest of. Judges score what is on the sheet in front of them.

Three minutes goes fast. Anything a judge has to be told before it makes sense costs time the rubric does not reward.

What should open Dev's three-minute demo?

Testing on his phone, Dev finds the bus times are tiny grey text on a pale map. What does he do?

Judge an entry →

What next? Pick a door

Chosen from what this app is about. What you open is remembered on this device only.