The bit about RWD becoming "boring" is very historically accurate. I try to use it in all my projects, but over the years I've noticed major companies trying and then bailing a fully responsive production solution.
Awesome! Currently working on PWA and Ade is god damn right. Thank you for the pwa-directory.appspot.com reference. This show is becoming my favorite youtube show.
I loved the way this discussion ended: As designers and developers, we _do_ have to make sure the Web doesn't lose its soul as we progress in the digital age. I am concerned day by day that soulless content is taking over ideas and aesthetics.
Impressive talk. Very centered on web app vs. native app dilema. I been working on making native desktops apps for web and just hidding url, links to other sites, etc. I rather just do a native app. I feel compelled to actually do a web site.
It does if you need to recreate an enterprise app on web. In my case, links, visible urls, going to other websites, etc. are limitations and problems that need to be removed.
In my mind hyper textuality is what makes the web, the web. A hyper link or a hyper reference (href) is a link from within a particular web site to an external web site. It is what connects web sites to each other. A PWA shrouds this aspect by appearing as a native app (no address bar and launching from the home screen for instance), and thus encouraging the act of staying within a particular app, making it appear less connected, less web-like.
I think he does explain it pretty well at 8:18 in the video. Instead of saying 8:18, I could use a more hypertextual way and said go to this link th-cam.com/video/J8Hj5bIYuYA/w-d-xo.htmlm18s. I could give you a link instead of telling you where to go. Native apps don't have url bars. Getting rid of the url bar may look a little cleaner, but you are sacrificing a huge (UGE) amount of functionality. PWAs are great as long as we don't completely abandon the web in order to make our web apps look more native. Native is cool, but it's not weblike. It's more confined into an app that restricts web linking because we eliminate the url bar. Url bars do provide challenges in single page web applications, however, with powerful frameworks like Angular and React...and many others, this functionality can be added quite easily. Great question.
Well said. I like PWAs and SPAs, but not to the point that they become restrictive. Hypertext linking is what makes the web great. Not sure why anyone would want to abandon that for a slick looking web app.
Re: #t=8m18s Exactly right! Fragment URIs enable a new way of using the Internet and viewing knowledge and the world, really. It's a big part of the original vision for the Web, which aimed to evolve into a hyper-connected nexus of knowledge that is easy to navigate, discover and compute. I used to store culture snippets in the form of TH-cam fragment links (an embed URL with ?start and ?end params). They could have been used in an audio/visual performance, and when the audience were curious about this or that they could get the rest of the video, and go on to make their own mashups, and so on. Now TH-cam removed frame-accuracy from fragment links and you can't do that anymore (no sub-second timestamps). But there are still people working tirelessly on web standards in accordance to the vision, doing more for our freedoms and wellbeing than many dream. I cannot thank them enough!
Why does it have to be vs tho? so combative.. Designer & Developer "..The TH-cam App .. Interfaces that expose the functionality" oh no no noo.. I will never abandon responsive because of a fickle trend shift and I'm not a designer, I'm a programmer by trade..
The bit about RWD becoming "boring" is very historically accurate. I try to use it in all my projects, but over the years I've noticed major companies trying and then bailing a fully responsive production solution.
Awesome! Currently working on PWA and Ade is god damn right. Thank you for the pwa-directory.appspot.com reference. This show is becoming my favorite youtube show.
thank you!
I loved the way this discussion ended: As designers and developers, we _do_ have to make sure the Web doesn't lose its soul as we progress in the digital age.
I am concerned day by day that soulless content is taking over ideas and aesthetics.
Great dialogue!
Impressive talk. Very centered on web app vs. native app dilema.
I been working on making native desktops apps for web and just hidding url, links to other sites, etc. I rather just do a native app. I feel compelled to actually do a web site.
It does if you need to recreate an enterprise app on web. In my case, links, visible urls, going to other websites, etc. are limitations and problems that need to be removed.
Love this series!
Great talk, thanks for the responsive design link =]
Sen adamın dibisin Mustafa
Could someone expand on what he means by hyper textuality?
In my mind hyper textuality is what makes the web, the web. A hyper link or a hyper reference (href) is a link from within a particular web site to an external web site. It is what connects web sites to each other. A PWA shrouds this aspect by appearing as a native app (no address bar and launching from the home screen for instance), and thus encouraging the act of staying within a particular app, making it appear less connected, less web-like.
I think he does explain it pretty well at 8:18 in the video. Instead of saying 8:18, I could use a more hypertextual way and said go to this link th-cam.com/video/J8Hj5bIYuYA/w-d-xo.htmlm18s. I could give you a link instead of telling you where to go. Native apps don't have url bars. Getting rid of the url bar may look a little cleaner, but you are sacrificing a huge (UGE) amount of functionality. PWAs are great as long as we don't completely abandon the web in order to make our web apps look more native. Native is cool, but it's not weblike. It's more confined into an app that restricts web linking because we eliminate the url bar. Url bars do provide challenges in single page web applications, however, with powerful frameworks like Angular and React...and many others, this functionality can be added quite easily. Great question.
Well said. I like PWAs and SPAs, but not to the point that they become restrictive. Hypertext linking is what makes the web great. Not sure why anyone would want to abandon that for a slick looking web app.
Re: #t=8m18s Exactly right! Fragment URIs enable a new way of using the Internet and viewing knowledge and the world, really. It's a big part of the original vision for the Web, which aimed to evolve into a hyper-connected nexus of knowledge that is easy to navigate, discover and compute. I used to store culture snippets in the form of TH-cam fragment links (an embed URL with ?start and ?end params). They could have been used in an audio/visual performance, and when the audience were curious about this or that they could get the rest of the video, and go on to make their own mashups, and so on. Now TH-cam removed frame-accuracy from fragment links and you can't do that anymore (no sub-second timestamps). But there are still people working tirelessly on web standards in accordance to the vision, doing more for our freedoms and wellbeing than many dream. I cannot thank them enough!
Why does it have to be vs tho? so combative.. Designer & Developer
"..The TH-cam App .. Interfaces that expose the functionality" oh no no noo..
I will never abandon responsive because of a fickle trend shift and I'm not a designer, I'm a programmer by trade..