Creating UX that “Just Feels Right” with Progressive Web Apps (Google I/O '17) 

A Google Developer talk that mentions Material UI for React and fails to mention Angular Material, very strange (@17:35)

The transition at 7:14 (ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-mmq-KVeO-uU.html) "just feels !right" 😥

His mom must be so proud! sheesh

This talk makes web development seem like a walk in the park

Zayn Malik.switched career.

Owen is a terrific product evangelist.

this is why companies go native. And build best animations with best speed with best user experience. With even all of this you can't do shared element transition (elements from one page animate and become part of next page)..

I've been wondering. What happens when two people with hyphenated last names marry? Does both their last names become a 4-tuple and so on in perpetuity? Or maybe their parent's names become a cute portmanteau and they just form a hyphenate from the two synthesized names? I think that'd be awesome!

you should send this to the youtube devs

Cannot use Service workers with Hybrid Cordova Android :( Or can we? This seems crazy. Even can use on iOS now with plugin

Very usefull, thanks

I learned today 🍎

interesting!

What happened to the angular-cli --mobile option for PWA projects? It was an option and then removed when the angular-cli went to version 1.0.0. What should Angular developers use to build PWA's? Ionic? or the Create React App?

does Google really has the world's best developers as mentioned ?

The hoodie whats the label

This ripple effect on buttons is a total overkill. Why doing the animation via adding classes with javascript when you could do it with the “:active” pseudo class and CSS only?

huh. is this a talk from I/O 16? I'm pretty sure Ive seen all this about 27 times already...

@27:11 Ugh, I hate full screen explanations. It assumes the user is dumb/ignorant and don't know that on news site you get news notifications, same on video site, your subscriptions and recommendations. And on slow phones and networks it usually works that way: you see interesting article, you read it while the rest of site is loading, then it freezes for a few seconds, trashes your screen and shows fullscreen explanation. You're pissed, more so if when you click close button, the site reloads and jumps to the beginning of the article. At least twitter shows it when you click notifications icon for the first time. But when I click it I expect to see my notifications not some fancy fullscreen dialog. It would be better if it showed dialog on the bottom. You read from the screen top to bottom anyways, so if it's resonably sized it won't block your text visibility too much. And if it's overlayed on top it won't move content you're reading out of the way. It's then simple, non intrusive and in context.

No ablo ingles pero le dije qué no y me pidieron opinión de como crear un apa y fue cundo use java llo pensé que era de Google por eso la use por que cuando usas un apa diferente ala aplicación tienes que pedir permiso y salí y me fui después me llego un mensaje de yutuve y le puse mucha atención fue que me di cuenta y fuy a ver como podía expulsar o como ayudar llo nunca corro a un reto llo no siempre voi a seguir el camino correcto el dinero no es más que eso la onestidad es primero aunque muera por ella

Mr. Dev, I don't feel so good

Perdón voi a seguir el camino correcto

react is not a framework. Google people seem to often make this mistake.

Google Design talk and not even at least 1080p in 2017? Hah.

There is no UX that feels "right" in a PWA. Just leave it in a website if you can't be bothered to build a native app. I'm tired of all of these websites being boxed in a wrapper and called an app. It's so lazy and it just doesn't utilize the OS you're using. Imagine having a disability and trying to use your Macs Accessibility features only to find they won't work with Teams, Slack, or some other website pretending to be an application. It's not native. I really wish they'd stop calling it "native" just because it has node and system hooks or a "native" bridge in React.

You can't make a good user experience for progressive web apps. You need to figure out what the user is trying to achieve and build either a native app or website to meet that need. PWAs get new features all the time but they still don't have unique features that regular apps and sites don't already offer the user. There is literally no point in trying to developing something new to do something a regular website or a real app can already do.

Africa is a country ...