670
edits
Connected Devices Weekly Update/2017-01-26: Difference between revisions
Connected Devices Weekly Update/2017-01-26 (view source)
Revision as of 18:53, 26 January 2017
, 26 January 2017revised SDK summary
(Updated color status for SensorWeb, Lighthouse) |
(revised SDK summary) |
||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 12: | Line 12: | ||
! style="background:#FF2800;" | Delayed | ! style="background:#FF2800;" | Delayed | ||
| | | | ||
* | '''Revised SensorWeb Timeline''' | ||
* | |||
[[File:SensorWeb Timeline Jan 26.png|600px]] | |||
* Building test units of the SensorWeb device and the manufacture of those devices have been delayed, pending a final budget decision. The overall project timeline has been adjusted accordingly. At this point, we're running about 5 weeks behind the original schedule for the manufacture of the devices. | |||
'''Beta Service and Developer Offering''' | |||
* Team is working on the deliverables for the beta service and developer offering. | |||
* Sprint 6, ending January 26th, has been focused on Favorites and the behavior when launching the the app (mobile and website) and authentication. A lot of work has been completed on the user interactions and wireframes have been updated. | |||
[[File:Save favorite.png|600px]] | |||
* Upcoming sprints will focus on developer access. | |||
'''SensorWeb SDK''' | |||
* A SensorThings SDK for developers consisting of Web Service endpoints, documentation for SensorWeb, example code, and release notes for developer who wish to have early access to SensorWeb web services. Additionally, we will add access control to our SensorWeb Cloud service through client and user authentication. We will have this available as a closed beta to developers who wish to have early access. Included in this release is API authentication. | |||
* This release will be an “early release”, not intended for large scale commercial deployment. It sets a foundation for further development. The objectives are: | |||
** Engage developers in the community to use the SensorWeb platform | |||
** Test our SensorWeb API for usability, reliability and completeness for both custom-defined devices and our devices and solicit feedback via closed beta for the SDK | |||
* Demonstrate an early consumer-facing service offering utilizing PM2.5, temperature and humidity data in a visualization | |||
* Give developers (contributors) the ability to add /remove/modify devices that they own | |||
* Enable developers to add devices compatible with our SensorWeb Device | |||
'''SensorWeb Device''' | |||
* As a reminder, the SensorWeb device has not yet been manufactured. About 25 early boards have been produced and distributed to internal members of the SensorWeb project team for testing and development purposes. | |||
[[File:SensorWeb Develop Board V1.3.png|500px]] | |||
|- | |- | ||
| Platform and Tools | | Platform and Tools | ||
| Line 20: | Line 38: | ||
! style="background:#00EC00;" | On Target | ! style="background:#00EC00;" | On Target | ||
| | | | ||
* | * Gateway Spike | ||
* | ** Put together an early draft of an [https://docs.google.com/a/mozilla.com/document/d/1Vby2UtY-WqGh_3AcqqZSRgyqSW6drFiISpGC9taE1b8/edit?usp=sharing architecture proposal] for the gateway implementation | ||
** Discussing technical details of Gateway implementation | |||
** Working on ZigBee adapter implementation for Q1 gateway spike | |||
** Experimenting with ZeroMQ for Q1 gateway spike - End to end sample with a broker architecture | |||
** Created an early draft of a [https://docs.google.com/a/mozilla.com/document/d/1Cr4IGTdzwWN_UrMjwemTwXz3VmJD4X57ljZh2NaaADg/edit?usp=sharing Web Thing API], focused on the initial simple use case for the Q1 gateway spike (turn a smart plug on and off). | |||
* Secure Communication Spike | |||
** Deep dive into identified approaches | |||
** Brain storming on each approach with Mozilla security team | |||
* Meeting with few MoFo/GigCity funded startups to discuss [https://drive.google.com/open?id=0B5Nzo4etQuvVRFYxSFN2c1N1cEd5R0lINTY3T0RHWlJoRk9v CD Whitepaper] | |||
|- | |- | ||
| [[Connected_Devices/Projects/Project_Magnet|Project Magnet]] | | [[Connected_Devices/Projects/Project_Magnet|Project Magnet]] | ||
| Line 50: | Line 80: | ||
! style="background:#FF2800;" | Delayed | ! style="background:#FF2800;" | Delayed | ||
| | | | ||
* | '''Resourcing''' | ||
* | * Pending resource funding decisions are a risk the overall schedule. QA assistance and a visual designer are needed to finish up the app. | ||
* Backup plan is for project team members to do QA testing. Team has also discussed using community help for QA and engagement of members of the accessibility community. | |||
* Team will also reach out to visual designers within Mozilla who are outside of CD. | |||
* Also wanted to start some work on the hardware side, but need industrial design help for that. This is currently on hold, pending the funding decision. We won’t be able to make our Q1 goal around ID. Waiting on final budget decisions before doing any more work on the device. | |||
'''App Progress''' | |||
* Planning and design work was conducted this week for the app. | |||
* Focus has been on diagramming the desired user interactions, with lots of collaboration within the team taking place. | |||
[[File:Taking a Photo.png|800px]] | |||
[[File:Camera access request.png|300px]] | |||
* We want to provide a good user experience, especially because our users are visually impaired. We want to get the user experience right. There will be a lot of testing in this area. | |||
* Also want to achieve speed and accuracy in matching. Low error rate is important. | |||
* Front-end work as well as work on image capture and matching is progressing in Sprint 2, which ends Jan 31. | |||
* Team is discussing the best way to conduct testing. TestFlight is still being considered, but the team is also discussing the pre-loading of the app. on smartphones and then distributing those for testing. | |||
* Team has held marketing discussions around the best ways to target users and to provide information about the app and what it does. | |||
|- | |- | ||
| [[Connected_Devices/Participation|Participation Update]] | | [[Connected_Devices/Participation|Participation Update]] | ||
| Line 58: | Line 101: | ||
! style="background:#00EC00;" | On Target | ! style="background:#00EC00;" | On Target | ||
| | | | ||
* | * | ||
* | * | ||
|- | |- | ||
| Market Developments Update | | Market Developments Update | ||
| Line 66: | Line 109: | ||
! | ! | ||
| | | | ||
* | * | ||
* | * | ||
|- | |- | ||
| Other Announcements / Questions | | Other Announcements / Questions | ||