April 1, 2020
Keynote (AMP Conf 2018)

Keynote (AMP Conf 2018)

DAVE BESBRIS: Hi. So I have a tradition of
telling really, really bad jokes to start off keynotes. But this year, they’re
exceptionally bad. So I’m saving them for the Ask
Me Anything booth for later on. Come and find me in the booth. And if you really want
to ask me anything, you can get a really
bad joke in response. But first of all, I want
to say welcome to everybody for the second annual AMP Conf. I’m really excited to have
everybody here in Amsterdam. We’ve never been here before. Last year, it was in New York. And also, a big
welcome to everybody on the Livestream,
who’s watching today, including my mom. So we’re two years into
building the AMP project. And we’ve made tremendous
progress together. For example, now there are
over 31 million domains on the internet publishing AMP. And they’ve published
over 5 billion pages. This number has been growing
a lot over the last year. And the types of publishers
that have been making AMP pages have changed quite a
bit since we launched. In fact, AMP is now used
for recipes, and travel, and retail, and dictionaries. And you know, Wrap-Genius,
and many other use cases. And in fact, over 60% of all the
clicks to AMP pages from Google Search go to non-news pages. So companies are investing in
AMP and seeing great returns. In fact, we’ve asked Forrester
to make a study on this topic and to see what they found, is
that publishers are doubling– are seeing a doubling of
time spent on their page, with a 20% increase
in conversion. That’s a pretty impressive stat. And we think that
these stats are showing this amazing
momentum that we’re seeing in the ecosystem. We’re really excited to talk
about what’s going on today. And we have an
incredible lineup, including the man
himself, Malte Ubl, who’s the tech lead of AMP. And I’m really excited to
pass it over to Malte now. [APPLAUSE] MALTE UBL: Thanks, Bes. Hi, everyone. Can you actually see me
against the backdrop? It’s like poor choice
of shirt color. So yeah, my name is Malte, and
I lead the Engineering team working on AMP for Google. Today I’m going to talk
about several big efforts that my team and the wider
community has been working on. And to kind of give you a
little bit of an overview, most sections will kind of
end in pointing to a talk has the deeper
dive on the topic. Because obviously,
we’re like the keynote and we’re glossing
over everything. So do make sure to
watch those talks. Cool. As the first thing, what
I wanted to talk about, is AMP’s vision as
a project, which is to create a strong,
user-first open web forever. And I really want to drill
on that user-first part. So what we’re
trying to do is kind of re-envision the web
along that user-centered, user-focused kind of model. And it kind of really
drives everything we do. We might not always
get it right. In that case, we really also
ask you to call us out on it. On the other hand, we
won’t stop to challenge the status quo in terms
of user-first principles. And I think there is
one particular way in which AMP is different
from other efforts along these lines. Because we’re not only trying
to change 100 websites, or 1,000 websites, or 10,000 websites. Our mission is really to
make big chunks of the web more excellent. The way I call this is to
commoditize excellence. So you really, like
uplift large chunks of the web to a higher standard. And I think we’ve had pretty
good success in the performance space, right? So Bes just said that we have
over 5 billion AMP pages. And then looking at
Google Search, when people come from web to AMP pages,
the load time we’re seeing is consistently at the
median under one second. So I think that’s pretty good. And definitely, an improvement
over the web before AMP. But I’m also, like not standing
here with a big “mission accomplished” banner. So I think there’s a
lot more we can do along this theme of
commoditizing excellence. And the topic that I
wanted to talk about first with this respect is
content consumption, because it is
changing over time. And people on mobile have
different expectations for how content works, right? So they might only
one to two minutes. They want a snack. And that long-form article might
not always be the right choice. And then, given this
insight, we felt that it wasn’t really that
easy to publish content in a form that would actually
match that user need. And that’s why we’re
introducing AMP Stories. So you might have heard about
this in the press before. I think “The Wall
Street Journal” wrote about it a while ago. But now, it’s actually a thing. It’s been coming together
on the open source project. And today, we’re launching
both a developer preview on AMP site. And there’s going to be
surfacing of these stories in Google Search. To give you a little bit
of an impression of what this actually is, let’s
AMP Stories, you’re getting rich visuals
with native video. There’s great support
for animations with tappable interaction. It’s very much
designed mobile first, but it works remarkably
well on desktop. And because it’s just
AMP, all the things you might already know and
might expect still works. For example, AMP analytics
is supported, obviously, right out of the box. It’s important as a
technology for many groups. So for a user,
what you’re getting are these snackable,
bite-sized pieces of visual content for
your mobile device. As a publisher, you can
focus on creating content while relying on the
well-tested technology basis. And then finally, these stories
are part of the open web. So they’re linkable, shareable. And they’re not locking you
into any particular native app walled garden. They’re just a web page. You publish into
your own web server, just like any
other AMP document. And so today, we have
the developer preview. There is the resources at
ampproject.org/stories. And you can actually try it
out in Google Search by going to g.co/ampstories with these
brands having created stories. This was just a short
overview of what is to come. There’s a talk right after
this keynote by Jon and Eli. So definitely, check that
out if you want to learn more about AMP Stories. As the next topic we’re going
to talk about, what I think my team has spent the most
time over the next year– over the last year,
which is e-commerce. And for that, please
welcome on stage, Lisa Wang, who is the Project Manager for
E-commerce on the Google team. [APPLAUSE] LISA WANG: Hi, I’m Lisa. I’m a Product Manager
on AMP, and I lead our e-commerce initiatives. And to start, I actually
want to reflect a little bit. So last year at AMP Conf,
we announced the launch of AMP Bind, which basically
opened the door to building interactive experiences in AMP. So now, not only can you build
a beautiful, user-friendly content page, you can also
build a beautiful, user-friendly interactive experience. And today, I’m so
excited to announce that AMP Bind is currently being
used on over 150 million URLs and over 80,000 domains. And it’s growing
really strongly. So if you haven’t
yet, I encourage you to take the time
to check out AMP Bind, see if you can build out
the interactive experiences on your own site with it. And with the support of
AMP Bind and the support for interactivity,
we really believe that AMP is now ready for
the full scope of e-commerce. So everything from
retail, to travel, to classifieds, to
listings, and more. But that’s not to say
that our job is done, so we’re continuing
to build out support for these new verticals. That demo that you see on the
right here is of a date picker that we are working on
to better support travel. And this recently went
into experimentation. So if this is something
that your site needs, please feel free to try it out
and let us know your feedback. And we’re seeing
that sites are also continuing to push the
boundaries of what’s possible in AMP. So that middle demo is
a Product Details page and add to cart experience
that AliExpress built. And you can see that
it’s fully interactive. It’s full of features. And it really just looks
like any other web page. And the AMP team, we also
continue to try and put ourselves in your shoes. To make sure that building
out experiences that we think can benefit from AMP is really
as easy as we think it is. So that last demo there
is some stress testing we were basically doing of
testing out different payment providers and making sure it
was really easy to integrate with an AMP form. And you can see the demo there. And for all three of these
experiences and more, I’ll go into the
technical details tomorrow morning in my talk,
9:00 AM, right back here bright and early. So I’ll see you then for that. And as we’ve moved our
support into new verticals, we’ve seen that many of
the top e-commerce brands across verticals and around the
world have really embraced AMP. And for a lot of
these brands, they started out by just building
out their simpler landing pages or their content
pages with AMP. But as they saw the immense
return on investment they were getting,
they’ve started to build out more and more
pages in the funnel with AMP. So moving into the checkout
flow and the payments flow, really trying to
give their customers that end-to-end seamless
and fast user experience. And so these are
some of the top– the logos of some of the top
companies that have adopted AMP. And we really hope
that next year, we’re able to see all of
your logos up here as well. Now, of course, the best
part about adopting AMP, aside from getting your logo
on our slide once a year, is really the immense
benefit that you can see to your revenue numbers. So a few quick examples here. Wego is a travel
aggregator that was able to see a 95% increase in
their partner conversion rates by converting their
landing pages to AMP. US Xpress is a shipping
company that saw $1 million in yearly projected savings just
by changing their recruitment pages to be built in AMP. And Event Tickets
on [INAUDIBLE],, which is a ticketing
company, saw a 20% uplift in conversions over
their responsive sites. So over a site that was
already optimized for mobile. And so we really believe that
the value of AMP for e-commerce is really clear
and really large. Because if you can get your
content in front of your users more quickly, they’re more
likely to engage with you and interact with you. And hopefully, make a purchase. Whereas, if you stick them
with a loading spinner and a blank screen,
they are more than happy to jump to a
competitor’s site and see if they can get
what they need more quickly. Oh, I actually need to
put on my Google hat now. It’s not the great. We are, obviously, a tech
company and not a hat company, but it’s fine. Now, I can officially speak
on some of the cool stuff that Google is doing with AMP. So one of the
biggest initiatives has been to expand AMP
experiences from just organic to paid as well– to paid search as well. And last year, the AdWords team
launched their AMP experience where clicking on ads will
now lead you to AMP pages. And they’re already seeing some
really great success with this. So Merchology is a retail
brand that when they did this, they saw that their AMP
pages were 286% faster. And with that, they saw
39% higher conversions. So if you use AdWords
and you have AMP pages, you should definitely
take advantage of this. And if you use AdWords but
you don’t have AMP pages, this is probably a good time
to check out AMP and see what it can do for your site. And if you’re familiar
with the shopping carousel on the
Search page, where you can swipe through
products and basically browse through
them, Google is also piloting serving
AMP pages from here. And they’re seeing some really
encouraging results from this already. So if you’re interested,
please let your account team know that you want to
participate in the pilot. Cool. I can get rid of this now. I want to take a quick minute
to just talk about the best approach to building AMP pages. So when we first launched
AMP, we provided a way for you to link your non-AMP page
with your new AMP page. At that time, it didn’t
really make sense for you to switch completely over to
AMP because the format was still new. And it was still developing. And we were still building
out functionality. But now, we’ve seen so
much success with AMP and the functionality
has grown so much that we feel confident
in saying that AMP is the right core technology
to build your site with. And we’re already seeing
this happen at scale. And not just with content sites. Not just with publishing sites,
but with e-commerce sites. So today, I’m so
excited to announce that AliExpress,
one of the largest e-commerce companies in the
world, has gone all-in on AMP. But you don’t take
my word for it, so we’ll watch a quick
video from their Technical Lead, Graham Lok, on why
they decided to choose AMP. [VIDEO PLAYBACK] [END PLAYBACK] LISA WANG: Thank you to
Graham and the AliExpress team for joining us remotely. I just wanted to
emphasize one thing that stuck with me as I
watched this video, which was that going all-in
on AMP at AliExpress was a decision that
was unanimously given the green light. Because they believe– and we
agree– that delivering pages faster to their users will lead
to a better user experience. Now, if you do decide to go
with this approach, which we’re calling canonical AMP,
traditionally there has been the challenge
that serving AMP pages from your origin isn’t
as fast as serving them from the AMP cache. So I’m also really
excited to announce today that we’re releasing the
AMP Toolbox Optimizer, which is basically a toolkit
that developers can use to optimize
AMP documents served from their origin. And right now, it includes all
those performance optimizations that make delivery from
the AMP cache really fast. And you can see that in this
demo, the optimized Tasty page loads about two seconds faster
than the regular AMP page. So the benefits of this can
be really huge for your site. And we’ll have more details on
this in Abby and Andre’s talk using AMP as a library to
build user-friendly sites later on today. And now, I will pass it
back to Malte to talk about ads and analytics. [APPLAUSE] MALTE UBL: Or, as I
sometimes call it, something has to pay the bills. Because you know, we all
enjoy that free content on the internet, but it
doesn’t come out of thin air. Someone has to make a
living making that content. And while we’re like,
actually super-big fans of alternative
ways of monetizing content, like subscriptions
or micro-payments, I think everyone realizes
that ads, and especially display ads, do have to play
at least some role in financing that content that we are
looking for on the web. And coming back to
that vision I outlined at the beginning
of this keynote, of the web re-expressed in
terms of a user-first principle, I think everyone would
admit that display ads on the internet aren’t
always the greatest user experience. And then, lately
I’ve seen headlines like this where ads
decided that maybe cryptomining on your
machine is a great idea. And what we found is that
the way ads work today on the internet,
there’s really nothing you can do at scale
to prevent this. You can, obviously,
audit things. And you can make sure
you trust people. But like, there’s nothing
there that really helps you ensure that it’s secure. So there is an
architectural issue that– the way the system works
by injecting third-party JavaScript from random people– doesn’t really produce
great results at scale. And so we’re on a
mission to fix this. And because we’re the
AMP team, we also, obviously, want to make
everything super-fast along the way. And so I think
that’s a good summary of what AMP HTML ads are. They’re a way to make fast
and beautiful-looking ads. But primarily, they’re
just purely declarative. So there’s no arbitrary
JavaScript execution. And so stuff like
bitcoin mining, or malware injection, et
cetera, just isn’t possible. And you know, this has
been a journey already for one and a half years. We’re pretty excited about it. And the first results
are very excellent. So for example, El Pais– it’s a Spanish
publisher– they were seeing a 90% reduction
in ad latency and a 32% increase in
click-through rate. And then, Logicad, which is
a Japanese demand side ad platform, I think, were seeing
a 33% reduction ad latency. And again, a 30% increase
in click-through rate. So again, we’ve been on this
for about one and a half years. And you know, it’s
a daunting project. Basically, all aspect of the
entire advertising value chain, which is incredibly big–
you wouldn’t imagine– have to be updated to work
inside of this new ecosystem. And one important
part of that is that someone has to actually
make these ad creatives. And so I’m very
excited to announce that Google’s tool for doing
this, which is Google Web Designer, will add support
for AMP HTML, rich media ads, in March of this year. Everyone’s super-excited. Yay, ads. Talking a little bit, switching
gears from AMP HTML ads just to how AMP– monetization with
ads on AMP is going. So what we’ve been
seeing over the last year is that publisher daily ad
revenue has increased by 3x. And that is only actually
the part of the statistics that we have access
to as Google. So we looked at
DoubleClick and AdSense. But what I think
is really important is that there is a large
and vibrant ecosystem of ad providers on AMP pages. So in fact, we’ve
done some research. And we found that
over a hundred ad networks are actively
monetizing on AMP pages. So if you’ve ever
heard, you have to run Google ads on AMP
pages, it’s totally not true. And also, not what’s actually
happening in the wild. Another important
way to look at it is, obviously, how much
money am I making per page? A great study here
from India Today. They were actually seeing a 23%
increase in revenue per page using fewer ads when comparing
their AMP pages and non-AMP pages. Now, this might not be
everyone’s experience. You really have to
optimize the experience to get the monetization
results that you want. Going back to that 3x metric,
where does it come from? Obviously, there
are some elements that just the entire corpus and
traffic to AMP pages has grown. But it’s not all there is to it. So the AMP team,
my team, has been working really hard
in making things that are good for monetization
be available in AMP, but along those
user-first principles. So for example, one of
the biggest things in AMP is that we don’t want stuff to
jump around while it’s loading. And so multi-size ads is
like the absolute opposite that you would ever want to do. However, we say if
it’s below the fold and it’s happening
before the user sees it, it’s totally fine. So we’ve now enabled this in
a way that’s good for users. Single-request architecture is
a way to kind of make certain regular [INAUDIBLE], et cetera. It’s just there. Now, you make more money. Great. There’s fluids ads, auto
refresh, and video ads. And then finally,
a technology we call RTC, or Real-Time Config. And that is actually
something I want to dive a little bit deeper in there. You might even put, like a
hell freezing over slide here, because it’s actually
a first-class way to do header bidding in
AMP in a way that does not impede user experience. And in a way that does
not expose the site to additional security holes. So this is something
we really want to encourage you to try out. It’s available today for
DoubleClick for Publishers together with AppNexus as
an app bidding back end. And then finally, you can
use it for other purposes, like audience
targeting and so forth. I’m actually not so much
of an advertising expert, but the actual experts
are here tomorrow at 11:00 AM talking about AMP is helping
the open web stay sustainable. Cool. This is all I wanted to
talk about on the ad side. For the analytics bit of this,
I actually have more of a PSA. So I think many of you who have
done some AMP development have like found this to be true. It’s pretty hard sometimes
to track user journeys when going from your AMP pages
to your non-AMP pages and back and forth. And there was actually
a talk this year– at AMP Conf last
year about eBay, who really nicely
expressed how they– and the AMP got to make it work. But it’s actually
quite easy today. There is a fix for this, at
least in Google Analytics. So you can take out your phone
and take a picture of this link if you haven’t actually
installed this fix yet. It’s something you have
to opt-in your site. If you do it, suddenly your
metrics become more correct. So I really encourage
you to do this. Again, this is a Google
Analytics-specific thing. If you happen to work for a
different analytics vendor, you can please come talk to us. You can use the same technology. And then also, later
this year we’re making the same underlying
API available to all of you. So that you can, for
example, hook it up to your in-house
analytics system. Everyone gets the picture? It’s the most exciting slide. Well, moving on from
this topic, what I want to spend a little
bit of time talking about the wider AMP ecosystem
and the various facets around it. The first part of it
are the platforms. So these are the websites,
and apps, and web apps, et cetera, that drive
traffic to your AMP pages. And obviously, we’d like
to see more of them. So it’s like the LinkedIns,
the Bings, the Feedlys, the Flipboards, the Mediums,
the Yahoos, the Pinterest, and so forth. And there’s Google on there. So we really like to see
this grow year over year, because basically
with every new logo, you get more traffic
without doing anything. So it’s great. There’s actually one
logo missing here. That’s on the next slide. I’m particularly
excited about that one, because it’s an app that I
happen to use quite a bit. Sometimes, two to four hours a
day, I think, which is Twitter. They launched support for
linking to AMP pages last year. And this is actually
the first time that they are releasing
statistics about it. So what they were seeing
is a 10% reduction in page load abandonment
when comparing AMP pages to non-AMP pages. What does it mean for you? Basically, this metric
has dramatic impact on all downstream metrics. So if you, for example,
want to optimize time on-site or
conversion rates, obviously those
will not be great if someone never actually
manages to load your page, but abandons it right away. So I think it’s a very
impressive metric. Moving on from the platforms,
the next important aspect of the AMP ecosystem
are the CMSes. I think we’ve been seeing a
healthy CMS ecosystem develop over the last years. This is particularly true,
obviously in publishing. And I think the news trend
is that the e-commerce CMSes, shopping platforms, et cetera,
are moving into AMP support. So it’s great to see Magento
and BigCommerce on board. One particular topic I wanted
to spend some time on though is WordPress. They were one of the earliest
partners on the AMP project. In fact, when basically
we first launched, one of the easiest
ways to get AMP support was to install the AMP plugin. And being very early, it had
some limitations, which I think is to be expected. But there has been really,
really nice momentum going months over months of
improvements of this plugin. So there’s now support for
pages, widgets, custom post types, and all kinds
of standard embeds, as well as direct integration in
the standard templating system. And there is master
releases, so this is getting better all the time. In fact, we have here today
a video from Matt Mullenweg, who was the creator of WordPress
and the CEO of Automatic, talking about how AMP and
the WordPress ecosystem are working together. Can we roll the video? By the way, he’s on vacation. [VIDEO PLAYBACK] [END PLAYBACK] MALTE UBL: Thank you very much. Yeah, so he is actually on
like, some tropical island and made this video. So really appreciate it. Yeah, so it’s great to see
that progress on that front. There’s one other aspect of the
ecosystem I want to talk about, which is
super-important, which is the feedback the community
has been giving about AMP. And there’s been
one particular topic that people are pretty
passionate about. Been a couple of
tweets over the years, but people aren’t like the
biggest fans of the AMP URLs, the google.com/amp. And the thing is that we
actually totally agree. I think we’ve talked
about why it’s there for privacy, preserving,
pre-rendering, and respective good performance. And the thing is
that we’ve always said we need it for
technical reasons. When those technical
reasons are removed, we could get rid of it. And so we’re super-excited that
there is a new technology that came out about a year
ago as a new web standard called Web packaging,
which happens to be absolutely the
perfect fit to enable the same kind of privacy
preserving pre-rendering that AMP provides in a way that
preserves the actual origin of the content. And so with that, we
are excited that we can get rid of the URL prefix. We announced this
in January this year that we’re working on this. So there has been some
significant progress. The Chrome team has sent
their intent to implement, which means they have officially
started the implementation. And my team has been
starting to work on actually serving this content. So we’ll keep you
posted on the progress, but it’s going to
be a bit of a road. In fact, Chrome and the AMP
team have been working together on quite a few initiatives. Basically, along
the lines of saying, AMP got a few things right. Why don’t we make those
available to the wider [INAUDIBLE] platform? To learn more about
that, check of the talk today at 3:15, where
the Chrome team is talking about how they
work together with us to make the web better. All right. The last aspect of the AMP
ecosystem I wanted to touch on is the AMP GitHub community. And I thought that given that
it’s Valentine’s Day tomorrow, it was appropriate to put
a few hearts on the slide. Because we really have to
thank all of you who help us build AMP. I have my team working full
time on AMP, which has not have come as far without
the tremendous support, both in terms of code,
filing issues, et cetera. It’s just incredibly important. And so thank you very much. I wanted to give a
bit of statistics about how that’s actually going. So there’s now over 560
unique contributors across all our open source projects. And I’ve been asked like, how
many of them work for Google? It’s actually 22%,
which I actually think is incredibly high. So there’s apparently, over
a hundred Google employees who have changed code in AMP. I don’t know them all
by name, for sure. So that’s kind of cool. But yeah, so definitely
78% of contributors don’t work for Google. However, obviously like
my team is full-time, so they write the
majority of the code. So about 90% of the code. This is something I think
we are both proud of, but we also would like us
to extend the contribution from non-Google contributors. And we’re doing a few
things to help with that. So one of them is that
we have a weekly hangout. So if you have any
idea of a change you want to propose to AMP, you can
file that in the GitHub issue and say, hey, I would
like to talk to us. And join us on the hangout. We’ve actually recently changed
this in terms of timing. So on a week-by-week
basis, it changes the time so that if you previously
thought like, I really would like to join it,
but it’s at 3:00 AM, you can now possibly
actually join it. Because there will be one
time where it’s actually in your time zone. If you’re interested
in contributing to AMP, please check out
the talk tomorrow at 4:30 PM that goes
deep into what you can do and how it’s easy
to get started. All right. That was all I wanted to talk
about in terms of ecosystem. And almost everything
in general, but there is actually
one more thing. I think we’ve talked about how
the AMP ecosystem is evolving and how it’s
evolving on the web, but I would say
there’s possibly a way to kind of push the envelope
if you want to put it that way. Give you a bit of a
history lesson, actually. The original code
name for this project was Portable Content
Unit, short PCU. And the idea was
basically that you could publish a piece
of content and control how it’s styled,
branded, monetized. But then, allow the
platforms across the web and apps to
distribute it for you. And I think it was a great idea. The implementation is fine. And it’s working well
in search engines, like Google or in
Twitter, and so forth. But I think we’ve only kind
of scratched the surface because content is
not only distributed in websites or in apps. There’s at least one
other way to do it. And in fact, that
one is happening 270 billion times a day. That is the number of
emails that are sent today. And with that, I’m super-excited
to announce that AMP is, in fact, coming to email. To learn more about what this
means, please welcome on stage Aakash Sahney, who is the
Product Manager on Gmail. [APPLAUSE] AAKASH SAHNEY: Thank
you very much, Malte. My name is Aakash Sahney. I’m a Product Manager on
the Gmail team at Google. So AMP is coming to email. Sounds cool, but what
exactly does that mean? So with AMP in
email, you can now include AMP components
inside of your email messages across all platforms. We’re really, really excited
about the possibilities here. You’ll be able to
send more interactive and engaging and actionable
emails than ever before. Your messages can include
many of the AMP components that you know and love, like
carousels and accordions. They can even update using
data from external services with features like
AMP Bind and AMP List. So I’ll give you a
couple of examples of what you can actually do
inside of AMP-based emails that we’re really excited about. But we’re really excited to
see what you build as well. So imagine that you could
complete tasks directly inside of your email. So with AMP for email, users can
quickly take actions on things like RSVPing to an event,
scheduling an appointment, or answering a
questionnaire right directly from their email. Emails can even be
kept up to date, so that when you open a
news update like this one, you can see the latest articles,
weather, and stock prices right there in your inbox. So as we’ve heard
today, AMP started as a tool for publishers
to build very fast-loading mobile web pages, but
it’s evolved a lot over the last several years. Or, I guess the last
couple of years. And it’s now one
of the best ways to build all kinds of
more general web pages. So we’re really excited about
the flexibility and the power of AMP and the opportunity that
it presents inside of email. So today, we’re publishing a
proposed spec for AMP in email that you can find on the
AMP Projects GitHub page. And we’re also announcing
a developer preview inside of Gmail. And we’re inviting
sign-ups starting today. We’re planning to launch this
to Gmail users later this year. So with the developer
preview, you’ll be able to start building and
testing your own emails inside of Gmail and send them
to users later this year. We have a lot more to tell
you about how this all works, and some really
exciting demos to share. So please, join me at
2:00 PM today for a talk to go into more
detail and learn more. Thanks very much. [APPLAUSE] MALTE UBL: That was cool. [INAUDIBLE] do now
is kind of wrap up. We learned today
about AMP Stories, how AMP is ready for
e-commerce, that you can have success with ads in AMP. The growth of the AMP
ecosystem and community. And then finally, that
AMP is coming to email. Please all join us in
building the user-first web. Thank you very much. You have two exciting
days ahead of you. Thank you very much, everybody,
for watching on the Livestream. And don’t forget to subscribe. [MUSIC PLAYING]

2 thoughts on “Keynote (AMP Conf 2018)

Leave a Reply

Your email address will not be published. Required fields are marked *