Exit to Site
Space / → next  ·  ← back  ·  F fullscreen + presenter mode
Before We Start

WiFi Details

Network Name

Foothills Library Public Wifi

Password

L1br@ryUs3r

YouthDevs Presents

SummerDevs '26

Welcome, builders. Today, you start with zero and finish with a working product.

Opening Ceremony

Thank You To Our Sponsor

SkipCourse

SkipCourse

Thank You To Our Sponsor

Ruach International Foundation

Ruach International Foundation

About YouthDevs

Helping students build projects for their community.

YouthDevs is an organization dedicated to helping students ship functional products from simply an idea. A lot of people don't know how to ship a product, so they think it's complicated. YouthDevs helps people do that! A lot of people in this room were probably scared to come here thinking you don't have any knowledge — but by the time you leave, you will have an excellent product!

Check out the website at youthdevs.org or scan the QR code.

Scan to visit youthdevs.org

youthdevs.org

Rules

Play Fair, Have Fun

Teams of up to 3

Preferred and max team size is 3. Have a balance of designers, coders, presenters.

Build during event hours

All code must be written today. Submissions are due at 4:00 PM sharp.

Be kind, ask mentors

Stuck? Mentors are roaming all day. Every question is a good one.

Today's Schedule

The Full Timeline

10:45 – 11:00Opening Ceremony
11:00 – 11:30Team Formation & Brainstorming
11:30 – 12:00Workshop
12:00 – 1:15Building
1:15 – 1:45Lunch
1:45 – 3:45Building
4:00Submissions Due
4:00 – 5:00Prepare Demo, Technical Judging
5:00 – 6:45Demos
6:45 – 7:00Closing Ceremony

Rubric

66.67%

Technical Criteria

Overall Technical Execution

  • 5 — Fully functional product. All core and secondary features work flawlessly without any noticeable bugs.
  • 4 — Mostly functional. Core features work smoothly, but secondary features have noticeable bugs.
  • 3 — Semi-functional prototype with critical or frequent bugs.
  • 2 — Barely functional. Only a single basic feature works, or heavily relies on mock data.
  • 1 — Non-working. Code doesn't compile, crashes instantly, or is a static mockup.

Style, UI

  • 5 — Intuitive UI, seamless navigation, highly professional and consistent visuals.
  • 4 — Clean UI, straightforward navigation, though a few asset choices feel unpolished.
  • 3 — Functional but basic UI. Layout lacks consistency, navigation feels clumsy.
  • 2 — Poor UX. Messy, misaligned, uninviting visuals lacking clear labels.
  • 1 — No intentional UI design. Unusable, broken, or completely blank.

Scalability

  • 5 — Exceptionally structured architecture, expands with no refactoring, handles massive traffic safely.
  • 4 — Fairly structured, expands with minor refactoring, handles standard loads safely.
  • 3 — Monolithic or rigid structure. Extending features requires a massive rewrite.
  • 2 — Hardcoded logic relying on hardcoded variables or static files.
  • 1 — No scalability consideration. Disorganized, no modular structure or database potential.

Rubric

33.33%

Non-Technical Criteria

Originality / Idea / Impact

  • 5 — Exceptionally significant and original, profound real-world impact, brilliant execution.
  • 4 — Interesting with clear real-world potential, well-executed, aligns with the theme.
  • 3 — Moderately original but lacks a strong, distinct impact. Basic execution.
  • 2 — Lacks originality or closely copies existing apps. Minimal real-world relevance.
  • 1 — No original thought or effort. Irrelevant to the hackathon theme.

Teamwork

  • 5 — Seamless collaboration. Tasks and effort shared equally among all teammates.
  • 4 — Clear signs of collaboration, fairly divided, minor imbalances.
  • 3 — Functional but siloed. Pieces combined at the end, uneven workload distribution.
  • 2 — Highly fragmented. One or two members did almost all the work.
  • 1 — No evidence of teamwork or cohesive group integration.

Demonstration

  • 5 — Immaculately thought out, error-free, presented equally by all students.
  • 4 — Smooth and mostly well-prepared, most members participated equally.
  • 3 — Functional but unpolished. Uneven presentation duties or minor technical hiccups.
  • 2 — Disorganized or confusing. Only one person presented, unclear communication.
  • 1 — Completely unprepared, chaotic, or non-existent demonstration.

What's On The Line

Prizes

🥇

1st Place

Dell Monitor + Internship at SkipCourse + Special Certificate

🥈

2nd Place

AI Glasses + Internship at Salus Daily + Special Certificate

🥉

3rd Place

Telescope + Special Certificate

4th

Special Certificate

5th

Special Certificate

Everyone

Digital Certificate, ASU Microcredential

Say Hi

Meet Your Mentors

Surya Sreenivasan

CSHS President

Deshna Arunkumar

CSHS Vice President

Shreemahor Sivakumar

CSHS Member & AI Club President

Who's Scoring You

Meet Your Judges

Brian Jacob John

ASU Alumni — Built websites for multiple schools

Karl Ersbenger

Founder, SkipCourse

Moses Katakanya

Founder, Ruach International Foundation

Blake Bergevin

IT Manager, BASIS Phoenix

Theme Reveal

🥁

Drumroll Please...

Theme Reveal

Build something to help students have healthy habits this school year.

How To Submit

Submissions on Devpost

4:00 PM

Submissions Due

Submit your project on Devpost by the 4:00 PM cutoff.

4–5 PM

Review & Demo Prep

Projects are reviewed while you work on your demo.

5 PM

Technical Judging

Technical judging begins at 5:00 PM sharp.

Submit at summerdevs26.devpost.com

Hacking Begins

Prompt: Build something to help students have healthy habits this school year.

00
Hours
00
Minutes
00
Seconds

Until submissions are due at 4:00 PM. Let's go!

Scan for all SummerDevs '26 links

All links at

summerdevs.youthdevs.org/links