Successfully reported this slideshow.
Your SlideShare is downloading. ×

The web - What it has, what it lacks and where it must go - Bulgaria Web Summit, February 2016

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad

Check these out next

1 of 103 Ad
Advertisement

More Related Content

Slideshows for you (20)

Similar to The web - What it has, what it lacks and where it must go - Bulgaria Web Summit, February 2016 (20)

Advertisement

More from Robert Nyman (20)

Recently uploaded (20)

Advertisement

The web - What it has, what it lacks and where it must go - Bulgaria Web Summit, February 2016

  1. The Web - What it Has, What it Lacks 
 and Where it Must Go @robertnyman
  2. 2010
  3. 2010
  4. 2010
  5. Party like it's 2010
  6. Our line of work
  7. My role at Google
  8. My role at Google https://developers.google.com/android/ https://developers.google.com/ios/ https://developers.google.com/web/
  9. My role at Google
  10. My role at Google - https://medium.com/latest-from-google
  11. My role at Google - understanding trends
  12. The web as of today The web vs. native Tools & resources from Google SLICE Why do developers need a native app? Monetization Future of the web
  13. The web as of today
  14. The web as of today
  15. The web as of today
  16. The web as of today One billion active users
  17. The web as of today
  18. The web as of today
  19. The web as of today Morgan Stanley: the web is winning
  20. The web vs. native
  21. The web vs. native Visitor traffic to top companies/services
  22. The web vs. native comScore: 87% of time on mobile spent in apps Native is winning
  23. The web vs. native 10% of time on mobile spent in the browser
  24. The web vs. native 10% of time on mobile spent in the browser
  25. The web vs. native ?
  26. The web vs. native Messaging, Social > Gaming
  27. The web vs. native Facebook One billion daily users, where 844 million daily users are on mobile
  28. The web vs. native …and these 7 products also have more than one billion users:
  29. The web vs. native
  30. The web vs. native
  31. Tools & measures from Google
  32. App install interstitials being non-mobile friendly
  33. App install interstitials being non-mobile friendly
  34. Mobile-Friendly Test
  35. Mobile-Friendly Test https://www.google.com/webmasters/tools/mobile-friendly/
  36. Communications & the web
  37. Communications & the web
  38. Communications & the web https://hangouts.google.com/
  39. Communications & the web WebRTC Desktop: Microsoft Edge Google Chrome Mozilla Firefox Opera Android: Google Chrome Mozilla Firefox Opera Mobile Chrome OS Firefox OS
  40. Chrome DevTools
  41. Chrome DevTools https://developers.google.com/web/tools/chrome-devtools/
  42. Web Fundamentals
  43. Web Fundamentals https://developers.google.com/web/fundamentals/
  44. Chrome Custom Tabs
  45. Chrome Custom Tabs https://developer.chrome.com/multidevice/android/customtabs
  46. SLICE
  47. Google influencers Paul Kinlan Jake Archibald Alex Russell Paul Lewis + many more
  48. The web, moving forward Build instantly engaging sites and apps without the need for a mandatory app download
  49. SLICE Secure
  50. SLICE Linkable
  51. SLICE Indexable
  52. SLICE Composable
  53. SLICE Ephemeral
  54. Why do developers need a native app?
  55. Performance Sensors OS-specific features Offline access Periodic background processing Notifications Why do developers need a native app? From Brian Kennan
  56. Performance Sensors OS-specific features Offline access Periodic background processing Notifications Why do developers need a native app? From Brian Kennan
  57. Initiatives to address this New web features
  58. Offline access => Service Workers Service Workers
  59. It's a JavaScript Worker, so it can't access the DOM directly. Instead responds to postMessages Service worker is a programmable network proxy It will be terminated when not in use, and restarted when it's next needed Makes extensive use of Promises Service Workers
  60. HTTPS is Needed Service Workers
  61. Register and Installing a Service Worker if ('serviceWorker' in navigator) {
 navigator.serviceWorker.register('/sw.js').then(function(registration) {
 // Registration was successful
 console.log('ServiceWorker registration successful with scope: ', registration.scope);
 }).catch(function(err) {
 // registration failed :(
 console.log('ServiceWorker registration failed: ', err);
 });
 }
  62. chrome://inspect/#service-workers chrome://serviceworker-internals/ Service Workers
  63. // The files we want to cache
 var urlsToCache = [
 '/',
 '/styles/main.css',
 '/script/main.js'
 ];
 
 // Set the callback for the install step
 self.addEventListener('install', function(event) {
 // Perform install steps
 }); Installing a Service Worker
  64. Inside our install callback: 1. Open a cache 2. Cache our files 3. Confirm whether all the required assets are cached or not Installing a Service Worker
  65. Install callback var CACHE_NAME = 'my-site-cache-v1';
 var urlsToCache = [
 '/',
 '/styles/main.css',
 '/script/main.js'
 ];
 
 self.addEventListener('install', function(event) {
 // Perform install steps
 event.waitUntil(
 caches.open(CACHE_NAME)
 .then(function(cache) {
 console.log('Opened cache');
 return cache.addAll(urlsToCache);
 })
 );
 });
  66. self.addEventListener('fetch', function(event) {
 event.respondWith(
 caches.match(event.request)
 .then(function(response) {
 // Cache hit - return response
 if (response) {
 return response;
 }
 
 return fetch(event.request);
 }
 )
 );
 }); Caching and Returning Requests
  67. Updating a Service Worker
  68. 1. Update your service worker JavaScript file. 2. Your new service worker will be started and the install event will be fired. 3. New Service Worker will enter a "waiting" state 4. When open pages are closed, the old Service Worker will be killed - new service worker will take control. 5. Once new Service Worker takes control, its activate event will be fired. Updating a Service Worker
  69. Instant Loading Web Apps with An Application Shell Architecture Application Shell
  70. Periodic background processing => Background Sync
  71. Background Sync
  72. Background Sync Chrome Dev for Android or Chrome Canary for desktop chrome://flags/#enable-experimental-web-platform-features Restart the browser
  73. Notifications => Push notifications
  74. Push notifications
  75. // Are Notifications supported in the service worker? 
 if (!('showNotification' in ServiceWorkerRegistration.prototype)) { 
 console.warn('Notifications aren't supported.'); 
 return; 
 } Push notifications
  76. // Check the current Notification permission. 
 // If its denied, it's a permanent block until the 
 // user changes the permission 
 if (Notification.permission === 'denied') { 
 console.warn('The user has blocked notifications.'); 
 return; 
 } Push notifications
  77. // Check if push messaging is supported 
 if (!('PushManager' in window)) { 
 console.warn('Push messaging isn't supported.'); 
 return; 
 } Push notifications
  78. // We need the service worker registration to check for a subscription 
 navigator.serviceWorker.ready.then(function(serviceWorkerRegistration) { 
 // Do we already have a push message subscription? 
 serviceWorkerRegistration.pushManager.getSubscription() 
 .then(function(subscription) { 
 // Enable any UI which subscribes / unsubscribes from 
 // push messages. 
 var pushButton = document.querySelector('.js-push-button'); 
 pushButton.disabled = false;
 
 if (!subscription) { 
 // We aren't subscribed to push, so set UI 
 // to allow the user to enable push 
 return; 
 }
 
 // Keep your server in sync with the latest subscriptionId
 sendSubscriptionToServer(subscription);
 
 // Set your UI to show they have subscribed for 
 // push messages 
 pushButton.textContent = 'Disable Push Messages'; 
 isPushEnabled = true; 
 }) 
 .catch(function(err) { 
 console.warn('Error during getSubscription()', err); 
 }); 
 }); Push notifications
  79. { 
 "name": "Push Demo", 
 "short_name": "Push Demo", 
 "icons": [{ 
 "src": "images/icon-192x192.png", 
 "sizes": "192x192",
 "type": "image/png" 
 }], 
 "start_url": "/index.html?homescreen=1", 
 "display": "standalone"
 } <link rel="manifest" href="manifest.json"> Push notifications
  80. Add to Homescreen
  81. Cache management & whitelistsApp Install Banners
  82. App Install Banners prerequisites You have a web app manifest file You have a service worker registered on your site. We recommend a simple custom offline page service 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.
  83. All this leads to progressive apps
  84. Progressive Apps These apps aren’t packaged and deployed through stores, they’re just websites that took all the right vitamins. They keep the web’s ask-when-you-need-it permission model and add in new capabilities like being top-level in your task switcher, on your home screen, and in your notification tray - Alex Russell
  85. Progressive Apps http://bit.ly/progressive-web-apps
  86. Web Updates - http://bit.ly/web-updates
  87. Monetization
  88. Future of the web
  89. Future of the web Why the web?
  90. Future of the web Native platforms needs to be matched and surpassed
  91. Future of the web Getting people back to using URLs, sharing things online and making it accessible across all platforms
  92. Future of the web Go simple
  93. Future of the web Go simple Right now the onboarding process for a (front- end) web developer is much harder than it was before
  94. Future of the web Go simple We've gone from HTML, CSS and JavaScript to incredibly complex solutions, build scripts & workflows
  95. Future of the web Spread the word about what the web can do
  96. Future of the web Longevity of the web Where stuff being built will still work 10 years down the line
  97. Future of the web
  98. Help keep the diversity of the web
  99. Robert Nyman robertnyman.com nyman@google.com Google @robertnyman

×