From 2b1dc5fe208172e5cc79d2510fff12d3f738b693 Mon Sep 17 00:00:00 2001 From: Paul Kinlan Date: Wed, 2 Oct 2013 10:58:15 +0100 Subject: [PATCH 1/2] Fixes some typos in requestAutoComplete API --- .../forms/requestautocomplete/en/index.html | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/tutorials/forms/requestautocomplete/en/index.html b/content/tutorials/forms/requestautocomplete/en/index.html index 1d6120e5f..ec8ae16fa 100644 --- a/content/tutorials/forms/requestautocomplete/en/index.html +++ b/content/tutorials/forms/requestautocomplete/en/index.html @@ -15,17 +15,17 @@

Introduction

I like the web. All in all, I think it’s a pretty good idea. As such, I get into a lot of web vs native debates. It doesn’t take long for the other person to start talking about the ease of payments through native systems. My usual response is to drop a smoke bomb and run out of the room laughing maniacally, because it’s not an argument I can win.

Shopping cart abandonment on the mobile web can be as high as 97%. Imagine that in the real world. Imagine 97% of people in a supermarket, with a cart brimming full of things that they want, flipping their cart over and walking out.

-

Now, some of those people are just pricing stuff up and never had an intention to buy, but horrific user experience of buying on the web is a significant contributor. We’re hitting users with a tax on their sanity.

+

Now, some of those people are just pricing stuff up and never had an intention to buy, but the horrific user experience of buying on the web is a significant contributor. We’re hitting users with a tax on their sanity.

Think of a pleasurable payment experience you had on the web, especially on mobile. It’s an app store, right? Or at least a similar closed system that already has your payment information.

-

This is a problem. It requires sites to commit to a particular payment provider that the user may already have an account with & be logged into, or commit to a platform that requires users to be logged into a particular payment provider, such as app stores which require you to code solely for that platform. If you don’t do one of these things, the user is doomed to tap away at their screen or keyboard until all their finger-skin is gone, or they give up.

+

This is a problem. It requires sites to commit to a particular payment provider that the user must already have an account with and be logged into, or to commit to a platform that requires users to be logged into a particular payment provider, such as an app storexs that require you to code solely for that platform. If you don’t do one of these things, the user is doomed to tap away at their screen or keyboard until all their finger-skin is gone, or they give up.

We need to fix that.

requestAutocomplete

-

In a world of WebGL, WebRTC and other fancy web APIs that start with “Web”, requestAutocomplete is rather unglamorous. However, it’s a superhero in beige clothing. A tiny boring API that can stick a stake through the heart of the web payments time-vampire.

+

In a world of WebGL, WebRTC and other fancy web APIs that start with “Web”, requestAutocomplete is rather unglamorous. However, it’s a superhero in beige clothing. A tiny, boring API that can stick a stake through the heart of the web payments time-vampire.

- +

Rather than the site relying on a particular payment provider, it requests payment details from the browser, which stores them on the user’s behalf.

@@ -96,7 +96,7 @@

Address

  • name - full name. Taking a full name as a single field is far better than multiple fields. Multiple fields such as first-name and last-name show a Western bias and may not make sense to other cultures, also it’s easier to type into a single field
  • tel - full telephone number including country code, can alternatively be broken down into
    • @@ -136,7 +136,7 @@

    Address

    Once again, the name attributes are examples, you can use whatever you want.

    -

    Obviously not all forms should request a shipping address, eg don’t ask me where I’d like my hotel room delivered, it’s current location is often the selling point.

    +

    Obviously not all forms should request a shipping address, e.g. don’t ask me where I’d like my hotel room delivered, it’s current location is often the selling point.

    Right, so we’ve got our form, and we know how to request autocompletion. But…

    When should requestAutocomplete be called?

    @@ -247,7 +247,7 @@

    You’ve called requestAutocomplete, what now?Where does the browser store my data?

    The specification doesn’t dictate where data is stored, allowing browsers to innovate.

    -

    If you’re logged into Chrome, you get the option to store details in Google Wallet, making them accessible on other devices you’re logged into. If you store your details in Wallet, your real card number won’t be dealt out by requestAutocomplete, instead a Google Wallet Virtual Card so your actual card number isn't sent to the seller, increasing security.

    +

    If you’re logged into Chrome, you get the option to store details in Google Wallet, making them accessible on other devices you’re logged into. If you store your details in Wallet, your real card number won’t be dealt out by requestAutocomplete, increasing security.

    If you aren’t logged into Chrome, or choose not to use Google Wallet, your details are optionally stored locally in the browser for reuse.

    This is the state of things now, but in future Chrome and other browsers may adopt additional payment providers.

    @@ -289,4 +289,4 @@

    Bonus round: Handling multi-page forms

    }); -{% endblock %} \ No newline at end of file +{% endblock %} From 206b5020561c866f72786cf5a4f639d81e610347 Mon Sep 17 00:00:00 2001 From: Paul Kinlan Date: Wed, 2 Oct 2013 11:51:43 +0100 Subject: [PATCH 2/2] Fixes tutorial.yaml with the correct information --- database/tutorials.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/database/tutorials.yaml b/database/tutorials.yaml index d6ba1c66b..69973f6f6 100644 --- a/database/tutorials.yaml +++ b/database/tutorials.yaml @@ -1,13 +1,13 @@ title: "requestAutocomplete - take my money, not my time" url: /tutorials/forms/requestautocomplete/ author_id: jakearchibald -publication_date: 2013-05-29 -description: How to squeeze performance out of script loading +publication_date: 2013-10-03 +description: "How to squeeze performance out of script loading" browser_support: - chrome tags: - forms -- type:tutorial +- type:article - class:nuts_and_bolts ---