Stay organized with collections
Save and categorize content based on your preferences.
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 and
discussions on everyday struggles.
Mustafa speaks to Rowan Merewood, Developer Advocate for Chrome
Developer Relations team, about Payments on the web, Progressive
web apps and how to think about designing for offline states.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-06 UTC."],[[["\u003cp\u003eThis episode of Designer Vs.Developer focuses on web performance, payments, progressive web apps, and designing for offline experiences.\u003c/p\u003e\n"],["\u003cp\u003eThe discussion includes practical examples like Amazon's approach to performance and considerations for CMS platforms like Drupal and WordPress.\u003c/p\u003e\n"],["\u003cp\u003eRowan Merewood, a Developer Advocate from Chrome Developer Relations, shares insights on these topics with host Mustafa.\u003c/p\u003e\n"],["\u003cp\u003eResources and further reading are provided on offline UX, Trivago's case study, and Navigator.onLine.\u003c/p\u003e\n"],["\u003cp\u003eYou can subscribe to the podcast on Spotify, Feedburner, iTunes, or Google Music, and watch the video recording on YouTube.\u003c/p\u003e\n"]]],["Mustafa and Rowan Merewood discuss web payments, progressive web apps, and designing for offline experiences. Key topics include designing for performance, incorporating performance into workflows, and working with CMS platforms like Drupal and WordPress. The conversation also touches on offline UX considerations, with a Trivago case study cited. Links to related resources on offline UX and Navigator.onLine are provided for further learning.\n"],null,["# Rowan Merewood on designing for offline\n\nWelcome to Designer Vs. Developer, a show that tries to solve the\nchallenges faced in the industry by opening a conversation between\nthe two, providing take aways, solutions to workflows, tools and\ndiscussions on everyday struggles.\n\nMustafa speaks to Rowan Merewood, Developer Advocate for Chrome\nDeveloper Relations team, about Payments on the web, Progressive\nweb apps and how to think about designing for offline states.\n\nIn this episode:\n\n- Designing for performance\n- Examples of Amazon\n- Building performance into your process\n- Working with CMS's like Drupal and Wordpress\n- [Offline UX Considerations](http://bit.ly/2LvNkl2)\n- [Trivago case study](http://bit.ly/2K5I8is)\n- [Read about Navigator.onLine](https://mzl.la/2vaRjsm)\n\nSubscribe to Designer Vs Developer Podcast via\n[Spotify](https://bit.ly/MustafaOnSpotify)\n[Feedburner](https://goo.gl/USHXv8),\n[iTunes](https://goo.gl/1E9U0G) Or\n[Google Music](https://goo.gl/qCBlST)\n\nWatch [the video recording](https://www.youtube.com/playlist?list=PLNYkxOF6rcIC60856GnLEV5GQXMxc9ByJ). \nWas this page helpful? \nYes \nWhat was the best thing about this page? \nIt helped me complete my goal(s) \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt had the information I needed \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt had accurate information \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt was easy to read \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nSomething else \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nNo \nWhat was the worst thing about this page? \nIt didn't help me complete my goal(s) \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt was missing information I needed \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt had inaccurate information \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nIt was hard to read \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new). \nSomething else \nThank you for the feedback. If you have specific ideas on how to improve this page, please [create an issue](https://github.com/google/webfundamentals/issues/new)."]]
