platform • Service workers • Push Notifications • App Manifest + related features 17:45 - 17:55 Break 17:55-18:30 • WebRTC • Microsoft Edge 18:30 - 19:00 • Food/Dinner 19:00 - 20:00 • Physical Web • The headless web • The web in a native world • Future challenges
requests from other origins • Client-side compiling and dependency management of CoffeeScript, less, CJS/AMD modules, etc. for dev purposes • Hooks for background services • Custom templating based on certain URL patterns • Performance enhancements, for example pre-fetching resources that the user is likely to need in the near future, such as the new few pictures in a photo album.
file ◦ The manifest defines how your app appears on the user’s system and how it should be launched - and you are required to have a `short_name` and a `144x144` png icon • You have a service worker registered on your site. We recommend a simple custom offline pageservice worker • Your site is served over HTTPS (you need a service worker after all) • The user has visited your site twice over two separate days during the course of two weeks.
streaming media initialization parameters • STUN - Session Traversal Utilities for NAT - Enables announcing your public IP addrreess during the negotiation phase of a session • TURN - Traversal Using Relays around NAT - Relays all media via a TURN server that is visible to all parties in a session • ICE - Interactive Connectivity Establishment - Decide the best solution connect (direct, STUN or TURN) Core protocols
• Connectivity independent: Progressively-enhanced with Service Workers to let them work offline • App-like-interactions: Adopt a Shell + Content application model to create appy navigations & interactions • Fresh: Transparently always up-to-date thanks to the Service Worker update process • Safe: Served via TLS (a Service Worker requirement) to prevent snooping • Discoverable: Are identifiable as “applications” thanks to W3C Manifests and Service Worker registration scope allowing search engines to find them • Re-engageable: Can access the re-engagement UIs of the OS; e.g. Push Notifications • Installable: to the home screen through browser-provided prompts, allowing users to “keep” apps they find most useful without the hassle of an app store • Linkable: meaning they’re zero-friction, zero-install, and easy to share. The social power of URLs matters.
for building UI’s so that you can render native components using JS as the runtime. • A Platform that run’s everywhere. • Optimized to run natively on the platform where the user is. • If you are Facebook, you now have an app platform without app stores. Facebook React as a Trojan Horse Paul Kinlan, Google