Find details on our facebook event page.
Here's Challenge the teams worked on:
Devices around get smarter. They turn to assistants. Yet, today they are still in a toddler phase. Teach them walking!
- Let your 'lazy self' speak: where can smart devices make your life easier? Yet: is your idea really more than just a simple replacement / mimicking of some real world thing? (I don't need an app to tell me, it's raining - I can look out of the window - these real things with non-touch-sensitive transparent panes)?
- How can capabilities of smart devices be enhanced? How can software expand on the available HW?
- Currently smart devices are islands and in isolation almost boring - can you build bridges?
Find resources online:
- https://developer.amazon.com/alexa
- https://github.com/alexa/alexa-skills-kit-sdk-for-nodejs
- https://echosim.io/
- https://github.com/alexa-pi/AlexaPi
- http://oauth.withings.com/api
- https://www.withings.com/eu/en/index/with-data
- http://wia.io/
- https://github.com/wiaio
- https://en.wikipedia.org/wiki/Business_Model_Canvas
Notes: for using some of these apis you need to register on their websites. In case you don't yet have an account, consider setting one up before the event. The list above is by no means exclusive - feel free to use any other tools, services, apis (while adhereing to their terms of use, please).
What you should bring?
- Ideas & inclination to create something new in a new team
- A notebook (with powersupply!)
- potentially a raspi or any other device you'd like to use
- coding experience helps - ideally already with alexa, withings, wia
- Sleeping bag or pads in case you'd like to take a nap
For presenting your results on Sunday to the jury, please:
- register to Open Ecosystem Network
- start a proposal - you can do this anytime and work on your proposal - you can find an example submission here.
- submit proposal before code freeze (Sunday, 09:00h local)
What does the jury expect from the proposals?
- A short description of your team's proposal that a five year old (or management) can understand
- Details:
- What problem is solved / addressed?
- How is it solved?
- Who are the main targeted audience or customers?
- What are the benefits / which value is created?
- What is still open?
- What would need to be done to make a real product and scale up?
- A prototype - the code & necessary documentation to make it run
- Don't forget the credits: list of team members (names, roles, anything else you'd like to share)
- Failure is an option: in case you got stuck somewhere or hit a wall: don't hesitate to still submit nevertheless & explain where the project got stuck.