Connected Devices Weekly Update/2016-05-03

• Team meetup in Berlin on 5/16 - 5/20 to focus on user testing and formulating hypothesis
• The entire team is going to be engaged in user testing to ensure that the full scope of users is understood
• Currently working on connecting with Friends and Family to discuss voice activation needs

Market Segment

• Looked into three potential segments: busy family, kids (at home/at school), elderly. Chose the busy family segment.

Hypothesis (still being refined)

• We believe that by offering a smart virtual assistant to busy families, we will reduce the time they spend on day to day tasks by 20% and increase the amount of time the families spend with each other by 20%.

Research

• Need to research what we perceive as the busy family segment, determine what their needs are and if there’s an intersection of that and what we can offer.
• Developing a framework or script for conducting the consumer interviews to be tested first before members of the team conduct interviews.
• Exploring the possibility of using DScout for our research study as well as a guerrilla style friends/family study
• Sampling, interviewing, and analysis tips were shared with the team
• Want to invest in brainstorming and research process over the next couple weeks

Differentiators

• Have developed a list of how we might differentiate ourselves from the competition

Demos

• Showed phase 1 demo to leadership team and received good feedback
• Currently working on video for London demo
• Worked with the Mountain View WPR team to use the Battlestar Galactica conference room as a demo/showcase room for Link devices

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

• We received positive feedback at our second check in last Friday (Slides and video recording)
• To test our current hypothesis, we've started to design our next round of research.
  • The test will include a functional research prototype that we'll share with a small group of 12-15 year-old girls.
  • We're investigating the use of the Particle "Photon" and "Internet Button" products as a quick start way to get a tactile, connected device into study participants hands. More details here.
• We finalized our Research Findings from our first user study.

• Finished Sprint 1: we already have a very basic client for Android and iOS to discover physical webs. This will be useful for prototyping and hypothesis validation.
  • Some demo videos for iOS and Android recorded during our Sprint 1 Demo and Retrospective
• The goals for sprint 2:
  • Research: Work in the assumptions/hypotheses document to be reviewed.
  • Be able to have downloadable builds (not finished in sprint 1)
    • Some legal issues have been raised about the distribution of iOS builds via Testflight and also with the Apple Developer Program account used that need to be clarified.
  • Polish the clients as many tasks/issues have been detected when they were developed during last sprint.
    • It would be also great start trying with URLs and start setting common use cases for the London office (specially for visitors) and London All Hands.
• Beacons research finished and now evaluating some providers to do a purchase.

• General updates
  • Technical review (https://goo.gl/lUf8qr) with Dylan on 4/28
• What’s done
  • 1st deployment success in a school
    • http://blog.sensorweb.io/2016/04/26/our-first-user-ping-sing-elementary-school/
• What’s next
  • portal refinement (adding intro video, etc etc)
  • Takeouts from legal review (map, SSO)
  • maker faire taipei on 5/7, 5/8 (https://goo.gl/irPKgA)
  • keep on deploying to schools.
• Upcoming Milestone:
  • Planned second PIB update on 5/4
  • London ww: hackathon (in planning), open session (in planning)

• Porting FirefoxOS Meeting merged with Weekly B2G Meeting
• Planning for meet up in London

• After studying several third party the team decided to go for Google Analytics.
  • It fits our needs both in terms of metric collection and visualization
  • GA has been already vetted in Mozilla and we are already paying for a premium service
  • Implementing GA will be faster and less effort than adapting the Mozilla telemetry pipeline for use with CD projects
• We are working in three major activities:
  • Implementing a library for Rust and JS that simplifies the adoption of Google Analytics by the trains
  • Documenting the parameters that can be used for collection of events
  • Evaluating reporting/visualization tools to ensure that metric data can be easily analyzed by the trains
• The target of this is ensuring all the trains send information in a consistent way and dashboards/reporting are consistent cross-train.

• Technical Research
• Looking at different ways to work moving forward
• Working on formulating hypothesis to prove
• Will be working with the different teams to move the hypothesis forward
• Market Research
• Continuing deep dive into conversational UI and digital assistants
• Getting access to consumer insights database from Forrester - Forrester Technographics
• User Research
• First deep dive into user research will be in the Vaani team
• working with the team on researching the product with everyone's involvement
• setting up workshops for the meetup in Berlin
• Setting up a workshop in London for the CD Team (What do you do after your train has been chosen?)

• 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.

• Smartphone Code Transition Wiki
• Working on removal of MobileID, Engineering Mode, and Apps APIs
• Continuing to work on getting homescreen and dialer working as chrome. The homescreen is now showing pinned sites on boot.
• We have a more solid plan for our build and test infrastructure. Merging back to master/m-c is coming soon, probably not this week but we are getting closer
• Working to get Gaia integration test suite (Gij) green. This is progressing along with the app:// to chrome:// conversion. We will not attempt to port the existing Gaia unit tests (Gu) during the refactor. We will rely on community to write new unit tests, likely mochitest-plain.

• B2G OS Transition Wiki
• Code contribution needs (more) experienced contributors. People mostly busy building and flashing now. 6 volunteers for code mentoring sessions to be organized soon.
• Future of infrastructure still in discussion. Test/Build infra at Mozilla could be available for a few more months. Volunteer contributors encouraged to have their own build infra for smartphone devices (already the case for ZTE Open C Fr).
• Documentation working group is active, working on restructuring the MDN doc. Permission to edit some parts of MDN might be a blocker here.
• Governance model decided for the module ownership system. Non-technical modules will be created to match the working groups. To be re discussed on week 20.
• Communication group to release a call for contribution on Tuesday the 3rd.
• Discourse category and Telegram group show an increasing activity over the past week.
• More information can be found at B2G Transition Working Groups

• Bulleted list item
• Bulleted list item

• Bulleted list item
• Bulleted list item

• Bulleted list item
• Bulleted list item