RESSOURCES

PITCH

Build the User Interface of the Android App that will hold the role of

• displaying the ultrasound image
• enabling the control of the ultrasound probe

I/O mode

• Input 

1. Functional MockUps that illustrate all the App cinematics
2. cut-out psd templates, with the assorted set of icons

• Output

1. Fully Integrated User INterface of the Android App

CONTEXT

The UX design of the Android Application is of critical interest, indeed there are a bunch of parameters that should be controllable by the medical operator. The latter is strongly constrained by the the fact

• there is a single available for the app, the other is holding the ultrasound probe
• the hand holding the probe is full of ultrasound gel, preventing him to click on the mobile device
• the hand holding the mobile device should control some examination parameters, such as gain, depth, frequently and in real time

This led a team of web designers, medical doctors, a few weeks ago, on 25.10.2016, to propose a serie of MockUps that you can find HERE.

Then, an echOpen workshop took place in Marrackech, Moroco, in the COP22 event, Africa4Tech, on 03.11.16 - 05.11.16, a team of developers made an incredible job in 2 hard-working days : they cut out the templates and produced a semi-native app, available HERE.

The challenge will be to produce an equivalent result at a native app level.

With the participation of :

And the support of :

ORGANIZATION

The Hackathon main info

Goals and objectives 

Fully Integrated User Interface of the Android App

Management team

• echOpen Paris - France

• Mehdi Benchoufi, nowami@echopen.org
• Olivier de Fresnoye, olivier@echopen.org
• Benoît Vincent, bvincent.perso@laposte.net 

• echOpen Morocco :

• SIKORO,Phaino

• Amine El Moutaouakil, devamine@gmail.com 
• Houssam Hamza, hamza@houssam.net 
• Mustapha Abdouss, mustapha.abdouss@gmail.com 
• Amine Khaddar, k.m.amine@gmail.com 

• Xhub

• Badr ELHOUARI badr.elhouari@gmail.com

• Fikra.ma

• Marouane El Moutaouakil  marouane@ons-maroc.com

• More to come !

DAY 1 (evening) : December the 16th 2016 - from 06.00 pm </timeout>

Introduction from 07.00 pm (Paris time) - 06.00 pm (Marrakech time)

• Presenting the echOpen project
• Presenting of participants + identification of skills
• explaining the dev challenge

• cut challenges in specific sub-challenges
• team management

• set as many teams as there are sub-challenges if possible +
• identify transversal skills that could refer globally

• presentation of the code format constraints

• brief tour of echOpen’s formating rules
• test driven if possible 

Setup from 08.00 pm (Paris time) - 07.00 pm (Marrakech time)

• installation

• presentation of the materials

• cut-out templates, native/semi-native app, VM
• + shared repo of open source libs and plug-ins
• GitHub : issues space + repos for PR

• presentation of the communication collaborative tools

• dedicated Slack channels (UI, shared process/code/libs, Q&A, bugs, random & helps)
• GitHub repo + issue tracking
• referees for each team in case of problem

• check of the connexion
• start coding either

• from scratch
• from semi-native app
• advanced configuration

• use of VM of team that want to code on the current android app

Launch 08.30 pm (Paris time) - 07.30 pm (Marrakech time) : Let’s code !! <code></code> ⇒ Hard Coding to </timeout>

Sanity Check : Who did what ? + and - & improvements

Beer Party when needed ;)

DAY 2 : December the 17th 2016 - from 09.00 am to </timeout>

Set Up ⇒ Synthesis of the precedent coding day, for insiders and new incomers

<code></code> ⇒ Hard Coding morning 09.00 am - 12.30am

Lunch time

<code></code> ⇒ Hard Coding afternoon 14.00 am  to </timeout>

Sanity Check

• Who did what ?
• + and - & improvements

Beer party when needed ;)

DAY 3 : December the 18th 2016 - to 5.00 pm

Set Up ⇒ Synthesis of the precedent coding day

<code></code> ⇒ Hard Coding day

Lunch time

<merge></merge> ⇒ GitHub PRs

Restitution ⇒ Merges of the Merges ;)

Logistic - Checklist

Before the D-Day

logistics matter

☐ Organize food and beverages  

☐ Confirm with eventual photographers, etc.

☐ Make a test scenario with your team and with printed badges, etc.

☐ Print the check sheet, badges, etc.

☐ Send a reminder to registered participants with all the information, including

how to find the place, parking, metro, how to sleep near by, etc.

☐ Send a last reminder to participants and a note to the organization team with each responsibilities

Communication matter

☐ Solution to register is created (MeetUp, Evenbrite, etc.)

☐ Publish the hackathon on various platform dedicated to this kind of events

☐ Start communication on social network

☐ Print posters to show up the way to the place. Including posters for toilets, wifi password, #tags of the event, etc.

Technical matter

☐ Check the audio materials

☐ Check the WIFI connection

☐ Skype SetUp for many teams communications

☐ Common Video Wall for the core multi-located teams to see and communicate

D-Day :

☐ Arrive early to setup register

☐ Team meeting with the program

☐ Welcome speech and organize a “safeplace” for the participant belogings

☐ Take pictures and share them on social network to animate the event.

After the D-Day

Send a thank message to participant with a review of the event, including results and pictures.

For more details, please see the following resources :

• Event Planning Guidelines
• Brigade Organizer’s Playbook