California · CA-49
Heart Angel
Catherine Wang
CPR training, AED lookup, and emergency response support.
Health and public-safety apps work well when the demo shows a real workflow under pressure.
Counselor intelligence brief
A practical guide for middle and high school students who want to build an app, enter through the correct congressional district, and turn the project into a credible application-season artifact.
Updated May 28, 2026. National registration is open, with the 2026 deadline listed as October 26, 2026. Member offices may publish local instructions, contacts, and announcement timing.
The Congressional App Challenge is a district-level software competition run through participating U.S. House offices. Students build an original app, submit a short application and public demo video, and compete against other eligible students in the district where they live or attend school.
The college-application value comes from three things: a built product, a local civic problem or user need, and recognition from a Member of Congress if the student wins. It is strongest when the app is still usable after the contest and can sit beside a GitHub repo, demo link, research note, or community pilot.
2026 deadline
Oct. 26
Official rules PDF lists 12:00 pm EDT. The registration page lists 8:00 pm ET, so students should submit well before the day-of deadline.
Team size
1 to 4
At least half the team must live or attend school in the submitting district.
Project age
After Oct. 30, 2025
For 2026, prior apps are allowed only if created after that date. A 2.0 entry should highlight the new coding.
This contest has one national portal, but eligibility and judging run through congressional districts. The first advising move is to identify the student's district choices and confirm that at least one is hosting the challenge.
No data leaves your browser.
Students often treat CAC like a single national contest, then discover late that their Member is not participating, their team district mix fails, or their local office has a contact, announcement cadence, or judging process they never checked.
Recent public winner announcements lean toward practical apps with visible users: health, sustainability, safety, transportation, food systems, and local civic needs. California winners are especially useful for Jay's students, but East Coast examples show the same core pattern.
California · CA-49
Catherine Wang
CPR training, AED lookup, and emergency response support.
Health and public-safety apps work well when the demo shows a real workflow under pressure.
California · CA-13
Aahlad Bysani
Satellite-data tool for detecting and exploring harmful algal blooms.
Strong district fit: local water, wetlands, and public data turned into a usable monitoring app.
California · CA-30
Andrew Oh, Hannah Lee, Ginna Kim, and Aaron Kim
Mobile app for coordinating rides.
Team projects need clean role division and a polished user experience because judges see the app through the demo.
California · CA-35
Alexander and Melissa Lee
Wi-Fi enabled chair-stand testing to help assess fall risk in older adults.
Hardware plus software can stand out if the student can explain the sensor, data, and clinical use case.
East Coast · MA-03
Reya Kannan
Restaurant and farm workflow for food-waste donation, compost, and local sourcing.
A local problem becomes stronger when the app connects two sides of a real ecosystem.
East Coast · NY-20
Daniel Joseph
Clinical-skills simulator with patient intake, AI avatar interaction, diagnosis, and feedback.
AI can help when it supports a bounded educational workflow and the student can defend the build choices.
East Coast · MA-04
Aaron Prager
Diabetes management app for smarter glucose-control decisions.
Personal problem knowledge can sharpen the product if privacy and medical-safety limits are handled carefully.
East Coast · NJ-04
Ava Obara, Skye Huang, and Abigail Riddle
Nutrition app that presents food facts in a clearer format.
Consumer-information apps need more than content. The judging question is what the interface helps users decide.
The best CAC entry is a finished small product with one clear user loop. Judges can consider idea quality, implementation, user experience, design, and coding skill, and they may request app or source-code access to verify function.
Example: CPR-certified volunteer, restaurant owner, diabetic teen, farm manager, student practicing patient intake.
Sign in, enter data, get recommendation, send alert, schedule pickup, save record, export result. One complete loop beats five mock screens.
The submission asks about technical difficulty. Keep a build log so the answer names the hard bug, the design choice, and the fix.
The 2026 rules permit AI tools if the student fully discloses usage. AI should support specific parts of the project. The student still needs significant personal technical contribution and enough understanding to explain the app under questioning.
Week 0
Find home and school districts, confirm participation, identify the Member office page, and register.
Weeks 1 to 2
Choose the user, write the one-sentence purpose, sketch the minimum viable workflow, and decide solo vs team.
Weeks 3 to 7
Ship the working loop, keep a build log, and document any open-source libraries, APIs, datasets, or AI tools.
Weeks 8 to 9
Run the app with three real users, record friction, fix the highest-impact issue, and prepare screenshots.
Weeks 10 to 11
Record a 1 to 3 minute public YouTube or Vimeo video that shows the actual app working.
Final week
Complete the profile, eligibility quiz, app questions, video link, and exit-questionnaire follow-up. Submit before deadline day.
Use these links before making a student-facing decision. District participation and office pages can change during the season.