Book Image

AMP: Building Accelerated Mobile Pages

By : Ruadhan O'Donoghue
Book Image

AMP: Building Accelerated Mobile Pages

By: Ruadhan O'Donoghue

Overview of this book

Google introduced the Accelerated Mobile Pages (AMP) project to give mobile users lightning-fast response times when accessing web pages on mobile devices. AMP delivers great user experiences by providing a framework for optimizing web pages that otherwise would take much longer to load on a mobile platform. This book shows how to solve page performance issues using the mobile web technologies available today. You will learn how to build instant-loading web pages, and have them featured more prominently on Google searches. If you want your website to succeed on mobile, if you care about SEO, and if you want to stay competitive, then this book is for you! You will go on a mobile web development journey that demonstrates with concrete examples how to build lightning-fast pages that will keep your visitors on-site and happy. This journey begins by showing how to build a simple blog article-style web page using AMP. As new concepts are introduced this page is gradually refined until you will have the skills and confidence to build a variety of rich and interactive mobile web pages. These will include e-commerce product pages, interactive forms and menus, maps and commenting systems, and even Progressive Web Apps.
Table of Contents (24 chapters)
Title Page
About the Author
About the Reviewer
Customer Feedback
Actions and Events
amp-bind Permitted Attribute Bindings

Fetching the shopping cart on page load

We just saw how to use amp-list to pull in a list of related products on a web page. Now let's try something a bit different. In the last chapter, we implemented a basic shopping cart: when an item was added to the cart, we displayed a summary of the cart contents after receiving a response from the server backend. A problem with this approach was that we couldn't show the cart summary on page load; we had to wait for the user to add an item and submit a form first. So if the user navigated to another page, for example, the cart summary would no longer be visible. We can fix this with amp-list.

We'll set it up so that on page load, amp-list will fetch the shopping cart, using the CLIENT_ID variable substitution we saw in the last chapter to identify the user.

First, we'll set up a server endpoint to return the same JSON data that represents the cart as before. Well, almost the same; we've added a new property, cart_total_items, that we'll display in...