Event Theme Here

Teams of Code/Interactive students will design and build a cool tech product that features an original solution for a problem. 

The problem can be a ....

1. Heath related problem that affects you or your peers at school

2. Heath related problem that affects people in your community

3. Heath related problem that affects people across the globe

 

WIFI: MSFTOPEN (no password)

See a map of the space, Microsoft:  http://bit.ly/microsoftmap

 

Schedule- Saturday, January April 2nd

9:00am - 10:00am Check-in + Breakfast + Volunteer Meeting + Student Scavenger Hunt

10:00am - 11:00am Event Kickoff + Devpost and Slack Setup

11:00pm - 12:00pm  Design Workshop

12:00am - 1:00pm Worktime

1:00pm -2:00pm Lunch, Game and Keynote

2:00pm - 3:00pm Worktime

3:00pm - 4:00pm Github/Azure Workshop

4:00pm - 4:30pm Worktime

4:30pm DEADLINE TO SUBMIT FINAL PROJECTS ON DEVPOST 

4:30pm - 5:00pm Pitch Practice Workshop

5:00pm - 5:30pm  Dinner and Pitch Practice

5:30pm - 6:45pm Student Product Pitches to Judges (Main Space) 

6:45pm - 7:15pm Judges Deliberate + Clean Up + Thank You Cards + Surveys 

7:15pm - 7:30pm Award Ceremony 

Eligibility

Your group must have between 3 and 5 participants from your school.

All students must be a part of C/I's in-school or after school programs.

All students must complete an initial brainstorming activity before they arrive at the hackathon.

All students must have their permission slips upon arrival or have their teacher e-mail permission slips to Programs@weare.ci before arrival.

Requirements

EACH TEAM HAS 3 DELIVERABLES 

1. Something coded

  • Choice #1: Your tech product (e.g. web app or mobile app). Try to make it as functonal as possible. However at a minimum, it can be a static website. 
  • Choice #2: A website that showcases your problem and solution and shows what your tech product would look like if you created it. 
  • Tools: Cloud9 for for browser text editing. Azure cloud for hosting.

2. A Complete project submission on Devpost 

  • Must include the url for your app / website. 
  • Make sure to give your team time to write your answers! 

3. A 2-minute pitch presentation  

4. *Bonus* 1-minute video 

  • Theme: "Learn. Build. Collaborate"
  • Create a short (fun / creative) video about your team's experience at C/I Code Camp. What did you learn? What did you build? How did you collaborate? 
  • Submit the url in your Devpost submission as the "Video Demo" 

--

 

YOU MUST INCLUDE YOUR PROBLEM + SOLUTION + VALIDATION IN YOUR FINAL SUBMISSIONS

(Can be included in your tech product / website, pitch, or Devpost submission) 

Problem + Validation:

  • Describe the problem that your team is trying to solve
  • Explain why it is a problem. 
  • Explain the validation process that you used and the results of your validation process. (i.e. "The Syrian Crisis has harmed the lives of 5.5 million children, but only 19/20 students surveyed said they knew about it," "Eating beef is bad for the planet, but only 17/20 students surveyed said they consider this when deciding what to eat.") 

Solution + Validation: 

  • Describe your tech solution that helps to solve your problem
  • Explain why it is a good solution.  
  • Be very detailed while describing the features.
  • Explain the results of the validation process for your solution. (i.e. "We surveyed __ people and __ people said that our website increased their interest in the problem and that they would use our tech solution to help solve it.)
  • Try to make your solutions as functional as possible (The more it works, the better!). However at minimum, if your team is only able to show what the solution looks like on your website without it actually working, that is acceptable. 

Hackathon Sponsors

Prizes

$7,000 in prizes
Best Overall Hack
1 winner

You are presenting at Creative Tech Week, going to the Xamarin Incubator, a Udacity Membership, and Prize Bag

Most Technical Hack
1 winner

Most Technical- Creative Tech Week Pass, Coursehorse Gift Cards, Prize Bag

Most Ambitious Hack
1 winner

Most Creative- Xamerin Incubator, Prize Bag

Best Pitch at the Hackathon
1 winner

Best Pitch- Xamerin Incubator, Prize Bag

Potential to Creative Change
1 winner

Potential to Creative Change- Xamerin Incubator, Prize Bag

Devpost Achievements

Submitting to this hackathon could earn you:

How to enter

All student participants will work with mentors and attend workshops in order to build a tech products that solve important teen problems.   

Step 1: Identify the Problem: The problem that you choose to address can be any health related problem. 

  • Does the team experience the problem personally?
  • Will the problem affect you community?
  • Is this a problem experienced in another country? 

Step 2: Brainstorm Solutions: Think of tech solutions that you can implement for the problem that you identify.  

  • Is your solution a new web or mobile app?
  • Is your solution a new website? 
  • Is your solution a modification or addition to an existing tech product?
  • How can you add technology to any factor surrounding your problem that is NOT currently using technology? 

Step 3: Research: Make sure that your solution is original and feasible by researching other technologies and apps that already exist.  

  • Is your solution original? 
  • Is your solution possible? 
  • If your idea already exists, how can you can make it better or add an extra feature? 

Step 4: Validation:

Validate your problem by either:

  • Surveying students at the hackathon if they experience that problem.  If no one experiences that problem, perhaps you're not solving the right thing!  
  • Researching for data from reliable sources that show many people experience your problem. 
  • Use our C/I Validation Form (http://bit.ly/civalidationform).  

Validate your solution by:

  • Surveying students at the event if they would use that product.  (Be prepared to present this information in your final pitch -- for example "We surveyed 40 students and over 60% said that this was a problem they experienced.  Over 70% said that they would use our solution.")
  • Use our C/I Validation Form (http://bit.ly/civalidationform).  

Step 5: Details and Features: What special features will your product have?  How will your users interact with your product?  Answer all of the questions provided in your product submission and do research as you go.  While thinking about your product, evaluate your idea and answer the following questions:

  • Will people use your app?
  • Would you use your app?
  • Is there a better solution?
  • Is there a better way to phrase your solution?
  • Is your solution too simple (or complex)?

Step 6: Wireframes: Plan your product's layout. 

Step 7: Attend Workshops: Learn new tools that you can implement in your product. Workshop resources: 

Step 8: Code your Product 

Step 9: Refine and Improve: Keep improving your product until final submission at 5:00pm on Saturday 4/2!

Step 10: Pitch Practice: Practice what you are going to say in front of the judges!  You only get 2 minutes to present, so you have to make a good impression and stand out!

Judges

Clive Henry

Clive Henry
Sr. Business Development Manager at Adobe

Pernell Brice

Pernell Brice

Fernado Tirado

Fernado Tirado

Udi Falkson

Udi Falkson

Stacey Jaffe

Stacey Jaffe

Liza Conrad

Liza Conrad

Judging Criteria

  • Potential to Create Change
    Did you choose to focus on a major teen problem? Does your tech product have the potential to solve it? Is your tech product a vitamin or is it a painkiller?
  • Technical Prowess
    How much of your coding knowledge did you implement? Did your team challenge yourselves by learning something new from your mentor or at a workshop to use in your project? Did you implement an API to make your app functional?
  • Creativity
    Is the idea original and unique, or just a copy of something that already exists? Creative solutions show a students' imagination regarding the problem and solution as well as the product features that are presented.
  • Presentation
    How well did the team present their project? Was the idea well communicated? Were the visuals engaging and appropriate? Did the team share presentation responsibilities? Was there a hook to build audience interest?

Questions? Email the hackathon manager

Tell your friends

Hackathon sponsors

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.