[MUSIC]
>> When am thinking about a mobile app,
I'm thinking about something that's going to be
able to access for example,
storage, or the camera,
or the file system, or the microphone,
call history, GPS, the location.
I'm thinking of all of those different things,
that a mobile app is going to want to be able to access.
Will a PWA have access to all of those as well?
>> Do they feed you-all these questions?
I'm going to take this question in two parts.
One is today if you wanted to do that,
you might go down the path of using a hybrid app,
like ionic and people
who give you a container that you
run your web app in, so to speak.
But they then have the native hooks that they surface up to you.
There's that option if you want to do that.
But with PWAs, yes, absolutely.
I think this is what I was going to talk
about the Project Fugu and I should have.
Well, let's see if I can find it.
There is this project called Project Fugu and
web capabilities that we should explore.
It's in that set of links as well.
The idea is that,
if you go with the hybrid app approach, let's say,
you're still using native APIs
directly and you're using it through someone else's framework.
You've got your operating system and the native APIs,
and you've got like some layer between you and that one.
Then you're writing a web app and you're dependent on them.
With Fugu, the idea is that the primary browser vendors are
working together to standardize JavaScript level APIs,
to those native capabilities.
I think that's the biggest challenge,
is how do we make sure that those capabilities are surfaced in
a consistent way across different vendors, first of all?
Second of all, what is the priority of those capabilities?
I think what's nice about this is,
if you look at this Fugu tracker in here,
they have a whole bunch of APIs and if you look at the right side,
they tell you who's supporting it right now,
who's looking into it, etc.
Long story short is,
I think of PWA as
a great investment for the long haul because work is in progress.
Which API is ready for cross-browser consistent usage today?
That's a little bit like watch the roadmaps.
But I think that, you mentioned file share.
What I read in the PWA builder kit,
for instance, is file share is there,
the ability to share button is there,
Web Bluetooth was one of those that came up
through this particular approach.
Depending on what APIs you're looking for,
see if they're in here,
and then look at what state they're in,
and that'll help you decide.
That said, there's always I think going to
be like niche capabilities,
that are very hardware centric perhaps.
Spatial computing, you need to have certain sensors.
I think those are going to take longer.
Is candlelight, so yeah.
>> That makes sense. I was looking
at the list as you had it up there.
At the very least, like some of the things that I think I would
most logically or most frequently want,
especially things like the camera and so forth.
It looked like, those were already there, already supported.
It looks like at the very least like that old 80-20 rule,
that 80 percent of the time you're
using 20 percent of the features.
It looks like there's a good portion of that 20 percent,
that I'm going to want most frequently,
that is supported here.
>> Yes. I also want to
just nudge attention to
the fact that when you look on the right side,
there is not just Android and iOS,
but there's Chrome and Windows.
I remember from back in the early days in PWA,
even when you had APIs like audio and camera,
the support across say
mobile Safari versus mobile Chrome, was different.
I think one of the things you have to look at
is not only is there support,
but is there support on
the platform that my audience is likely to use?
That is I think the sticky point, when I look at the dots,
there are still places where it says,
here's how 80 percent of browser vendors will do it.
But then there is this exception that
handles exception right is literally the phone.
We haven't got rid of that yet.
>> Fair enough, yeah. We're still
using vendor specific tags in CSS.
I guess we're going to be here for a while.
>> Our jobs are safe people.
Legacy code is why we all exist.