Create a seatmap

Important: this documentation is not applicable to your currently selected format ads!

Seatmaps are important parts of ticketers' web apps, but the implementation in AMP can be difficult. Read on to learn how to implement a seatmap in AMP by using a combination of available AMP components.

A live sample implementing the practices described below is available here.

AMP Components needed

Let's start by reviewing the components needed:


amp-pan-zoom allows to zoom and pan the content via double tap and pinching. This component serves as base for the seatmap implementation.


amp-list fetches content dynamically from a CORS JSON endpoint and renders it using a supplied template. Used to fetch current seatmap availability, so that users always get the latest data.


amp-bind adds interactivity to the page. Needed here to keep track of how many seats have been selected.


amp-selector represents a control that presents a menu of options and lets the user choose from it. The entire seatmap can be considered a menu of options where each seat is an option. It makes styling the selected state for seats much easier by allowing you to use CSS expressions. For example, the following expression fills a seat with an orange color once selected.

rect[selected].seat {
  fill: var(--orange-theme);


  1. To draw a seatmap as an SVG where each seat is represented by a rect element, you need information on each seat: position x and y, width and height and possibly rx and ry to round the corners of the rectangles.
  2. A unique identifier for very seat that can be used to make the booking.
  3. A measure of the entire width and height of the seatmap to be used in the viewbox attribute.

Drawing the seatmap

The seatmap is rendered via amp-list and amp-mustache. After receiving the data from the amp-list call, you can use said data to iterate through the seats:

<svg preserveAspectRatio="xMidYMin slice" viewBox="0 0 {{width}} {{height}}">
<rect option="{{id}}" role="button" tabindex="0" class="seat {{unavailable}}" x="{{x}}" y="{{y}}" width="{{width}}" height="{{height}}" rx="{{rx}}" ry="{{ry}}"/>

Styling unavailable seats

In the above example, {{unavailable}} is the value of a field returned by the JSON endpoint and used to style an unavailable seat. This approach doesn’t allow you to remove attributes like option="" in case a seat is unavailable, as the template cannot wrap the entire pages' <html> element.

An alternative, more verbose approach is to repeat the tags as following:

{{#available }}<rect option="" role="button" tabindex="0" class="seat" x="" y="" width="" height="" rx="" ry=""/>{{/available }}
{{^available}}<rect role="button" tabindex="0" class="seat unavailable" x="" y="" width="" height="" rx="" ry=""/>{{/available }}

Sizing your seatmap

Unless your seatmap's size is fixed, it's difficult to size the amp-list containing the seatmap. amp-list needs either fixed dimensions or use layout="fill" (to use the available space of the parent container). There are two ways to address this problem:

  1. Calculate the available space on the page once you know the space used by other components like headers and footers. This calculation can be done in CSS by using the calc expression and assigning it as the min-height of a parent div of the amp-list.
  2. Use a flex layout when knowing the height of the page layout.

Styling amp-pan-zoom

If using the approach described in the previous section, amp-pan-zoom needs to use layout="fill" as well.

TIP – To keep some white space around the seatmap and still make it part of the pinch and zooming area:

  • Add a wrapping div for the svg
  • Add padding

If you don’t have a wrapping div and add margin to the SVG instead, it won't make the margins part of the pinch and zooming area.

Handling state

When users click on different seats, it’s possible to keep track of the selected seat ids in a variable by using amp-state, either by:

  • Adding an amp-bind expression for every seat to add the selected seat to a list
  • Or using amp-selector with the action on="select:AMP.setState({selectedSeats: event.selectedOptions})" so that all the selected seats are added to a list

While the first approach doesn’t require the additional component amp-selector, it can make the seatmap very slow because every amp-bind expression will be evaluated at every seat selection/deselection.

The second approach also allows you to reduce the duplication of the amp-bind expression for every seat that will be rendered by the template.

Final HTML structure

For reference, here's the final HTML for the seatmap:

<div class="seatmap-container">
  <amp-list layout="fill" src="/json/seats.json" binding="no" items="." single-item noloading>
    <template type="amp-mustache">
      <amp-pan-zoom layout="fill" class="seatmap">
        <amp-selector multiple on="select:AMP.setState({
          selectedSeats: event.selectedOptions
        })" layout="fill">
          <div class="svg-container">
            <svg preserveAspectRatio="xMidYMin slice" viewBox="0 0 {{width}} {{height}}">
              <rect option="{{id}}" role="button"
               tabindex="0" class="seat {{unavailable}}"
              x="{{x}}" y="{{y}}"
              width="{{width}}" height="{{height}}"
              rx="{{rx}}" ry="{{ry}}"/>