This is the code repository for AMP: Building Accelerated Mobile Pages, published by Packt. It contains all the supporting project files necessary to work through the book from start to finish.

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.

All of the code is organized into folders. Each folder starts with a number followed by the application name. For example, Chapter02.

The code will look like the following:

<div id="confirm">Are you sure you want to continue?</div>
<a on="tap:confirm.hide">Cancel</a> <a href="confirm-page.html">Confirm</a>

The requirements for this book are straightforward for AMP, and are similar for every chapter:

• Webserver such as Apache, NGINX, or NodeJS
• Web browser (such as Chrome or Firefox)
• Text/HTML editor (such as SublimeText)
• A web-connected mobile device, such as an Android or iOS phone, is recommended but not required Additionally, some examples require the following. Where required, this is noted along with the example: HTTPS: Server-side technology--some examples require a server-side component to deliver data. PHP was chosen for its wide availability, but any server-side language could be used. Access to an alternative domain--this can simply be a domain alias that points to the same application directory on your server.

• Building Mobile Applications Using Kendo UI Mobile and ASP.NET Web API

• Building a Single Page Web Application with Knockout.js [Video]

• Building Single-page Web Apps with Meteor

Click here if you have any feedback or suggestions.