So, my name is Surma I work for Google in London and I'm a developer advocate for Chrome and in general the web platform
Mobile websites are just a really
direct way to get a user into
Your experience whatever you want to offer to them because there's no installation process. There's no
Requirements for the system you just open up and they start working right away
And that's so frictionless that it turned out to be super good at convincing to just took take a closer
Look at what you have to offer
And it's a really good platform. And that's why Google has been working on that to make it even more powerful
So, I think I feel there's been a lot of confusion around the PWA buzzword because
It's not that you have to use a certain technology to be a PWA. It's mostly about improving the users experience
So make your app work
Well, even when the network is flaky, be high-performance, have a good visual representation and be smooth in your animations
all these little things that make the user feel
Like they're actually using an app rather than just a scrolling document
and
That is just what pwa is really about and part of that are the new technologies on the web that make achieving this goal
Easier than it has been in the past
So luckily I my job basically is to be a web developer
so I just build things and I just
tend to use what developers use to figure out why it is so appealing to them and then try to figure out
What of these things need to remain as a tool and one of these things could actually part off the web platform?
so I've been playing around with web hack and with react but also just trying to
rebuild what these frameworks and tools are doing by just using vanilla JavaScript and whatever there is on the platform and
Trying to account if it is
faster that way or slower that way or more painful to use that way and figuring out the differences and so I just
Have an editor. I have a web server and I just build things and see where I end up
So as I said, I try new things all the time but one of my focus is for the next couple of months
I guess is that I want to
build web apps that
Have work off the mains right that sounds a little bit ominous. But basically I want my browser experience to always be responsive
I don't never have the feeling that I'm scrolling and nothing is happening
It should always respond immediately. And that is one way of achieving that and in connection with that. There is devices coming out that have
120 Hertz screens, which is fairly new but that means you have even less time to do any calculations on a device
So you need to write really code in a very specific way
to have this really high frame rate which makes a big difference in how the app appears so you can really tell the difference if
a device is running at 60 or 120 Hertz and
Kind of 20 just seems so much more smooth that you really want to try to get there
I
Think that it's a massive space that is really hard to like just wrap your head around
It's a lot of exploration that have to be done
I think in terms of UI and UX design both
voice based interfaces and augmented reality are a completely new perspective on what we've done so far because on the one hand you now have
to represent information in a
Audible way and also take audio as input which hasn't usually have touch input or mouse input and now it's voice
So that's interesting because there is no drag-and-drop with voice for example. So, how do you do things?
Augmented reality. You have the real world and you try to overlay information. It's useful but not overwhelming to the user
there's lots of exploration has to be done and
machine learning is super interesting just in the sense that on the one end you have a huge responsibility of
Removing biases and making sure that it doesn't go strain on the other hand
You don't really understand how it's working just that it is working. It can be super powerful, but I don't quite know
How much it's gonna affect the web just yet
If I feel in long run, it definitely will but it's really hard to wrap my head around it just now