ubi i/o APIs Hackathon

APIs are eating the world and so will ubi i/o startups!

ubi i/o is proud to organize a special hackathon in San Francisco for an entire week (online)! (June 3rd - 9th, 2016). Let’s hack around three new APIs provided by Akeneo, OpenIO and Sevenhugs!

The challenge is open to everyone willing to play & create with our APIs. Sign-up and compete for one of the 3 prizes valued at more than $1300 each. Participants must attend the opening (June 3rd) and closing event (June 9th) in San Francisco.

We thank our sponsor OVH. With a community of over 1,000,000 customers, OVH is the third internet hosting company in the world.

Prizes

The top teams for each API will win the following prizes:

AKENEO’s PRIZE:

• $1,100 Amazon gift card

• OVH: Access to OVH public cloud ($240) + goodies

OPENIO’s PRIZE:

• $1,100 Amazon gift card

• OVH: Access to OVH public cloud ($240) + goodies

SEVENHUGS’ PRIZE:

• $1,100 Amazon gift card

• OVH: Access to OVH public cloud ($240) + goodies

CODINGAME’s HACKER PRIZE:

• $300 Amazon gift card for the best codingamer

• OVH: Access to OVH public cloud ($120) + goodies

Challenges

ubi i/o APIs Hack

Use one of the three featured APIs to create brand new use cases. Your project must significantly rely on the API.

Akeneo

Akeneo is a Product Information Management platform helping manufacturers and retailers to collect and distribute product data across multiple channels. Our tool is entirely open source (Symfony2 framework / Hybrid storage with MySQL + MongoDB) and relies on a very flexible import / export API that can be leveraged to connect Akeneo with any third party system (for instance an e-commerce platform like Magento, Shopify or Prestashop).

Our customers and users are using Akeneo as a hub for their product data. They are looking for innovative ways to exploit their data. Feel free to propose / experiment any connection between Akeneo and another system that could leverage product data (e-commerce, print, mobile apps, marketplaces, recommendation engines, ...)

Use cases / Examples :

• Connector with an e-commerce tool like Shopify or WooCommerce

• Slack connector to trigger some automatic notifications when a product has been updated in Akeneo

• Connector with a translation engine (like translations.com or Textmaster)

Doc : http://docs.akeneo.com

OpenIO

Want to be a part of our open source community? Welcome aboard for this hackathon where all your codes will be pushed on github to build the future of OpenIO.

OpenIO’s Object Storage API differs from a conventional filesystem: instead of directories and files, you will manipulate containers where you store objects and where one container can hold millions of objects.

Guess what? OpenIO provides SDKs for the language you prefer:

• Python SDK: https://github.com/open-io/oiopy/blob/master/docs/object_storage.md

• Java SDK: https://github.com/open-io/oio-api-java

• C SDK: https://github.com/open-io/oio-sds/wiki/C-SDK

Didn’t find what you were looking for? Here is a way to develop your own client, in the language of your choice: https://github.com/open-io/oio-sds/wiki/Write-your-own-client

Let your imagination build something useful and awesome! Lack of ideas? Here are a couple of interesting use cases:

• Wordpress/Owncloud connector to store data inside OpenIO (need to develop the PHP client first, again this is challenging but a good way to win the contest)

• ElasticSearch connector to store and retrieve indexes directly from OpenIO: https://www.elastic.co/guide/en/elasticsearch/plugins/current/repository.html

• Alfresco connector to store and retrieve indexes directly from OpenIO : http://docs.alfresco.com/4.1/concepts/S3content-intro.html (S3 sample)

• Add OpenIO to the trusted registry driver of Docker: https://github.com/docker/distribution/tree/master/registry/storage/driver

• Build OpenIO access driver for Pydio (https://pydio.com/en/docs/developer-guide/other-access-drivers)

Play with OpenIO’s API & get help from one of our development team member to win the $1100 prize!

Sevenhugs

Tired of using your smartphone or a dozen of remote controls to control your devices at home ? Sevenhugs has unveiled its contextual Smart Remote at the 2016 CES, and now it’s time for developers to play with it!

The Sevenhugs Smart Remote offers multi-device control from a sleek, simple touchscreen interface. The remote control comes with three accessories, which provide a triangulated location inside the home that automatically identifies where the remote points to, thanks to our patented system.

The Smart Remote embed motion tracking sensors and indoor positionning system with a 3 to 6 inch precision. We know precisely the indoor location of the remote in 3D and the relative location of the accessories. We combine the position of the remote and its orientation in 3D space to determine what the user is pointing to.

After the Smart Remote system recognizes the device you're aiming at, it changes the remote's touchscreen interface to match to that device and give you wireless control.

All this magic is done thanks to data fusion between inertial motion unit and locations.
It currently works with the Nest thermostat, Philips Hue lights and Sonos speakers, VLC player. Sevenhugs is opening up its API/SDK to give developers the opportunity to control any smart device.

Main interface to control devices is in Lua.

Our SDK offers 3 levels to developers:

• Level 1 : open API to control several classes of equipment
• Level 2 : SDK for creating basic use cases
• Level 3 : SDK for creating advanced use cases

Level 1 (fully available)

Developers can use this level through a PC simulator released on github : this is an Open API to control several classes of peripherals :

• Bulbs
• Music speakers
• Thermostat
• TV
• Etc

Level 2 (not fully available, you can build the front-end and explain what you would do with this level)

It will allow you to create & define new use cases and new screens.
• Typical example: point to the window and get weather information
• Developers can imagine new services by pointing to virtual zones

Level 3 (not fully available, you can build the front-end and explain what you would do with this level)

To create advanced use cases, developers will be able to:

-Register some callbacks, for example: subscribe to positions / orientations or specific events from 9-axis sensors and trigger specific actions/services
-Possibility to add more screen menus

For this level, we are very eager to provide our hardware to top notch developers and support them with the objective of flying a drone with our smart remote. The craziness of this scenario is to create a virtual cage that will define the limits of where the drone can fly! Then, even a 5 years old child will be able to fly a drone with no risk of crashing against the walls.

If you have new ideas, basic use cases that we don’t support yet or any relevant scenario with interaction with smart home hubs, Raspberry or Arduino, send us an e-mail at contact@sevenhugs.com

Access the Sevenhugs Smart Remote SDK here: https://github.com/sevenhugs/smart-remote-sdk

CODINGAME CHALLENGE

Each day, compete and solve complex programming challenges while playing on Codingame’s platform. The best coder will win the $300 prize!

Schedules

FRIDAY OPENING NIGHT - June 3rd

6pm Pizza and beers served!

6:15pm ubi i/o Opening

6:30pm Akeneo, OpenIO and Sevenhugs APIs presentations

7:00pm Q&A

7:20pm Reminder of the rules

7:30pm Codingame's presentation

7:40pm Clash of Codes with Codingame

8:00pm Let’s hack! Beginning of the hackathon - social time

JUNE 3RD - 9TH

The Agorize platform is available to submit your code during the whole week.

Each day we will send a notification to each hacker to compete on Codingame.

THURSDAY CLOSING NIGHT - June 9th

10:00 am Final Coding and Submission Deadline

6:00 pm Project presentations – Judging and voting begins

7:00 pm Panel deliberations / mingle and snacks for participants

8:00 pm Awards

9:00 pm Closing

Rules

There will be three tracks with a different API for each. Your team (1 to 5 people, everyone needs to subscribe to the event) must select and compete in one track only, there will be separate prizes for each track.

All code developed as part of the ubi i/o hackathon must be fresh. To keep things fair, all codes must be written during the length of the hackathon starting at 8:15pm on Friday. Other than that, almost anything goes and you can use any coding languages, open-source libraries, and APIs.

HACKATHON REQUIREMENTS

Each team is required to submit their project on Agorize no later than 2pm on Wednesday. On Thursday evening, accepted submissions will be given 2 minutes to pitch their functioning solution in front of the judges followed by a 1 minute Q&A session. Your presentation format is up to you, but it is recommended to share a very brief visual, e.g. PowerPoint or a video combined with a demo of the solution developed. We will provide you with projection equipment.

Hackers who can’t attend the closing event in San Francisco will not be eligible for the prizes.

WHO OWNS THE IP?

Akeneo

Participants will own the rights to their work. If the teams decide not to further develop the idea, Akeneo retains the right to develop a similar solution with different methods. Akeneo strongly encourages hackers to release their code under open source license (MIT or OSL v3).

OpenIO

Participants will own the rights to their work. If the teams decide not to further develop the idea, OpenIO retains the right to develop a similar solution with different methods. OpenIO strongly encourages hackers to release their code under open source license.

Sevenhugs

Participants will not own the rights to their work. Sevenhugs can decide to reuse your work to further develop the project.

PARTICIPATION AGREEMENT

There are participation agreements both for hackers and makers available on our website, you will be required to sign at the event. You can review the Participation Agreement here.

JUDGING CRITERIA

The ideas are judged based on 4 criteria from a panel of judges:

1. How innovative the app is

Includes the degree of innovation demonstrated using the API and the extent to which the API is key in the solution.

2. User experience and design

Includes how beautiful and elegant the solution is in terms of how it looks to the user and how easy it is to use.

3. How well it works

Includes the extent to which the solution does what it is supposed to do and how good the code is written in a performance point of view.

4. Hot factor - Potential

Includes how compelling the solution is and how likely people are to be excited about it.

Judges

Jérôme Louvel: founder, CTO and VP of Engineering of Restlet and an expert in web APIs and REST.

Reza Malekzadeh: US Marketing, OVH

François Baldassari: Software Engineer at Pebble

Thanks to our sponsor: