FlyWeb: Difference between revisions
(Fixed link to spec.) |
mNo edit summary |
||
| Line 23: | Line 23: | ||
FlyWeb is not just IoT. | FlyWeb is not just IoT. | ||
= | =Proposal= | ||
==Draft Specification== | |||
<big>[https://github.com/flyweb/spec Draft Specification Link]</big> | |||
=See Also= | |||
* [https://docs.google.com/document/d/1MoyseigM7iYSoQZ0PsnIyU6yE1GzwE7-ETCZOS1hmFw/edit User and Market Research]: Due to the confidential nature of the interviews, and our respect for our interviewees' privacy, we are restricting access to this information. | |||
==Demo Videos== | |||
* [https://youtu.be/j3E4dKNaQRM Teasers. We don't plan to build any of these anytime soon.] | |||
** [https://youtu.be/kq1ygsQzuO0 Developer commentary over this video.] | |||
* [https://youtu.be/g-zHE33xKng Early-stage browser casting demo.] | |||
==Strategy Essays== | |||
* [https://docs.google.com/document/d/1o3pY73CBiFSx7fNDwDfzJ1TggUIIa-RWBL4-eqpy_nE/edit 2015-05 Operational Overview] | |||
* [https://docs.google.com/document/d/1948ryrtM2_zCQKy7ADcnwoxcviTC4sOvCeCtJGcwDVU/edit 2015-07 In-depth Strategy Document] | |||
==Related Initiatives== | |||
* [https://github.com/google/physical-web Google's "Physical Web" Initiative] | |||
* [http://coap.technology/impls.html Constrained Application Model - Internet of Things] | |||
==Related APIs== | |||
* [http://www.w3.org/TR/presentation-api/ W3C Presentation API] | |||
* [https://blog.mozilla.org/blog/2015/05/14/first-panasonic-smart-tvs-powered-by-firefox-os-debut-worldwide/ Mozilla Smart TV's] | |||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1143996 KDDI Web-Cast] | |||
* [https://en.wikipedia.org/wiki/Discovery_and_Launch Discovery and Launch (DIAL)] | |||
=Communication= | |||
==Video Conferencing - Vidyo Room== | ==Video Conferencing - Vidyo Room== | ||
| Line 56: | Line 83: | ||
|} | |} | ||
==Project Management | ==Team== | ||
* [mailto:drs@mozilla.com Doug Sherk (:drs)] - product management | |||
* [mailto:kvijayan@mozilla.com Kannan Vijayan (:djvj)] - engineering | |||
* [mailto:jdarcangelo@mozilla.com Justin D'Arcangelo (:justindarc)] - engineering | |||
* [mailto:jonas@sicking.cc Jonas Sicking (:sicking)] - specifications | |||
* [mailto:nyee@mozilla.com Nicole Yee (:nicoleyee)] - project management | |||
=Project Management= | |||
<big>[https://trello.com/b/IlFy9m7y/flyweb Trello dashboard]</big> | <big>[https://trello.com/b/IlFy9m7y/flyweb Trello dashboard]</big> | ||
| Line 101: | Line 136: | ||
*Product Proposal | *Product Proposal | ||
*Use Case Doc | *Use Case Doc | ||
Revision as of 02:31, 14 August 2015
The web already powers the world's email, media, shopping, and more. Interacting with these things is a breeze because they all use the web. What if the electronics around us were the same?
Meet FlyWeb. FlyWeb is a very simple idea at its core. Instead of phones interacting only with the cloud, they can discover and interact with electronics around them that are running empty web clients, such as TV's, projectors, game consoles, etc. The electronics come to life when connected to phones. The key here is that either the phones serve web apps to these electronics, or the electronics serve web apps to the phones.
Why?
The connected devices market is ready to explode. As the market grows, much like the early internet, these devices are being segregated into walled gardens of one-off proprietary initiatives, such as AirPlay, the Google Cast API, etc. These solutions not only lock their users into specific vendor ecosystems -- to the benefit of those vendors and detriment of their users -- but also require significant investment to solve each use case.
Many of these connected devices initiatives have common underlying platform needs:
- to discover and connect devices together,
- enable bi-directional communication,
- allow arbitrary, but secure code execution on each side,
- and require knowledge of as few details of a device's peers as possible.
The web is the best platform for serving all of these needs. Indeed, it has been designed for them for over a decade.
What about IoT?
FlyWeb is not just IoT.
Proposal
Draft Specification
See Also
- User and Market Research: Due to the confidential nature of the interviews, and our respect for our interviewees' privacy, we are restricting access to this information.
Demo Videos
Strategy Essays
Related Initiatives
Related APIs
Communication
Video Conferencing - Vidyo Room
Quick link to join with the Vidyo app (prompts install if needed)
We have our own Vidyo room for meetings. Contributors and non-employees are welcome to attend all meetings. Here are the full details for joining:
| "FlyWeb" Vidyo Room |
|---|
|
Hello, |
Team
- Doug Sherk (:drs) - product management
- Kannan Vijayan (:djvj) - engineering
- Justin D'Arcangelo (:justindarc) - engineering
- Jonas Sicking (:sicking) - specifications
- Nicole Yee (:nicoleyee) - project management
Project Management
We use Trello for project management. All ongoing tasks are listed there.
Meetings
Anyone is welcome to attend FlyWeb meetings.
Calendar
The FlyWeb team has a public calendar with every team meeting.
Instructions for Adding to your Calendar
- Open the calendar.
- Click on the "+ Google Calendar" button in the very bottom right of your screen.
You can also use the XML and ICS methods, but these are not recommended.
Note: The "Find a Time" feature will not work for other people if you import this calendar. As a consequence, others will not see that you are unavailable when attending a FlyWeb meeting. We suggest either accepting this, or adding the meetings to your main calendar as well.
Standups
We have weekly standups on Mondays at 10 am PT (17:00 UTC). These happen in the FlyWeb Vidyo room.
All meeting minutes
Material Compilation Meeting:
August 12, 2015 @ 12PM PST
Objective: Discuss and compile current material supporting FlyWeb
Attendees: drs, nicoleyee, djvj, tedders1,justindarc
[Notes]
Compiled material: (Referencing Flyweb Folder)
- API Draft
- Architecture Doc
- Proposal
- Wiki
- Product Proposal
- Use Case Doc