Skip to content

rules.md

Latest commit

 

History

History
53 lines (41 loc) · 2.95 KB

rules.md

File metadata and controls

53 lines (41 loc) · 2.95 KB
Raw

Devpost rules and judging criteria

Source: https://amazonappdev2026.devpost.com/rules (read 2026-10-01, re-checked 2026-10-03; quotes below are from the 2026-10-03 reading). Re-check the page before submitting.

Dates (PT)

  • Submission: Aug 31 2026 10:15 AM - Oct 23 2026 12:00 PM. Judging Nov 9-20. Winners Dec 3.

Alexa+ track

"Build a working Agent Skill or a self-hosted MCP server, implementing MCP spec version (minimum acceptable version is 2025-11-25)"

Developers new to MCP may instead build a simulated Alexa+ experience in a web app (from the track page, read 2026-10-01). Ours: a real self-hosted MCP server (spec 2025-11-25, Streamable HTTP) plus a simulated Alexa+. The code must use the required technology at runtime, and the video must show it working.

Mini challenges ($5,000 each)

  • AWS Builder: "Any primary track project that incorporates AWS services (i.e. Amazon Bedrock, AgentCore, Strands SDK, Kiro Crew, SageMaker, etc.) with documented integrations". Ours: docs/challenges.md lists every AWS service, what it does and where it is in the code.
  • Open Source: "Create a new, additional open-source project or contribute to an existing public repository during the hackathon window, alongside a primary track submission". Making our own repo public is not enough: it needs a separate project (or a contribution to someone else's). Options in docs/challenges.md.

Demo video

"should be less than three (3) minutes. Judges are not required to watch beyond three minutes"

"should include footage that shows the Project functioning on the device for which it was built"

"must be uploaded to and made publicly visible on YouTube or Vimeo and a link to the video must be provided on the submission form"

"must not include third party trademarks, or copyrighted music or other material unless the Entrant has permission to use such material"

So: an edited, promotional-style video is fine, as long as it contains real footage of the project working. Use music you have a license for (royalty-free with a license, or none), and be careful with third-party logos and trademarks.

Judging (stage two, equally weighted)

  1. Tech Implementation: "How well is the project built, and how effectively does it use the required tech?"
  2. Design: "Does the project deliver a complete, coherent product experience? Is the interaction model intuitive and well-considered for the target device or platform?"
  3. Potential Impact: "Does the project make a credible, specific case for solving customer needs?"
  4. Quality of the Idea: "Is this a creative, imaginative use of the required tools?"

Submission deliverables

  • Working application; text description.
  • Repository: public with an open-source license, or private and shared with the judging team.
  • Demo video (above).
  • Product feedback on every tool/API/SDK used (FEEDBACK.md). Optional friction log, up to a 10% bonus (FRICTION_LOG.md).
  • Track and mini-challenge selection.