Connected Devices Weekly Update/2016-05-17

• Day 1 of the Vaani Meetup complete!
• What are we working on this week?
  • Interviewing users (user testing)
  • Structuring Observations
  • Using data to form insights
  • Prioritization of tasks
  • Success Metrics
  • Working in Lean

• User Study and Interviews focused on Busy families
  • Worked on interview guidelines, and questions with the help of Mihaela
  • Team members reached out to nearly 30 friends and families across various cities in US, CA, and EU to schedule interviews
  • Planning to wrap up the user study by May 17th and synthesize the results by May 20th.
• Investigating 3rd party Voice solutions for next phase of Link (time-boxed to wrap up by end of next week)

• 2.6 milestones:
  • 4/27 branched
  • 7/15 FC

Hypotheses

• Creating an ambient method of communicating for 12 to 15 year old girls will create fewer interruptions that distract them from being in the moment at home and at school and improve their personal connections.

Research update

• Yesterday we had our third check in, slides and video video recording are also available in our wiki.
• The team continues prototyping and preparing for our upcoming user research study that starts on May 25th (to May 29th)
  • Wifi setup on the device using soft access point to select SSID and enter credentials
  • Click, double-click and long-click actions hooked up to publish to device pair and implemented LED animations on receipt of each of click messages
  • Logging actions per device-pair to Google Sheets via webhook & Zapier
  • Started modelling the enclosure for the prototype, false-start on the 3d printer which was DOA. A replacement was received so we can start printing and iterating through this week.
  • Working with legal team on the details for our consent forms and compatibility of 3rd party service's privacy policies (already available)
  • Last Friday an email was sent to MTV Mozillians for recruiting
  • We need to continue working in the logistics around the user research: interview guide, prototypes set up, diaries, instructions for the participants, support during the study...

Hypotheses

• We believe that broadcasting professional content (e.g. professional websites, contact info, twitter, etc) for conference presenters will help presenters promote themselves more easily than current methods

Research

• Target audience: Presenters (Mix of tech and non-tech conferences, Mix of males and females, Mix of ages)
• Interview guide ready
• Interviews are planned to be finished by May 27th

Development

• Sprint 2 finished. Some demos videos have been recorded to show the progress of the project:
  • Magnet and Sched integration
  • New visual features: Custom web views and a feature to provide the user the option to get rid of one of the tiles or cards.
• Sprint 3 started this week, goals apart of doing interviews and preparing London video:
  • Stabilization of the app to avoid server to explode if it's used by many people.
  • Sched adaptor: regression test, report and fix bugs.

Other:

• After updating github project and github wiki in last Sprint we had our first two contributors!
• First project Magnet check in scheduled on June 2nd

• What’s done
  • Widget visual design: http://bugzil.la/1271540 - Visual design for the Web widget
  • PM2.5 widget: http://sensorweb.io/sensor.html?id=B1giofox
• What’s next
  • Deliver Bug 1271206 (SensorWeb Q2 goals)
  • keep on deploying to schools. (Fix the WiFi connectivity issue in Da Quan elementary school)
  • London ww preparation
• Upcoming Milestone:
  • Sprint demo this week (May/20)
  • London ww: hackathon (in planning), open session (in planning)

• Build for Fairphone 2 seems to be almost ready (taken on by a community member)
  • build issue: https://discourse.mozilla-community.org/t/fairphone-2-build/8641/
• B2G installer add-on will be signed ASAP
  • https://bugzilla.mozilla.org/show_bug.cgi?id=1265385
• Meeting in London: Porting B2G: Where to next
  • Hosting with Valentin and it is mandatory for the porting team to attend and open to anyone who is interested (especially community members attending)
  • Get together and get some ideas for our roadmap
  • Wednesday June 15, 2016 13:00 - 14:00
  • Great Western II Paddington Hotel
  • Please add it to your sched if you are interested :)

• Sprint 4 finished last week, the goal was sending data end to end through Google Analytics.
• All the task were done, and the team was able not only to implement a library for Rust and JS that simplifies the adoption of Google Analytics by the trains, they were also completed the Java-Rust bridge to enable metrics for Vaani/OpenHab projects
• Now we need feedback from the trains to integrate Metrics and to be able to determine following tasks/steps in the library.
  • Magnet has included metrics tasks in this sprint.

• Currently working on bringing the research teams together
  • Completed the research team kickoff meeting with all teams attending
    • Research teams next steps
• Questions to Answer
• What are the goals of the research team for both general research as well as research on specific trains?
  • Will be looking at ideas in the pipeline to see what their validity is
  • Have 2 different groups
    • 1 team looks at the larger picture and where opportunities are
    • 1 team looks at the ideas coming through the pipeline and will validate based on market, user and technical research

• Smartphone Commercial Transition Wiki
• Plan to continue support thru Q1 2018. Have some logistics to resolve for the period from Jan 1 2017 to March 31 2018. Will continue to keep an eye on that.
• Update on path forward for OWDCRB expected May 19, will provide a read-out next week.

• Smartphone Code Transition Wiki
• Homescreen is now mostly working, working on a way to populate default pinned sites
• Biggest pieces remaining are getting the dialer working and removing the rest of the Apps API
• Work continues to get the automated tests passing so that we can merge the transition code branches back to master/central.

• B2G OS Transition Wiki
• Mozilla to give the community access to TaskCluster
• More technical contributors are joining, but as of now, there are still few actual contributions to the code
• Call for contribution published, translation on going