This hackathon is about highlighting the possibilities of edge AI leveraging the Copilot+ PC with the Snapdragon^® X or X Elite. Teams of up to five developers will work together to build an on-device application that highlights the creative use cases on edge AI. 

The Edge AI Developer Hackathon is taking place in multiple regions around the globe. The hackathon will kick off in Bengaluru, India in June and then in various other regions including Brazil, Kingdom of Saudi Arabia, Taiwan, Korea, London, China, New York, and San Francisco. Exact dates for each region will be announced shortly. If interested, submit this form and we’ll reach out closer to the event.

Below is the eligibility criteria for participating:

• Age Requirement: Participants must be at least 18 years of age at the time of registration
• Open to both individuals and teams (up to five members per team)
• Residency: The hackathon is open to residents of the country in which the hackathon is taking place. For example, to participate in the Bengaluru hackathon, you must be a resident of the Republic of India.
• Exclusions:
  • Employees, interns, or contractors of Qualcomm Technologies, Inc. or its affiliates are not eligible to participate.
  • Government officials or employees of government entities are not eligible to participate.
  • Individuals subject to trade restrictions, including sanctions or embargoes, are not eligible.
  • Participants who have previously participated in the Edge AI Developer Hackathon in another region are not eligible to participate again. Each individual may only participate in one regional edition of the Edge AI Developer Hackathon.

There is no particular theme or focus as long as your application runs primarily on-device. Target platform is the Snapdragon® X or X Elite. Devices will be provided to teams for use during the hackathon.

Please see each region’s event page for registration details. If registration is not yet open, please submit this form and we’ll reach out as soon as registration opens.Each person on a team must register for the hackathon in the region they wish to participate using the same Project Title. If you have a team of four developers, each person on the team must individually register and submit the team’s project proposal.

Limitations vary by region and are determined by the number of devices we have available. 

Teams of 3-5 are recommended for the hackathon. Teams tend to have more fun and build more impactful projects. With just a short timeframe to develop something meaningful, having a few extra hands can make a big difference. Participants must register as a team to participate.

This is an in-person event. If you are participating on a team, the majority of your team must be in person. If you have any team members participating remotely, your team is responsible for ensuring they have all the hackathon information, understand the schedule, and for providing a means of communication amongst the team throughout the event.

Teams should be 3 - 5 members. Some hackathons may be open to teams of 2 - 5. Please check the page for the event you're interested in for more information.

Below are the rules and regulations of the hackathon:

                Eligibility Criteria:

• Age Requirement: Participants must be at least 18 years of age at the time of registration
• Open to both individuals and teams (up to five members per team)
• Residency: The hackathon is open to residents of countries not restricted by applicable export control or sanctions laws.
• Exclusions:
  • Employees, interns, or contractors of Qualcomm Technologies, Inc. or its affiliates are not eligible to participate.
  • Government officials or employees of government entities are not eligible to participate.
  • Individuals subject to trade restrictions, including sanctions or embargoes, are not eligible.
  • Participants who have previously participated in the Edge AI Developer Hackathon in another region are not eligible to participate again. Each individual may only participate in one regional edition of the Edge AI Developer Hackathon.
• Original work: Participants must submit original work created during the hackathon period.

Agreement to Rules: By registering, participants agree to abide by the official hackathon rules, code of conduct, and decisions of the organizers and judges.

Project Submission Requirements:

To be considered for the prize, your project submission must meet the following criteria:

• The application must be provided in a GitHub repository with the following files in addition to your code:
  • A README file with the following information:
    • An app description
    • Dev names and a way to connect (LinkedIn or email)
    • Setup instructions from scratch, including dependencies if applicable
    • Run and usage instructions
  • An open-source license (refer to https://choosealicense.com for help choosing)
• the application must be runnable using your provided instructions
• the application and most components must run on the edge (hybrid edge/cloud is ok but majority should run locally)
• the GitHub repo must be submitted by the hackathon deadline
  • A link to your GitHub repo must be provided via a Microsoft Form submission. Form will be shared at the beginning of the hackathon
• Nice to have, but not required, components include:
  • Tests and testing instructions to verify the app setup
  • Notes section containing additional information not covered in the app description
  • References used while developing the app
  • Well-commented code

Project Evaluation Criteria:

Each application submitted at the end of the hackathon will be evaluated based on 5 categories with a total of 100 achievable points. Additional details about the scoring/assessment framework within each category will be shared with participants prior to the event.

• Technical Implementation – 40 points
• Application Use-Case and Innovation – 25 points
• Local Processing and Privacy – 15 points
• Deployment and Accessibility – 10 points
• Presentation and Documentation – 10 points

Prize Award Rules:

• Number of Winners: Two teams will be awarded prizes at the conclusion of the hackathon.
  • Grand Prize Winner
  • Runner-Up (People’s Choice) Winner
• Grand Prize Selection: The grand prize will be awarded to the team with the highest total score based on the evaluation criteria provided. Judges will evaluate each team across five categories, with a total of 100 possible points. If there is a tie between multiple teams, organizers and judges will vote on their selection for the grand prize winner.
• People’s Choice Award: The Runner-Up prize will be awarded based on peer voting. Each participating team will cast one vote for a team (other than their own) they believe deserves recognition. The team with the highest number of votes will receive the People’s Choice Award.
  • Voting Restrictions:
    • Teams cannot vote for themselves.
    • In the event of a tie, organizers will conduct a secondary round of voting or make the final decision at their discretion.

Eligibility for Prizes: Only teams that have submitted a project that meets the Project Submission Guidelines by the hackathon deadline and have provided a demo will be eligible for either award.

For additional rules and terms of the hackathon, please see the Official Rules for the regional event you have registered for.

Rules and regulations may be different in various regions. Please review the Official Rules for the event you are participating in for more information.”

The hackathon will last for approximately 24 hours, followed by a post-event social reception for participants. The two hours preceding the event will be reserved for hardware distribution, intros, kickoff, and applicable masterclass sessions. Expect to dedicate your entire weekend to this effort; sessions will generally begin around 12pm Saturday and end in the evening on Sunday.

To maintain fairness, the entirety of the application functionality submitted for prize consideration should be written/generated during the main body of the hackathon. As such, most of the code should be written during the event. The only exception to this rule is an allowance for personal, open-source frameworks that you may want to leverage in the hacks. This should be included in the proposal submission and approved beforehand. Without approval, pre-existing code should not be considered. For approval, email [email protected]

In general, no. Your application needs to run on the target platform – the Snapdragon^® X or X Elite. Specific events may impose superseding requirements, and these will be made clear in the announcements. For example, a particular hack may require integration of a partner application such as Neo4j or AnythingLLM.

Application submissions must adhere to the following guidelines:

To be considered for the prize, your project submission must meet the following criteria:

• The application must be provided in a GitHub repository with the following files in addition to your code:
  • A README file with the following information:
    • An app description
    • Dev names and emails
    • Setup instructions from scratch, including dependencies if applicable
    • Run and usage instructions
  • An open-source license (refer to https://choosealicense.com for help choosing)
• the application must be runnable using your provided instructions
• the application and most components must run on the edge (hybrid edge/cloud is ok but majority should run locally)
• the GitHub repo must be submitted by the hackathon deadline
  • A link to your GitHub repo must be provided via a Microsoft Form submission. Form will be shared at the beginning of the hackathon
• Nice to have, but not required, components include:
  • Tests and testing instructions to verify the app setup
  • Notes section containing additional information not covered in the app description
  • References used while developing the app
  • Well-commented code

Yes, mentors from Qualcomm and supporting partners will be available online or in-person for most of the hackathon. 

You can contact the onsite mentors, use the Qualcomm Developer Discord or AI Hub slack, or pull from any other resources available online.

The best way to ask a technical question is to describe the issue in context, give relevant project details, and provide relevant implementation details. For example: if you are getting an error while making an API call to a language model server in Python and need to ask for help, you should provide:

1. The specific error you are getting
2. What you are building, along with the piece that is not working
3. The python version, language model version, OS, error traceback, and any other relevant information

Each application submitted at the end of the hackathon will be evaluated based on 5 categories with a total of 100 achievable points. Additional details about the scoring/assessment framework within each category will be shared with participants prior to the event.

• Technical Implementation – 40 points
• Application Use-Case and Innovation – 25 points
• Local Processing and Privacy – 15 points
• Deployment and Accessibility – 10 points
• Presentation and Documentation – 10 points

Judges will vary by region but will include Qualcomm employees and employees from partners supporting the hackathon. Judges will be identified prior to the hackathon.

Prizes vary by region. For prize information, see the registration page for the region.

Hackathon winners will be announced shortly after the hackathon development period ends. Participants will be given 24 hours to develop their application and 5-10 minutes to demo their application to all participants and judges after the development period. After all demos, the judges will score each team’s application and a winner will be announced. 

Prizes will be given to the winning teams at the conclusion of the hackathon event. 

You should bring your primary laptop, a notebook and pen/pencil for planning, and a backpack. You may also consider a water bottle and snacks, though refreshments will be provided. It is recommended you wear comfortable clothes.

Yes, unless otherwise noted.

No, you are responsible for travel to/from the venue as well as accommodation if applicable.

Your project needs to be contained in a GitHub repository. A link to your GitHub repo must be provided via a Microsoft Form submission. Form will be shared at the beginning of the hackathon and must be submitted prior to the end of the hackathon.

To be considered for the prize, your project submission must meet the following criteria:

• The application must be provided in a GitHub repository with the following files in addition to your code:
  • A README file with the following information:
    • An app description
    • Dev names and emails
    • Setup instructions from scratch, including dependencies if applicable
    • Run and usage instructions
  • An open-source license (refer to https://choosealicense.com for help choosing)
    • the application must be runnable using your provided instructions
    • the application and most components must run on the edge (hybrid edge/cloud is ok but majority should run locally)
    • the GitHub repo must be submitted by the hackathon deadline
  • A link to your GitHub repo must be provided via a Microsoft Form submission. Form will be shared at the beginning of the hackathon
• Nice to have, but not required, components include:
  • Tests and testing instructions to verify the app setup
  • Notes section containing additional information not covered in the app description
  • References used while developing the app
  • Well-commented code