21 thoughts on “Google I/O 2015 – The next generation mobile web

  1. the way these presenters are talking reminds me of how people suck at practice presentations they make you do in job training

  2. A remotely relevant observation – my G+ app (native) uses 1GB+ phone storage and it only shows about 10-15 posts in my stream with no photos when I am in Airplane Mode. I always wonder why. 😉

  3. Next generation mobile web (notes)
    =================

    we will talk about 4 forces that are there now (or almost)  // ended up talking about three. hmm.

      – In the 90's is was easy to put yourself up on the web and both presenters made a niche-fansites when they were 12. So did you. 
      – E-comerce is big. Lots of trillions of USD every year. Another reason why to love web.

    Mobile was fundamental shift from desktop:
      – there are performance expectations (feeling responsive, 60fps smooth scrolling)
      – power limitations (battery holds limited amount of charge)
      – push notifications

    Web is huge, strong, still growing
      – Every week many millions of people use Chrome Dev tools, this number is growing.
      – Web (can) has reach, performance, engagement:

    Reach
    =====

      – Browsers are everywhere
      – Web content is easilly reached (through links, even between websites and search)
         – Imagine Dragons: frictionlessly jumped through 7 websites during a shotr demo

      – Average person uses 12 to 20 apps per Month
      – Average Chrome for Android user visits over 100 websites
      – 85% of US retailers mobile traffic (accounting for 90% revenue) is through web, not apps

      – Clicking a link is a noncommiting and safe action (compared to installing an App)

    Performance
    ========

      – Page load time: good tools, good understanding
      – RAIL, be performant enough so that the user does not feel she is waiting
         –  ….
         – this part actually worth watching, at 11:25
      – QUICK, Service Worker, minimize time to first (partial) render
      – Chrome does a lot of things (slide at 14:15) to make pages faster
         – one example: prioritizing scrolling over everything else
         – Canary behind a flag: FIlm strip in Dev Tools, shows render progression while loading
         – automated assistants in Dev Tools, give helpful tips what to change

    Engagement
    ========

    Native apps have access to Android/iOS APIs, like camera, storage, GPS location
    Web apps cannot, just clicking a link site should not allow it to
      – take photos, run background threads,
      – make background HTTP requests (say visiting embarassing site and they you transition from home to corporate network)

    Solutions
      – progressive permission asking when the need arises

      – Add to homescreen
        – reminds people to jump there when they have a little bit of time on their hands
        – site has to be offline-capable
           – appcache was declarative, sometimes hard to declare what you exatly need
           – service worker, imperative JS, client proxy between browser and server
              – this years IO app uses this
              – there is easy to use gulp plugin swprecache that caches all requests
              – one service worker can handle multiple tabs
              – service worker can run without a tab in front, reacting to
                   – network events, other types of events, used for Push notifications
        – Chrome will allow requesting on pages the user engages with enough
        – question at the end: Do mobile users use homescreen?
            – answer, they do, we have numbers, we cannot give them to you now

        – Push notifications
            – people open apps for a reason: in a response to notifications
                – Guardian, 40% article views from push notifications
            – don't make people refresh to engage
                – instead give people button to be notified to events on what they care about
            – shows on Android Wear as well
            – works on Chrome, other browsers generally onboard with this
            – progressively enhances UX (if available)

  4. I especially liked the push notifications part. When I first heard about web-based push notifications, I wasn't sure what I could do with it. Now I'm excited to play around with them.

  5. A most refreshing and awe inspiring double act talk from @Elisabeth Morant & @Alex Komoroske with perfect timing – learned loads from this, being entertained was the added bonus

  6. website can send push notifications to phone through chrome browser.. just click allow this site send msg..

Leave a Reply

Your email address will not be published. Required fields are marked *

Back To Top