Published on April 12, 2017 by Chrome

Welcome to Designer Vs Developer, a show that tries to solve the challenges faced in the industry by opening a conversation between the two, providing take aways, solutions to workflows, tools & discussions on everyday struggles.

This week Mustafa speaks to Ade Oshineye, a Developer Advocate on the Google Developer Relations Team, about how the incorrect use of design language has influenced us to adopt the UX practices of the native app world and how the web should seek to create a native language of its own.

You can listen to an extended version of our conversation downloading our podcast here:
goo.gl/uSx6pD

Read our blog post here:
goo.gl/no4484

Mustafa is a Design Advocate at Google and has over 16 years experience working UX and visual designer. You can follow him at www.twitter.com/mustafa_x/

Lean more about the subjects mentioned in our video:

Progressive Web App Directory –
pwa-directory.appspot.com

Responsive Web Design Basics –
goo.gl/0E3wAW

Tom Formaro’s thesis –
www.tformaro.com/thesis/

Watch more Designer vs. Developer videos here: goo.gl/0GOEy4

Subscribe to the Chrome Developers Channel: goo.gl/LLLNvf

Leave a Reply

17 Comments on "Adopting the native language of the web — Designer vs. Developer #3"

Notify of
avatar

perspicaciouscritic
Guest
perspicaciouscritic
3 days 22 hours ago

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.

Ümit Ahmet Şahin
Guest
Ümit Ahmet Şahin
6 days 3 hours ago

Sen adamın dibisin Mustafa

Jan Valuštík
Guest
Jan Valuštík
14 days 6 hours ago

Very interesting ideas. I especially love the part when Ade is talking about what tools we use for designing and that these tools (like Sketch or Adobe) are still influenced by static medium – paper. That they don't give us the possibilities of responsiveness and designing systems instead of static pictures. Love that and I'm actually working on a tool that's gonna change that, if you are interested, you can check it out here: twitter.com/honzavalustik/status/850742132075773953

3m0_Wr3ck
Guest
3m0_Wr3ck
16 days 1 hour ago

Why does it have to be vs tho? so combative.. Designer & Developer"..The Youtube 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..

Виталий Шаповалов
Guest
Виталий Шаповалов
17 days 5 hours ago

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.

Mustafa Kurtuldu
Guest
Mustafa Kurtuldu
11 days 3 hours ago

thank you!

Jorge Escobar
Guest
Jorge Escobar
17 days 18 hours ago

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.

Jorge Escobar
Guest
Jorge Escobar
16 days 23 hours ago

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.

comet3bc13
Guest
comet3bc13
17 days 9 hours ago

Ricardo Escobar That makes no sense: "native desktop apps for web"

Omar Chehab
Guest
Omar Chehab
17 days 21 hours ago

Could someone expand on what he means by hyper textuality?

Lee Roy
Guest
Lee Roy
9 days 23 hours ago
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 YouTube 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… Read more »
sreid70
Guest
sreid70
17 days 13 hours ago

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.

sreid70
Guest
sreid70
17 days 13 hours ago
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 . 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.… Read more »
Mads Bruun Færch-Jensen
Guest
Mads Bruun Færch-Jensen
17 days 21 hours ago

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.

Ondřej Pokorný
Guest
Ondřej Pokorný
17 days 22 hours ago

Great dialogue!

Sam Sharpe
Guest
Sam Sharpe
11 days 10 hours ago

What dialogue this is google talking to itself?

Tim Siwula
Guest
Tim Siwula
17 days 22 hours ago

Great talk, thanks for the responsive design link =]

wpDiscuz