Building Successful Websites: Case Studies for Mature and Emerging Markets (Google I/O ’19)

Building Successful Websites: Case Studies for Mature and Emerging Markets (Google I/O ’19)

Show Video

Good. Afternoon thank you all for being here you're almost through day one a file so we really really glad that you're here i mantle. I work on the product partnerships, team here at Google, and I, support Chrome, our. Goal is to help developers, like all of you build great websites so. You can be successful, and make, those experiences. For everyone everywhere. While. Framing the context, of this talk I was, naturally, inclined, towards, anchoring, it on the core benefits of the web it's, massive, reach, frictionless. Access, and the. Fact that a website just works no, matter where you are you. Could be on the fastest, internet connection, or you, could be busy playing the often Dino game it. Just works and yes. This, is what has kept the, foundation, of the web solid. And steady for over 30 years but. There's, so much path prating development, that's happened, in the far past few years with, service workers and progressive, web apps or pwace, things. Are changing, just. By making small changes developers. Across the world are seeing, that they're delighting, their users they're finding new ones and they're. Ultimately seeing, great results. Here. Are some examples, of this. Tokopedia. The. Biggest marketplace, platform, in indonesia it's. Seeing that by using a combination of amp and PWA, they're, seeing five times higher conversions, on their website, and. It's like me you enjoy listening to music you. Can do that on Spotify, on a Chromebook, on their progressive web app on desktop, and they're, seeing higher engagements. From these installed pwace. In. Brazil, Tara ortega a new, pub news publisher, has seen that users are sharing, more articles, after they implemented, the web share API and. Buco, of boosha boosha I. Might have missed, that up and I apologize. To anybody who speaks German but a leading, German works, in media. Has, a top-performing PWA. And they, use trusted, web activities, as, a building, block for their priests or experience. These. Core values of, universal, reach and reliability. When, you combine them with the new super pass they. Can help you solve real world problems for, all your users. Let's. Walk you through my daily routine as an example, so. The, first thing I do when I wake up even before the caffeine kicks in I check. My email messages. What's, going on in the world what's happening back home in India. And. Sometime during the day I hit my lord lowest productivity, R and after. A heavy lunch they go onto social media and I ask some very profound, questions. That's. Still bothering me by the way and. Then. Once I go home I obviously, sit on my couch and I'm binge watching the latest episodes, assumption. That's. A crazy routine, it goes against everything they tell you about the true well-being so please remember to hit pause every, once in a while. Here's. A quote from someone who, lives and breathes the Internet, the. Point is I'm, in this business when. I wear my user hat on as a user all, I want, is a fast, seamless. Experience, I don't, care how I would have consumed, that news those tweets or those shows I just, want it to be seamless. As. Developers. All of you have a choice, which.

Of The superpowers, will you use that will delight your users you. Have different, locations, that your users are present in different markets, mature emerging, markets different connection, types low-end. Devices faster. Smartphones, you're, building for everyone, and so it's important, to keep, that in mind as you, look to be successful, in the long term. There. Are developers amongst, you who've made some great choices to, delight their users, let's. Talk about Twitter's, web experience, I, remember. When Twitter shipped their PW a two years ago it was a turning point in the broader adoption, of pwace, I heard. Many reviews, about the, Twitter experience. The new PWA being light fast. And everybody was just really happy using it and not all these people worked at Google. These. Folks used the new capabilities of the web across mobile and desktop and they're, able to do this all in one code base which. Has resulted in business outcomes. Sometimes. A focus on performance, can, make all the difference, The, Times wrote the. Largest, media conglomerate in India, has, seen that by just having a laser sharp focus on performance, a lighthouse. Core that is always at hundred, they're. Seeing business, outcomes, and they're doing this in a remarkable, way and then. Finally, Hulu, an online, streaming service. Identified. An opportunity, that was almost entirely based on user feedback the, users were saying, things about a great. Website but. They were complaining about it not being installable, and so, they brought, the two worlds together built, a desktop PWA and now, they're and it's not been too long but they're already seeing great business results. Wouldn't. It be cool if these, companies were here to tell you their stories in their own words, so, as you applaud me for my genius set up please, welcome Jessa, and Charlie to tell you about Twitter. Hi. Everyone my, name is Jess ER and I'm a product manager on the web team at Twitter my, name is Charlie I'm one of the engineers who helped build Twitter's new PWA and we, are very excited to be here today to talk about Twitter's, journey of building, one progress, or one universal, web app to serve people in both emerging, and mature markets. So. Twitter is the platform, to find out what's happening, our mission. Is to serve the public conversation. That. Starts, with giving everyone, the access to create and can share, ideas and, information. Instantly. One. Of the ways we aim to do this is by building, experiences. That are available to people no, matter what device they use. So. We were here in 2017. To talk about one of those experiences, our mobile, website that we had just launched as a PWI but, a lot has changed since, then. Twitter's. PWA has grown, since, 2017, and is also more powerful now, we're. Available, on almost every, browser and almost, every, operating, system. This. Wide reach spends, a huge, diversity of use cases customers. And devices, so. This for us prompted, a fundamental, shift in how we build our web, experiences. We've. Used our Twitter users as our customers, and we wanted to ensure we, were building and a universal, app that was responsive, to their diverse needs. One. Of the major benefits of, building a universal, app is that it allows us to build once and ship to everyone, in one, single codebase our. Users, benefit, from, regular. Updates, and consistency. Across platforms. Which, makes a better Twitter experience overall and. Organizationally. This allows us to move faster, as a team and have more focus, on the things that matter most to our users so. In, order to achieve our vision of building a universal, app we, needed to extend the functionality of our PWA to all devices, there. Are a lot of devices out there some of which are on the screen and the, team brainstormed. Dozens, of things that we needed to improve we. Built our roadmap by, launching smaller units of work and getting public feed back at each step of the way to help us iterate and improve on, the user experience. We. Started, with the mobile logged in experience, and have worked our way through replacing. Some of our legacy desktop, apps with the PW I am at. Each milestone, we, considered, what, was unique about the set of customers that we were adding how.

Did They access, Twitter differently, and how, can we meet their needs through the web product. In. Particular when. We did research across devices and markets, we, found a difference, between mobile and desktop use, cases. Mobile. Web is expected. To be fast lightweight. And cost effective, people. Tend to use mobile web when they're on the goal or looking for quick information on Twitter. Desktop. Web on the other hand is expected. To be more powerful, task-driven. And additive, to the mobile experience. People. Tend to use desktop web in a stationary, setting, with more time and intent, to consume and create, conversation, on twitter. So. Given the differences that we saw between mobile web and desktop web, we, needed to pick one as a starting, point we. Know that the majority of our users on Twitter use. Mobile devices to access the public conversation every, day so. With that in mind we start decided, to start with mobile first. It. Offered the largest room, for growth for a largest, opportunity for growth for us and also the room - most room to improve technically. We. Know that there are several barriers to using Twitter on mobile including. Poor connectivity slow. Mobile networks. Expensive. Data plans and also slow storage on devices so. In 2017. We launched our first iteration of the PWA, branded. As twitter light it. Was, faster, lighter, and engaging, giving. Our users the best Twitter, experience, at a lower cost, hence. The name white, in. Order to serve the global, conversation we. Need to make sure that, Twitter is available, to everyone and our PWA, is helping us do you adjust that and. Since. Then we've, been growing Twitter's user base with. The help of the PWI. Tweets, sent from the PWA have, increased by nearly three, times since, the launch and. Our. Users love the PWA as well they're, each using it for different reasons from data constraints. To storage constraints. We. Wanted to increase the discoverability, of the PDA so. We decided to list it in the Play Store which is where our users, went. To look for apps since. It was 2017. We did this via a webview wrapper, which. Helped, us achieve the level of discoverability, we were looking for and, essentially. Reach our users. When. We did this the install size was much smaller than our Twitter for Android app which was a huge, win for our data and storage constrained customers, we. Also saw over five million installs, of the app from the Play Store since, launch which, increased, the number of PETA people, who have the PWA, on their device. So. By, listening in the Play Store we were able to increase discoverability. Which, allowed us to reach more people and grow our user base. Listed. Again in the Play Store also gave us visibility, into how our users perceived. Our app at scale the. Reviews, and ratings across, countries, and languages, increased, our ability to find gaps, in the user experience that's. Especially, important, when you're building a global product from, San Francisco, like we are and. Today. There are a lot more options for distribution, we, started with add to homescreen, used, a webview wrapper, to bring our PW to the Play Store and I've, also used PW a builder to, bring PW, a to the Windows desktop. We're. Now exploring using trusted, web activity, as a building. Block instead of the webview all. These options mean that, whenever a customer looks, for Twitter there's, a way to install it and keep it on their device to help us grow our user base. So. All these distribution. Mechanisms, mean there's even more ways to access, the Twitter PWA and, it's gesture mentions we want to think about how our customers are different but, technically, we can go one step further and think about how their devices are different as well that. We started by building the mobile experience. Our goal has always been to create a richer, faster, experience for, all of our users and today I want to talk about how we did that for desktop, from a technical perspective. So. This is the traditional way that you might start thinking about how to create a responsive, experience for your users you'd, segment, the desktop users on one side and the mobile users on the other but. This method doesn't really capture, the level of nuance that exists in the world today many. People use physical, keyboards, with their phones or live in places where wired Internet as you might have on a desktop is actually, slower or more expensive than their wireless connection. Instead. We thought about our users and their devices in a different way instead, of looking at a device level, we broke down the properties, of their devices and treated them as parameters.

Into Our application, and. I think that this is a really great way to think about your PWA and how you build it what's. The output of an app when the Internet is 2g how. Does usability, change when a mouse or a keyboard is detected, what. About if the device is low on memory or it just doesn't have a lot of memory to start with, using. These techniques is one of the reasons we decided to keep data saver available, on the new twitter.com desktop, site we. Recognize, that there are many people in the world who can benefit from this even. If they're on a larger screen experience. Perhaps. The most important, tool to help us make these changes wasn't, even a web api it, was actually a design pattern our. Awesome designers have worked tirelessly to help us standardize, the way we use small repeated, elements across the site like, the button you see here and. It means that anytime we're working on a new page or a new feature the. Method for implementing, this is not only very clear design wise but it's well-documented, it an easy to drop in code wise as well, and. What. I've discovered is that the concept, of progressive. Enhancement it. Really lends itself to merge in components, and parameters on Twitter. We have a ton of floating, action buttons, and these allow you to do things like compose a tweet reply, to someone or create, a new list and. Anytime, we use these throughout our codebase it's always the same single, component. So, when we worked on bringing our PWA to feature, phones like you see here or other, smaller devices we, found the floating action button, was often in the way it, was too big it was hard to get to without touched and support and so. Instead of using that button we used the smaller action, bar and this was powered by the extra physical keys that those smaller devices have. So. I want to show you how easy this was to do we, use react at Twitter so that's what I'm showing here but you could do this with any component, based framework the. Gist is that we have our floating action button, component and if, we detect that the user agent is a feature phone we instead simply, render a soft button bar and what's, fun is that this is really the code we use we have a few more properties but it is this easy to alter functionality. Throughout the entire website and I think that this is a really, neat example, of progressive, enhancement because it helps the developer, make things more easily and provides, benefit, to your users as well and. We. Use this pattern to help us create better desktop, experiences. For, instance when using an overflow, menu on mobile, you see it as an action sheet while on desktop it presents instead, is a drop-down on. Larger. Screen devices we can take advantage of all that extra screen real estate to, show related content, alongside a screen this. Adds on top of the mobile experience. We. Can even go one step further and show two screens, side-by-side. Like your DM inbox and a particular message view from your DMS this, makes navigation, easier, and more powerful, for our users. Finally. Because, we've been iteratively experimenting. With desktop we got feedback along the way that the widescreen design didn't take full advantage of all the things that make desktop, unique and powerful compared, to mobile based, on this we've been experimenting with newer designs that allow easier, access to features customers, care about like, lists bookmarks, and more to come. So. We hope our journey can inspire you to build a single codebase PWA, and we have a few tips we hope that helped get you started. First. Progressive, enhancement isn't, just about the API as you use its, for the way you design the way you roadmap, and the way you think about your product as well. Next. Make sure to get your core experience right first, ensure. That the code that everyone, sees is the very best code, you write. Also. Think not just about the users but their devices and the, properties, of those devices and. Finally. Use those properties, to create a responsive, experience that, adapts, to the diverse needs of each user. So. Gesture and I didn't do this alone it takes a village to make something, that's large so a huge thanks to the entire team back at Twitter. As. You might have noticed a few of them are in the room today and so we look forward to hearing from you all we, really love working on this PWA and we truly hope that you enjoy using it and now, I'd like to welcome Rudra on stage to tell you more about how times internet builds for their users in India. Hi. Everyone namaste, from India I am, Rudra Kasturi I'm grow, today x group I'm very. Excited to be here to share times, web, success story with all of you at. Times group we, build products, for all segments, of users as we, touch their lives in everyday. In different, ways some. Of these are just, not product, but iconic, brands in their own right.

Our. Business, is large, and spread, across multiple, use cases like news, languages. Music, OTT. You. Name it at times, group we have a business around it, now. This, comes with huge. Growth opportunities, and unique, challenges, a. Recent. Study states that Internet. Users in India will, almost double, alongside, smartphones, growth in next, three to four years, but. The reality, is majority. Of these users are on slow connections on, low-end, devices with. Low storage capacity. And. If, those constraints, were an inner language. Is also a key consideration when. Building for, these users. There. Are over 200, languages spoken in Indian subcontinent with. Different scripts and dialects. We. Have seen our Hindi. Users a surpassed. English, and are growing at 94%, Iranian. This. Is where we, have identified, a huge, opportunity as, I, said earlier at times group we build products, for everyone, so. We focused, on improving the, user experience on. Our Hindi property, no, bar at times or we. Love to call it as an BT, and BT, has. Been delighting, users since, 1947. And today. We, proudly serve, 65. Million users on web. But. Most. Of these users are, in, small cities with, poor connectivity. Keeping. This in mind we. Build NBD. PWA which, is fast light. And reliable. My. Team contributes, to the growth and revenue, for the company, so, our PWA, is built, on two, pillars, performance. And engagement. Performance. Is critical for all businesses, in India and of course across the world but. Every second, delay on page load will. Lose substantial. Traffic, so. We have performance. Budget which ensures, we don't, exceed, jeaious, limit, on each, page. We. Have a maximum, JS bundle size and total. Image weight and a, specific load time to, ensure our time, to interact - always stays, under 5 seconds, on most. Of the networks and. We. Also have, a system, in place if any, of these limits has crossed we. Have an electric system that, triggers and identify. The issue and, we, quickly implement, to fix it. As. An example, we. Use webpack, bundle analyzer that helped, us to reduce our JS, file size by 70%. Or the past few months. As. A media, site we depend heavily on images, so, we used, intersection. Observer to, prioritize, and lazy load images, ensuring. The right images are loading on the right time and. We. Don't want our users to see any blank, screen or an, offline dyno when they're offline, so. We have used caching. Strategies, using, word box, so, user can still consume top, 20 stories on NBT, when, they're offline. With. All the great efforts we. Launched NV tpw a super. Fast super. Light and instant. Loading I love, the screen shot. And. We. Use lighthouse, as a source of truth to, measure, this performance, and now. Our producer. Super fast now. We want to ensure that our, users, to stays engage, more and consume, more content, keeping. This in mind we. Used add, to homescreen prom, that, waits to prompt the user when. They're most likely to install typically. During breaking, news or big events in India like elections, budget. Old, Caprica, and so, on. We. Want to earn the love of our users so we let them experience, rpw first, before. Asking them to install it and. The. Best part our. Marketing. Teams don't. Have to spend a thing they. Don't have to spend it again, because. Our average. Time, spent average spend to install an Android app is ranged between forty, two hundred rupees, depends. On the quality of the user you acquired which, is about a dollar or so. PW. Installs are absolutely. Free and. The. Biggest achievement, with this is we, have driven engagement, higher, by almost 50%, and. Finally. We, used web, share API that. Triggers, the, Android, native, share dialog to, give users control over. How and where. The, data shared, since. Launching, it we have seen increase. Of 24%. Coming, users coming to NBD why are they shared post. With. All of these we have seen incredible, wins on NB tpw, we. Saw a stunning. 72%. Increase in acquiring, new users and. We. Achieved our engagement, goals by increasing, the average time, spent by that. One percent. Which. Means the, users are sticking around for longer sessions, watching. More videos and, consuming, more content. And. Finally. I love. This light there. Was a clear, revenue, impact for, MBT as we recorded. 59. Percent increase in our network arena. There. Is no magic, will. There. Is no magic bullet here keeping. Performance. And engagement. As a key, focus areas we, are able to achieve these results. Also. We did the impossible I'm sure most of you know Alex, Russell that. Take late for PWA when, he saw NB. Tpw a trace he, went on Twitter this. Thank. You Alex. So. If you're wondering where we want to take our development, effort next, with. Incredible, bills from NBD we have launched, TWA, in six more languages, telugu. Tamil merle. Malayalam. Kannada and Bengali languages. And. Across, multiple brands such as the economic, times the biggest business news in the country Ghana, our music, streaming service, dine, out our table reservation service, and many more.

We. Strive to be at the forefront of web development so, we have used, trusted. Web activities, as a, building, block for our, Android, offering, ladies. And gentlemen I'm super. Excited to announce on this, days for the first time NBT. 2.0. Attracting. And retaining abusers, is a tough problem for users on low-end, devices with, low storage capacity, in, such scenarios. Smaller. Apps seal. The deal. Using. Trusted web activities, we, have created, a lighter experience. For the users on low-end, devices, we. Are now able to offer an experience that, is less than, 1.2. MB and five. Times faster, to install. You. Can, all cache his later experience, on web, sandbox. Please. Don't miss it, and. Finally. I. Would. Not have this opportunity to present these amazing. Business outcomes, if we didn't have been for the team a huge. Thanks, to all of them on the screen and the, Google team who helped us to achieve these, rails for the behind the screen. Now. Would like to call onstage Matt from Hulu to, explain PW a success story on the desktop. Thank. You rudra good. Afternoon everyone my name is matt oil and i'm a product manager at hulu. Hulu. Is the fastest growing streaming, service offering, live and on-demand TV, and movies in the US with over 28, million subscribers. We're. Home to acclaimed, Emmy, award-winning, Hulu original series The Handmaid's Tale an. Oscar-nominated. Documentary. Film, mining the gap. My. Team's mission at Hulu is to ensure that the Hulu experience, is especially tailored, to every single device that we're on whether. It's the TV in your living room the, computer, you're using right now or the, phone in your pocket. And. Today I'm gonna talk to you about Hulu on desktop. In. September. Of last year we, relaunched, hulu.com, it, was built from the ground up with a brand new UI and in a modern tech stack using node in next j/s and. Just. Last month, we were rewarded the 2019. People's. Voice web. Or for best media. Streaming, website. As. We. Heard from Twitter, the beauty, of developing, for web is to build once and ship, to everyone. So. My. Team's work was done right. Well. Not. Quite it turns, out we, didn't quite ship to everyone. You. See we developed, a universal, Windows platform application. For desktop in 2015, and since. Then it's, gone largely, untouched, it, was built on our old stack lacked, a ton of features didn't, have live TV, and. The. Reviews, weren't that great, but. If there was one positive, that, we could take away from what our viewers were saying about our legacy app, it. Was that our new website was better. At, Hulu we actually saw this as an opportunity to. Try something new and that's, what I'm gonna talk to you about today. We. Began by, asking ourselves, why. Did our viewers keep coming back to this legacy application, even though it lacked so, many features, well. Simply put, it. Was installable. Hulu. Viewers loved having their favorite, TV shows and movies just, a tap or click away without having a bill to their browser and. We know that having Hulu on a user's home screen drives, repeat, visits and increased, engagement. This. Is when, we had our lightbulb moment. Desktop. PWA. Leveraging. The fundamental, PWA components, would, allow us to replace the legacy, app and when, also, allow us to iteratively test PWA, without rolling out to all of our viewers, so. Where do we start. Well. We chose to start small a basic. PWA, made up of a web app manifest and. A serviceworker. Simple. Enough right just two things. Well. We. Actually found there quite a few challenges challenges. In these two components here. Are some decisions that we made that might help you and when you approach your own pwace. The. First was scope. We use the ability to set the scope of our serviceworker, to allow us to incrementally roll, out our PWA. We. Scope the server worker to its own path at hulu.com at, slash out. Then. We, pointed a native app wrapper, to this path this, allowed us to seamlessly, migrate users, from the legacy app to the new Hulu, Desktop PWA.

Without, Impacting, the entirety, of hulu.com. Here's. What that looks like in our web app manifest, we. Plan to continue to utilize this approach to incrementally test PWA, through the web browser as well and it's an approach that all of you can take to roll out PWA to your users. Second. Serviceworker. Installation. We. Had to decide when server service, worker installs would have become effective, since. Tab hoarding, is pretty common on desktop, and I know some of you are guilty of this up here we. Chose to skip the waiting phase. Here's. What it looks like in our serviceworker. Choosing. Skip waiting ensured that the latest version of the serviceworker was, installed, even when users don't close their tabs we. Refer to the serviceworker lifecycle. Developer, documentation to, pick the approach that was best for us and. Finally. Caching, the, caching, strategy, is going to determine what the offline, experience, looks like for your users do. You want to show them a cached version, of your homepage or. Display something completely, different when your users are offline at. Hulu, we have a live TV service and it's, important, that the data that we display to our users is fresh all the time. So. Hulu we took a network only approach four domains associated with these services this. Approach works really well for items with no offline, equivalent, when. Building your own pwace. It's important, to select the caching, strategy, that works best for your application, and at Hulu we, continue, to explore new avenues to, provide the right offline, experience, for our viewers without. In it without negatively, impacting, the. Timeliness, they expect from a live TV service. So. Now the, big question how. Long did all of this take well. Getting. To a baseline, PWA. Took, just one developer. Only two weeks to research, build, QA. And release. That's. Just one sprint, for my team we, literally couldn't have done it any faster, than this and. This. Is what it looks like once. Installed the hulu PWA behaves just like any other application, and now, it's just a tap or click away no. Need to sift through a forest of tabs and, we. Were able to deliver this experience, to our viewers with very little effort and consolidate. Another. Codebase in the process. Now. When. We ship a feature on hulu.com, we. Can say we, can truly build once and ship. To everyone, on desktop, and. Since. Launching, the PWA, in january it's, been doing great in just three, short months we, successfully, migrated, 96%. Of all, of our legacy app users, to, the new hulu PWA, we. Saw a 27%. Increase in, return visitors, and a, 5.5. Percent, increase. In engagement, but. I'll tell you the, best thing. Was. That our our, viewers are loving that at. Hulu we care about every single one of our viewers and feedback, like this is better, than any other KPI. Discoverability. Of desktop, pwace, has never been easier, current. Hulu subscribers, can try the PW, today PWA. Today by visiting hulu.com, slash. App using, Chrome simply. Click, on the Add to Home screen prompt, to add Hulu to your computer, and, soon. You'll. Be able to add pwace, directly. From the omnibox, in Chrome, all. Of this has given us the confidence to invest further, and PWA technology. At hulu and in. The coming months we're going to be adding a support for push notifications, media. Key is a media session api and an, enhanced offline, experience. Because. Although, we all love trying to beat our high score on the dyno game we, think that we have an opportunity to provide an even better offline, experience, for hulu subscribers, enabled.

By PWA technology. We're. Going to use offline, as a way to drive awareness for the latest Hulu, original series and we're. Going to experiment with offline media caching, to provide trailer playback, even, when a user doesn't have an internet connection, at. Hulu we are just getting started with PWA and we look forward to bringing all these features and more to our viewers soon and. Finally. I wanted to give a big thanks, to the entire Hulu, web team without, whom we couldn't have delivered this amazing, experience reviewers, thank. You all so much and back. To us all to wrap it up. Summarizing. Months of hard work in just 10 minutes is, no easy task so, as a measure, of how amazing they were can you please give them a loud cheer and a huge round of applause. Lighthouse. Tour 1000. I'm. Sure you've been listening intently, for the past 30 minutes that. Was a lot of information, and so I'm going to quickly recap, for you take, your phones out take, photographs, and if you are watching us on the live stream screenshots. Twitter. Showed us that by building a responsive experience, in, one, codebase, you. Lower development, costs, you, create engineering, velocity and. You. Increase the number of tweets that they had sent by, almost, three times this, is a direct business outcome, for Twitter. X. Builds, for the next billion users with. A laser sharp focus on performance, and a, tracking system that breaks if you don't hit that hundred, on lighthouse they've, successfully earned the love of their users. Across. Different. Languages their, PWA, has contributed to, 59%. Increase in ad, network, revenue a direct. Business, outcome and. Finally. If there's one thing you take away from what Matt said listen. To what your users are saying they. Might be giving you some feedback, that might really be, helpful for you in ads we'll make development, choices so look, at your legacy apps some, that you might have ignored for a while use. The web superpowers, and. Create lightful, experiences, just like Hulu's PWA, on desktop, it's. Still early days but Hulu's PWA is loved by, their users and they're, seeing an increase in, 27%. For return visitors, an engagement. Is also on the rise at about five and a half percent it's it's just been a few months these, are direct business outcomes for hulu and finally. As a user it's, not that i don't care i trust, you to make the right choices so I can have a delightful, daily, routine I can continue asking profound, questions so thank you very much, take. A look at your business see how PW, is can help you we've, got material. When you're ready up on webdev, so the exact this is a good one to take a photograph of or, did your site lighthouse, helps you test against various benchmarks, or, just come talk to us at the web sound rocks and if you're watching online you can leave a comment or a question below, and we'll get back to you can't, wait to see what you all will thank you very much.

2019-05-15 22:02

Show Video

Comments:

Wow! This is amazing. The presenter was extremely articulate.

What is wrong with the audio?

This is cool but what in the world... Just building stuff and telling people what the future is; then just building more stuff and saying the same thing. Again, it's very cool but this is just blah blah blah

Something wrong with sound

these are all almost everywhere lolx

Feeling so happy n n soo proud to see so many Indians at Google IO

Other news