 Hi, everyone. My name is Eiji. I'm working at Google from Tokyo Office. And as Monica said, I was born in Liptei. In general, Asian people are said to look like younger than other people, but I'm actually younger. Anyway, today I'm going to talk about signing and payment without forms. So last month, I was going to purchase a TV rack. I knew what I wanted, so I just searched for the web for that particular product and found the most reasonable deal at a small e-commerce website. So I decided to purchase that using my mobile phone. According to a research, 66% of mobile purchases are done through mobile web rather than native apps. That's great to hear, right? So I went to continue to check out form and try to fill out form. But in the end, I gave it up. The reason is that the entire experience filling out forms is so painful. Typing physical information, address information, and a password on tiny, tiny software keyboard is such a frustrating experience, right? So the same research tells that the conversion rates on mobile web is 66% fewer comparing to that on the desktop. Even for returning users, remembering and typing their password is a pain. Another study shows that 92% of users who visited your website leaves without resetting or recovering their account when they forget their password. Web forms causing lots of friction. And we need to fix that. In order to overcome this situation, web platform have come up with two new APIs, which are payment request API and credential management API. So what I'm going to do now is to show you a demo website which we introduced at Google I.O. called Polymer Shop. And how we integrated payment request API and credential management API play nice together. So this is the Polymer Shop website. It looks nice, right? So imagine that I'm looking for a sweater or some kind of clothes that won't be up for upcoming winter. So let's explore the website. By the way, these looks all good, right? And you want it, but these are not actual shop. And please don't send us email asking when did you get the goods delivered. We actually had that. But anyway, let's continue. Yeah, this one, this hoodie looks nice. So let's purchase this. Price looks good, right? $38.85. Buy now. And now you see a dialog pops up from the bottom. This is actually done by API called Payment Request API. Let's have a look at from the top. So at the top, order summary shows the price of the goods, hoodie $38.85, that's correct. So let's continue. Then next one is a shipping address. What is surprising is that my address information, three of my address information, of course, these are fake, but showed up. And what is nice about this is that I am not signed in or signed up to this website yet. But these information are already available. Why? Because I have entered this kind of information in the past using the same browser. So browser nicely remembers my old address information for me, so I can use them here. So let's select one. And the next one is shipping option. So standard shipping or express shipping. So I'm not in hurry. I can just select standard shipping. Notice that by selecting one, the order summary has added new price, standard shipping. So the total cost has been changed. And now I go to the payment. And like my address information, my credit card information is already filled here. It's quite nice, right? And lastly, contact information. So my email address is there. Looks good. OK, everything looks good, so I can just proceed to payment, pay. Then I give my CVC and confirm. And done. So imagine that I wasn't explaining all this, right? It's only a few tabs without typing single letter using a software keyboard. It's an amazing experience. And now we are at the account creation page. So the good thing about making a account creation page after making purchase is that users can make purchase using a guest checkout, which is much, much lower hardware for users. And then users are motivated to create an account. You may provide some reason for that. For example, you can provide 10% discount for the next purchase, or maybe you can provide like a delivery tracking feature, right? So why not? Let's sign up. So email address is, as you see, already filled up. It's nice because it was provided by payment request API. The email address is already filled. So all I have to do is to type my new password here and sign up. And done. And now, if you look at the bottom of the page, it's asking me if I want to store my credential information. It's nice, yeah? So save. This will make my next visit to this website much, much easier. So browser assist me to sign in. But here's a new thing. By using credential management API, the things got much, much easier by letting me sign in without a single tap. To demonstrate that feature, I'm going to swap device to a new one. So what is going to happen is that the credential information I have just stored to my other device is synchronized across my Google account. And it is now, it should be, now in my other device. And hopefully, it will work. And yeah, let's see. To be honest, this sometimes fails. So fingers crossed. OK, ready? Look at the bottom of the page. Boom. I'm signed in. Yeah. So imagine that you have to sign in by tapping something at least. But with this, you have no action required to get signed in. And just continue your shopping experience. This is really nice. OK, can you turn back the page slide? So this beautiful integration was possible because of a payment request API and credential management API. And I'm going to introduce each of APIs now. So payment request API. So payment request API provides some standard compliant online payment flow. Usually, making payment requires you to fill a long form and submit that to the server. But with payment request API, you can, instead filling out form, you can just a few taps to submit the same information. If there are no address or credit card information already available, users can just add them on the fly using the same native UI. The address information can be stored and synchronized across devices and available from anywhere for their future shopping experience. The best part of payment request API is that once those information is stored to the browser, we basically have all the data required to get the payment flow, get through the payment flow and without creating an account. Even for the users who have never visited your website before can make a purchase. And it's easy. Payment request API also allows third party payment methods to be part of the ecosystem. Anyone will be able to provide an app or a web app for merchants to process payment in the future. One such effort is Android Pay for payment request API, which is currently in beta. And you can try it out. To learn more about payment request API, we provide integration guide and demo site and so on. So you can just follow the link, g.show payment request API. So integrating payment request API into Polymer Shop, we created a component, Shop Payment Request. Nice thing about making it a web component is that the sum of predefined parameters can be set as element attributes, declaratively, like currency supported methods and request pay or email and so on. It's declarative. Requesting payment can be done through a function call because it returns a promise. You can just continue with sending the result to payment processors when the promise results. And now about the Credential Management API. So Credential Management API provides a programmatic interface to the browser's password manager in a secure way. So you can obtain or store user's credential information on behalf of the user. As you have seen at the Polymer Shop demo, you can enable odd sign-in by obtaining the credential information, then send that over to the server on behalf of the user, which is authentication. Sign-in using a third party identity, such as Google or Login, is quite popular because it allows users to sign in just by one tap. And it's also good for your security. But the problem is that that kind of information is not stored to the browser. So you forget which identity provider I use to sign in to this website. But by using Credential Management API, it can even remember that information. So by storing the choice of your federated Login account, you can let invoke identity provider's authentication logic to let the user sign in. Even if you choose not to use odd sign-in, you can still skip the sign-in form by using an account chooser without typing a password. This feature is also useful for those who have multiple accounts. So it's handy. Android apps have similar feature called a SmartLock for Password. By associating your Android app and your website, you can share the same credential information between them. So if a user stored credential information to Android app by signing up, the user can come back to their associated website to get odd sign-in, which is awesome. To learn more about Credential Management API, we also provide an integration guide and so on. So you can just follow g.co slash Credential Management API. And integrating this shop Credential Management API and entire authentication mechanism was created by a shop account component. We put various features into this. For example, FormUI actually included UI and loading UI, notification UI, as well as authentication logic, federated Login logic, and Credential Management API, and also managing profile data. So it's very complex. And the point is that a lot of different part of the app required to access those kind of information or logic. So what we've done is to decided to split that into two parts. So one is a shop account, the same name, with all the UI related things. And the new one is shop account data, which handles all the authentication logic related things, as well as managing profile data. By adding IRON meta behavior to the shop account data, we've made it available throughout the app. Also, by returning a promise, things got much simpler by changing functions to reflect results to the UI, depending on the context. So RECAP Polymer Shop, I started with a Polymer Shop demo, and it integrated two APIs, which is a payment request API and a credential management API, and how we integrated these APIs into Polymer Shop. And lastly, I forgot to mention that what about the TB rack I was going to purchase. And what I've done was, after abandoning my purchase on the checkout form, I just went home and opened up my laptop and continue my purchase. And it's happily sitting in my living room. So I'm very happy. And I'm really hoping that they will come soon, where I could finish all the entire shopping experience using mobile web. Thank you.