WEBVTT

00:00:00.120 --> 00:00:01.520
Thanks for watching Techquickie.

00:00:01.520 --> 00:00:05.920
Click the subscribe button, then enable notifications with the bell icon so you won't miss any

00:00:05.920 --> 00:00:07.560
future videos.

00:00:07.560 --> 00:00:11.960
So mobile internet sure has come a long way since the days of downloading sick ringtones

00:00:11.960 --> 00:00:13.480
to our flip phones.

00:00:13.480 --> 00:00:17.280
But using a browser on the latest smartphone still presents some challenges.

00:00:17.280 --> 00:00:21.400
Clunky advertisements that take up the whole screen right as you're about to scroll down,

00:00:21.400 --> 00:00:26.200
poor responsiveness caused by too much page clutter, and spotty connections in some areas

00:00:26.200 --> 00:00:28.640
that can all be incredibly frustrating.

00:00:28.640 --> 00:00:32.980
And all of these issues were the inspiration for Google's AMP project, something you've

00:00:32.980 --> 00:00:36.360
probably taken advantage of without even realizing it.

00:00:36.360 --> 00:00:40.480
You see, whenever you run a Google search on a mobile device, you might notice a small

00:00:40.480 --> 00:00:44.640
lightning bolt icon beside a given search result to let you know that if you click on

00:00:44.640 --> 00:00:48.160
it, you'll be served an AMP version of that page.

00:00:48.160 --> 00:00:51.680
Now this page won't come to you directly from the site you're trying to view.

00:00:51.680 --> 00:00:56.260
Instead, after the administrator of the site creates an AMP version of the page, it'll

00:00:56.260 --> 00:00:58.620
be automatically pushed to a CDN or console.

00:00:58.620 --> 00:01:01.860
You'll see that the AMP version of the page will be pushed to a CDN or console, and the

00:01:01.860 --> 00:01:02.860
CDN will be pushed to a CDN or console.

00:01:02.860 --> 00:01:06.500
These AMP caches then push the page to your phone, with the goal of improving loading

00:01:06.500 --> 00:01:07.500
times.

00:01:07.500 --> 00:01:11.220
But this isn't the only difference between an AMP and a regular page.

00:01:11.220 --> 00:01:15.700
If one of your favorite sites often takes a long time to load, the culprit may not be

00:01:15.700 --> 00:01:17.620
a server with a slow connection.

00:01:17.620 --> 00:01:22.340
Instead, there might be complicated HTML elements that take a long time for your browser to

00:01:22.340 --> 00:01:27.840
render, poorly written CSS that makes the page look like a mess, or scripts that ask

00:01:27.840 --> 00:01:28.200
for more resources than you need.

00:01:28.620 --> 00:01:35.940
So instead of allowing website owners to design their pages however they want, AMP uses its

00:01:35.940 --> 00:01:40.680
own customized and stripped-down versions of HTML and JavaScript.

00:01:40.680 --> 00:01:45.240
These prevent the implementation of layouts that are slow, clunky, or disruptive to the

00:01:45.240 --> 00:01:48.420
user, like the dreadful full-screen ads I mentioned before.

00:01:48.420 --> 00:01:52.980
In fact, one of AMP's built-in restrictions is that ads can only take up a certain amount

00:01:52.980 --> 00:01:54.540
of space on the screen.

00:01:54.540 --> 00:01:56.200
You'll still see them, of course.

00:01:56.200 --> 00:01:58.380
But an AMP page should mostly be the actual content.

00:01:58.380 --> 00:02:01.800
It should be the content you want to see, rather than the scammers screaming at you

00:02:01.800 --> 00:02:05.360
about a fat-busting juice cleanse.

00:02:05.360 --> 00:02:09.920
And AMP is also smart enough to judge the relative importance of each element of the

00:02:09.920 --> 00:02:10.880
web page.

00:02:10.880 --> 00:02:14.580
So if you're trying to read an article about the latest big scandal, it'll try to load

00:02:14.580 --> 00:02:20.860
things like the article text and an unflattering picture of your local politician before, say,

00:02:20.860 --> 00:02:24.460
an ad that you won't see until you scroll to the end of the page.

00:02:24.460 --> 00:02:28.600
Combine all of this with limiting other resource-hogging effects like animations, and it's going to

00:02:28.600 --> 00:02:34.240
end up doing a pretty decent job of making the mobile browsing experience less rage-inspiring

00:02:34.240 --> 00:02:35.240
overall.

00:02:35.240 --> 00:02:37.840
Now, it does have its limitations.

00:02:37.840 --> 00:02:41.640
The restrictions on page elements and style mean that it works best for news articles

00:02:41.640 --> 00:02:46.560
consisting of mostly text and a few still images, rather than highly interactive websites

00:02:46.560 --> 00:02:49.340
more suited to a desktop browser.

00:02:49.340 --> 00:02:53.020
But if you are doing lots of your browsing on mobile, see if you notice a difference

00:02:53.020 --> 00:02:55.060
the next time you load up an AMP page.

00:02:55.060 --> 00:02:56.880
After all, this new world of constant connectivity has gotten us all into a situation where we're

00:02:56.880 --> 00:02:57.880
not able to read and write.

00:02:57.880 --> 00:02:57.920
We're not able to read and write.

00:02:57.920 --> 00:02:57.960
We're not able to read and write.

00:02:57.960 --> 00:02:57.980
We're not able to read and write.

00:02:57.980 --> 00:02:58.040
We're not able to read and write.

00:02:58.040 --> 00:02:58.080
We're not able to read and write.

00:02:58.080 --> 00:02:58.120
We're not able to read and write.

00:02:58.120 --> 00:02:58.160
We're not able to read and write.

00:02:58.160 --> 00:02:58.780
We're not able to read and write.

00:03:00.200 --> 00:03:03.460
We've gotten all amped up on instant gratification, so, if it can be slightly more instant, so

00:03:03.460 --> 00:03:05.160
much the better, right?

00:03:05.160 --> 00:03:06.820
Are you interested in computer science?

00:03:06.820 --> 00:03:11.180
Then, check out Brilliant, a problem-solving website that teaches you to think like a computer

00:03:11.200 --> 00:03:12.260
scientist.

00:03:12.260 --> 00:03:16.720
Instead of passively listening to lectures, you get to master concepts by solving fun

00:03:16.720 --> 00:03:21.100
and challenging problems, and Brilliant provides the tools and framework you need to tackle

00:03:21.100 --> 00:03:22.040
these challenges.

00:03:22.040 --> 00:03:26.540
Brilliant's thought-provoking content, based around breaking up complexities into bite-sized,

00:03:26.540 --> 00:03:27.540
understandable chunks, will lead to you finding a tool that disappears your bottlenecks.

00:03:27.540 --> 00:03:27.600
But you can do a full 84 hours of data analysis of a things that actually help make a difference

00:03:27.600 --> 00:03:28.140
and a thing that doğnik I will leave shift to.

00:03:28.140 --> 00:03:32.960
from curiosity to mastery, and you'll be in the company of over five and a half million

00:03:32.960 --> 00:03:36.140
members who share your curiosity and love for math and science.

00:03:36.140 --> 00:03:37.200
So what are you waiting for?

00:03:37.200 --> 00:03:40.440
You can support Techquickie and learn more about Brilliant by clicking the link down

00:03:40.440 --> 00:03:45.520
in the video description or going to brilliant.org slash Linus Tech Tips and signing up for free.

00:03:45.520 --> 00:03:50.300
The first 200 people to go to the link will get 20% off an annual premium subscription,

00:03:50.300 --> 00:03:51.780
so be sure to check it out.

00:03:51.780 --> 00:03:53.580
Okay guys, thanks for watching Techquickie.

00:03:53.580 --> 00:03:56.940
Like, dislike, check out other channels, leave a comment down below with your suggestions

00:03:56.940 --> 00:03:59.040
for future videos, and don't forget to subscribe.
