Prototyping Motion and Material Design - Designer vs. Developer #23

Mustafa speaks to Nick Butcher, Design and Developer Advocate at Google, about motion design, prototyping and the three layers of material design.
Designer Vs Developer is a show that tries to solve the challenges faced in the industry by opening a conversation between the two, providing takeaways, solutions to workflows, tools & discussions on everyday struggles.
Watch the rest of the series here → bit.ly/2sXpWBR
Subscribe to the Chrome Developers channel → bit.ly/ChromeDevs1
Learn more about the subjects mentioned in our video:
Animating on schedule
bit.ly/2ysuKB6
Lottie motion library
bit.ly/2C88nED
Plaid on GitHub
bit.ly/2pMftXT
How to design your own design system
bit.ly/2QJIMG7
For unedited conversations subscribe to or download our podcast from these services;
iTunes: goo.gl/1E9U0G
Google Music: goo.gl/qCBlST (USA ONLY)
Web Fundamentals: goo.gl/Kt3nE9
Feedburner: goo.gl/USHXv8

[@Mustafa-ux]

Special thanks to Nick Butcher for appearing in this episode. IF you have any questions or comments, please feel free to add :)

[@ajdink.]

when will google play music get new material design v2 like other google app (chrome , photos ... etc )

[@henrypostulart]

Over the decades of the web, designers and developers have struggled through the evolution of various details of their respective crafts. From typography through image formats and palette specifications there’s been a growing synchrony of objectives, understandings and tool development. Motion, it seems to an old veteran like me, is just another stage in the ongoing process of understanding and mastering our crafts to better serve both our users and our employers. Nothing new here, just more ways to do our jobs more effectively.

[@smithshelke2036]

This is so true! When spent so much time developing a transition in code, I don't feel like throwing it away, even though the transition doesn't make much sense.

[@TheNewton]

Too much high level theory with jargon that's mainly accessible to people that already know most those things. So about prototyping motion...how? what tools? what's the workflow like? Daily struggles? Do you just code everything in a big syntax timesink? Use something like flash to make animation in a proprietary format but export to code/gif/video? How do you test something so visual for consistency? Does the designer know enough code to get it into whatever is the flavor of the month framework or is the dev teams problem?

[@davidhsv2]

Best episode so far!