<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Chris Nienhuis on Medium]]></title>
        <description><![CDATA[Stories by Chris Nienhuis on Medium]]></description>
        <link>https://medium.com/@chrisnienhuis?source=rss-cf15c21a5d57------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*6DlBGW9amkCcEMUM</url>
            <title>Stories by Chris Nienhuis on Medium</title>
            <link>https://medium.com/@chrisnienhuis?source=rss-cf15c21a5d57------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:28:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chrisnienhuis/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Using Webpack Module Federation To Share An App Shell]]></title>
            <link>https://medium.com/expedia-group-tech/using-webpack-module-federation-to-share-an-app-shell-7d23633510e?source=rss-cf15c21a5d57------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d23633510e</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Chris Nienhuis]]></dc:creator>
            <pubDate>Wed, 10 Jun 2020 13:01:01 GMT</pubDate>
            <atom:updated>2020-06-10T13:01:01.009Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="https://medium.com/expedia-group-tech/software/home">EXPEDIA GROUP TECHNOLOGY — SOFTWARE</a></h4><h3>Using Webpack Module Federation to Create an App Shell</h3><h4>Keep modules in sync across different web applications at scale</h4><p>Webpack 5.0 will ship a powerful new feature for javascript application architecture: <a href="https://indepth.dev/webpack-5-module-federation-a-game-changer-in-javascript-architecture/">module federation</a> (<a href="https://github.com/webpack/webpack/commit/faa7dda8cd816cb30e25a439ac6a208a7ba2034f#diff-4e1b67b6df506eec0034b54c61d802af">committed in v5.0.0-beta.16</a>). Module federation provides several powerful architectural benefits:</p><ul><li>It keeps common modules synchronized across different web applications at scale, enabling evergreen releases and boosting performance</li><li>Teams can independently deploy updates of code they own without requiring additional releases from other teams</li><li>Works server- and client-side without any additional required code</li></ul><p>This article explores an implementation of a federated <a href="https://developers.google.com/web/fundamentals/architecture/app-shell">app shell</a> micro front-end (MFE) working with an example travel shopping experience.</p><h3>What is webpack module federation?</h3><figure><img alt="Webpack module federation logo in front of Vrbo screenshots" src="https://cdn-images-1.medium.com/max/1024/1*CfhNMWS8hclyfSW_crMa1w.jpeg" /></figure><p>Module federation allows a JavaScript application to dynamically run code from another bundle/build, on both client and server. This means that javascript applications can both consume and provide code:</p><figure><img alt="Diagram showing a consuming app interacting with other applications to obtain its modules" src="https://cdn-images-1.medium.com/max/1024/1*j8id2Z-ZeJ9kek9-pTA16Q.jpeg" /></figure><p>Any javascript application that enables this feature can be considered as a “host”. Any host application can:</p><ul><li>Expose code to be shared with other applications</li><li>Consume code from other host applications</li><li>If doing both above, the host is considered to be “bidirectional”</li></ul><p>With module federation, federated dependencies are dynamically loaded and rendered both on the client and server. If additional dependencies are needed for a federated module from a remote host, webpack will continue to download required dependencies from the remote host.</p><p>For a deeper introduction to webpack module federation, check out <a href="https://youtu.be/D3XYAx30CNc">Jack Herrington’s Overview Of Federated Modules (10 min)</a>.</p><p>Let’s apply this pattern to create a standalone MFE that shares a simple application shell consumed by the shopping experience.</p><h3>Building a federated app shell</h3><p><a href="https://github.com/neenhouse/federated-app-shell">Here’s a demo</a> of applying module federation to create a shared app shell in a travel shopping experience.</p><p>Let’s say your shopping experience consists of a search page, a property details page, and a favorites page that contains user preferences and saved favorite destinations. Those pages will likely have the same content at the top and bottom of the page (a header and a footer).</p><p>Let’s take the header and footer and create a standalone federated module called “app shell” and use webpack federation to share it with search, property, and favorite pages.</p><figure><img alt="Diagram showing a header and footer in a component that is depended on by other micro frontends" src="https://cdn-images-1.medium.com/max/1024/1*R8Sw29emDnDcbWakoWb9Rw.jpeg" /></figure><p>Let’s look at the code.</p><h3>Define the app shell</h3><p>First, we write our module resource that we we would like to share. It should render a header and footer and pass content through to its body.</p><p><strong>appshell/src/App.jsx</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1bc04f918d3603f9a66c22b7a76181db/href">https://medium.com/media/1bc04f918d3603f9a66c22b7a76181db/href</a></iframe><p>Here is our app shell with the dummy content “Your content here!”</p><figure><img alt="Screenshot of a web page with headers and footers and a placeholder reading “Content here!” between them" src="https://cdn-images-1.medium.com/max/1024/1*HKYZm0BTHvWCblDr9kMcEg.png" /></figure><h3>Expose an interface</h3><p>Let’s create an interface called StandardLayout which will act as a default app shell that renders a header and footer.</p><p>First, we write the React component which will define required properties and act as our interface. Consider this a representation of appshell/src/App.jsx.</p><p><strong>appshell/src/StandardLayout.jsx</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bfb59f1c3826e1335cc86da85f8856a8/href">https://medium.com/media/bfb59f1c3826e1335cc86da85f8856a8/href</a></iframe><p>Then we expose this component in our webpack configuration.</p><p><strong>appshell/src/webpack.config.js</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f03bea73a5f891ec590e5c5de2a6ca44/href">https://medium.com/media/f03bea73a5f891ec590e5c5de2a6ca44/href</a></iframe><p>This will expose a version of our app shell to consumers that implements what we are defining as our standard layout.</p><h3>Consume app shell from application</h3><p>Finally, we’ll consume our app shell from another application, called property.</p><p><strong>property/src/App.jsx</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e563a73271bcad354457f64ba4d7b194/href">https://medium.com/media/e563a73271bcad354457f64ba4d7b194/href</a></iframe><p>Configure the appshell remote in the webpack configuration.</p><p><strong>property/src/webpack.config.js</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/26e43f488a15bfb907011b86ec658b8b/href">https://medium.com/media/26e43f488a15bfb907011b86ec658b8b/href</a></iframe><p>Include a link to the deployed remoteEntry chunk to enable loading of the federated app shell.</p><p><strong>property/public/index.html</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c3f99943c66a7d936a66330abbf2dbe4/href">https://medium.com/media/c3f99943c66a7d936a66330abbf2dbe4/href</a></iframe><p>Here is our app:</p><figure><img alt="Screenshot of web page with same footers as before, but now with a property details page for an island resort" src="https://cdn-images-1.medium.com/max/1024/1*A7qyGU76bnRIBEVBXTYZTQ.png" /></figure><p>We can repeat this same process for search and favorites:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4X5_PzZiJ1_644eEiS9Kwg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EBTFcSe6RWum5xg_Jc8_xw.png" /><figcaption>Search and favorites pages in app shell</figcaption></figure><p>To run the demo for yourself, check out <a href="https://github.com/neenhouse/federated-app-shell">my demo application</a>.</p><h3>How does it work?</h3><p>When you run the above demo, the following servers are run:</p><ul><li>localhost:3001 — app shell</li><li>localhost:3002|3003|3004 — property details, search, favorites (uses app shell)</li></ul><p>If you access localhost:3002 (property details), you can observe how module federation works:</p><ul><li>HTML downloads and parses main.jsentry point from localhost:3002</li><li>HTML downloads and parses remoteEntry.js entry point from localhost:3001</li></ul><p>When both of these assets are resolved, the webpack container intelligently resolve dependencies at runtime and requests any remaining required dependencies from localhost:3001 to complete the app shell (vendors and StandardLayout)</p><p><em>Note: the exact details of how the webpack container resolves its dependencies are still a work in progress (see </em><a href="https://medium.com/u/cccc522e775a"><em>Tobias Koppers</em></a><em>’ </em><a href="https://github.com/webpack/webpack/pull/10960"><em>refactor of shared modules in federation plugin</em></a><em>, for example).</em></p><h3>Bonus Feature: Federated Dashboard</h3><p>Another powerful feature is the federated dashboard plugin (<a href="https://github.com/neenhouse/federated-app-shell">included in demo</a>), currently in development by <a href="https://medium.com/u/9ef1379caffc">Zack Jackson</a>. The dashboard enables:</p><ul><li>Dependency graphs for visualizing cohesion of federated modules</li><li>Dependency tables to monitor deployed versions of components and drift between consuming applications</li><li>Enables control plane for deploying new versions</li><li>Usage and health statistics of federated modules</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qoG2rjY1chrY15LXbo4xvA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gZf-4QtnEGpSSZi6sligkQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EA85RQ2Fh959Y_rpyjRj0g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BpsegiuSxXERy1W2NPzIYw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kevn_Qv3B3V8Q6g_RoSwdA.png" /></figure><p>The federated dashboard plugin looks like a key feature to enable powerful observability features and deployment controls that enable intelligent management of federated modules.</p><h3>Caveat: Immutable remoteEntry.js chunks</h3><p>Many sites (including <a href="https://www.vrbo.com/">Vrbo.com</a>™, part of Expedia Group™) optimize the download of assets using the following recipe:</p><ul><li>Upload content hashed assets to a content delivery network (CDN) (i.e., myapp.636afebbf02818aa1fa6.min.js)</li><li>Set time-to-live (TTL) to one year</li><li>Ensure web applications render links to correct content hashed assets</li></ul><p>When an application is prepared for release, assets are content-hashed and references to these hashes are stored with the web server so it can render the correct links. This ensures that clients get the optimal download performance while maintaining the ability to update them by simply updating the HTML to new CDN locations.</p><figure><img alt="Diagram showing how web servers identify CDN bundles using hashes" src="https://cdn-images-1.medium.com/max/1024/1*sQkf9c3R_-SVeWai298-XA.jpeg" /><figcaption>Building, publishing, and deploying immutable assets to end-users</figcaption></figure><p>With module federation, federated modules can be independently deployed because the implementation of remoteEntry.js provides indirection to where the assets live. The problem is that this asset itself, when named remoteEntry.js, implies a short TTL duration, which is suboptimal for the user’s performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*58H2Zs7Rn2c3ioGSu7yk0Q.jpeg" /><figcaption>Diagram illustrating linkage to remote immutable remoteEntry.js asset</figcaption></figure><p>At Vrbo.com, we’ve created an internal proposal for solving this problem by creating an asset registry that provides an API and a simple UI dashboard for managing content-hashed files. We are also making general proposals around observability and control of remote federated deployments. A system like this might be best built in the open in collaboration with other companies who have the same sorts of problems.</p><figure><img alt="Diagram showing an artifact built by CI/CD in a registry which is consulted by web servers" src="https://cdn-images-1.medium.com/max/1024/1*oy3Syc9lT9ugH1KdLvgGzg.jpeg" /><figcaption>Building, publishing, and deploying immutable assets with asset registry to end-users</figcaption></figure><p>Next steps are to reach out to <a href="https://medium.com/u/9ef1379caffc">Zack Jackson</a> (creator of module federation), who would be a key person to work with to build this sort of community solution, assuming there is demand for it. There is also an <a href="https://github.com/webpack/webpack/issues/10352">open merge proposal</a> for module federation on the official webpack repo that describes patterns to support immutable asset support.</p><p><em>Update 6/9: Caught up with Zack and he is currently developing first-class support in module federation that will enable intelligent management of assets.</em></p><h3>Advantages of module federation</h3><p>In this exploration, we created a MFE to act as a dedicated host for sharing an app shell module using module federation. Federated module architecture offers several benefits to teams:</p><ul><li>Streamlines software development lifecycle for teams that own shared code that is distributed to many different applications</li><li>Shrinks monolithic JavaScript applications that inconsistently implement common customer experiences</li><li>Enables efficient code sharing that supports universal rendering for a faster customer experience</li></ul><h3>Challenges of module federation</h3><p>Likely challenges with pursuing this kind of application architecture include:</p><ul><li>Single point of failure for rolling out new versions across sites (due to logical errors, broken interfaces, etc)</li><li>Infrastructure for monitoring these kinds of deployments requires investment</li><li>New CI/CD processes require time to mature and scale</li></ul><p>Thoughtful consideration of required engineering investment and added risk/complexity should be evaluated when considering these challenges in building support for module federation.</p><figure><img alt="Decorative separator" src="https://cdn-images-1.medium.com/max/1024/1*vsv7RejfqSHcIc2Q2awEOg.png" /></figure><p>Webpack module federation is a fresh new approach to sharing modules across applications that has exciting potential to increase developer efficiency while providing a better customer experience. Even though this feature is still new, it is already drawing a lot of attention and excitement from the web development community. A serious implementation of MFE federated applications requires careful consideration of how the remoteEntry.js chunk is deployed to a CDN and how to link to it, among other design considerations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d23633510e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/expedia-group-tech/using-webpack-module-federation-to-share-an-app-shell-7d23633510e">Using Webpack Module Federation To Share An App Shell</a> was originally published in <a href="https://medium.com/expedia-group-tech">Expedia Group Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Measuring Interaction Performance with FPS Data]]></title>
            <link>https://medium.com/expedia-group-tech/measuring-interaction-performance-with-fps-data-b0eee1d102c4?source=rss-cf15c21a5d57------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0eee1d102c4</guid>
            <category><![CDATA[web-performance]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[fps]]></category>
            <category><![CDATA[rendering]]></category>
            <dc:creator><![CDATA[Chris Nienhuis]]></dc:creator>
            <pubDate>Mon, 16 Dec 2019 17:19:38 GMT</pubDate>
            <atom:updated>2020-01-14T15:24:31.250Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="https://medium.com/expedia-group-tech/software/home">EXPEDIA GROUP TECHNOLOGY — SOFTWARE</a></h4><h4>How janky is your site?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*5djANC04uWjyO8cAwa0_bg.jpeg" /><figcaption>Understanding browser interaction performance is a fundamental insight for smooth user experiences</figcaption></figure><p>Faster load performance leads to more customer conversion at Vrbo™ (part of Expedia Group™) and every other e-commerce site. <a href="https://medium.com/u/b9d376fc7894">Carlos Moro</a> demonstrates this well in <a href="https://medium.com/expedia-group-tech/web-performance-vs-user-engagement-7eda84f6436b">Web Performance vs. User Engagement</a>. Collecting metrics such as DOM content load (DCL), time to interactive (TTI), and first contentful paint (FCP) is straightforward — they are simple timestamps relative to the start of loading a web page. But what about the interactive performance of your site? How sluggish do your customers perceive your site to be when they touch, scroll, click, and animate UI elements?</p><p>For the purposes of this article, let’s refer to degradation of interaction performance as “jank”. MDN has a <a href="https://developer.mozilla.org/en-US/docs/Glossary/Jank">definition handy as well</a>:</p><blockquote>Jank refers to sluggishness in a user interface, usually caused by executing long tasks on the main thread, blocking rendering, or expending too much processor power on background processes.</blockquote><p>Consider the following demo of jank:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FAc9h3-hET8c%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DAc9h3-hET8c&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FAc9h3-hET8c%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/71440299625d834f944c2458b6597e7a/href">https://medium.com/media/71440299625d834f944c2458b6597e7a/href</a></iframe><p>The above demo is a carousel that illustrates how jank can be measured with frames per second (FPS) data. We consider jank to be user friction and continually streamline our code to run as efficiently as possible.</p><blockquote>We consider jank to be user friction</blockquote><p>Here’s how we measure jank at Vrbo™ in the first five seconds of interaction:</p><ul><li>Use window.requestionAnimationFrame to calculate FPS (s<a href="https://github.com/ExpediaGroup/fpsmeter/blob/master/src/index.js#L82">ource: FPSMeter</a>)</li><li>Collect average FPS every 500ms starting <a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/DOMContentLoaded_event">DomContentLoaded</a></li><li>If customer switches tabs, halt FPS collection</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fw-ctEIJhRHLMLOS5hVn6A.png" /><figcaption>Visualization of measuring average FPS every 500ms</figcaption></figure><p>When we collect this data, we use Grafana to process regions and graph trendlines that we can use to see a real user metric (RUM) approximation of the jank a user experienced when loading the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8HdTCtQVZrosQV76L4Qk2Q.png" /><figcaption>Visualization of FPS RUM data between 3s and 3.5s</figcaption></figure><p>The above graph tells us over the last week, between 3.0s and 3.5s of using one of our sites, the frame rates were:</p><ul><li>5% of customer page views had ~5 FPS or worse</li><li>10% of customer page views had ~11 FPS or worse</li><li>25% of customer page views had ~30 FPS or worse</li><li>50% of customer page views had ~55 FPS or worse</li></ul><p>This data shows us how our customers are experiencing our site, and it is a great approximation of how responsive our site is at given time windows. 25% of our customers after three seconds are likely perceiving some jank — and possibly extreme jank.</p><p>Let’s look between 4.5s and 5s:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yaaXW_5gdg9WDLm0ghsHnw.png" /><figcaption>Visualization of FPS RUM data between 4.5s and 5.s</figcaption></figure><ul><li>5% of customer page views had ~13 FPS or worse</li><li>10% of customer page views had ~29 FPS or worse</li><li>25% of customer page views had ~50 FPS or worse</li><li>50% of customer page views had ~58 FPS or worse</li></ul><p>After 4.5s, 75% of our customers are experiencing a good interaction performance of 50 FPS or better. You must understand this data to understand how your customers are experiencing your site.</p><h3>What causes jank and how do I fix it?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3EjkvVtB2sCw6MtkqOYDyQ.jpeg" /><figcaption>“The pixel pipeline” — from <a href="https://developers.google.com/web/fundamentals/performance/rendering">Rendering Performance</a></figcaption></figure><p>I’ll keep this section brief, as many others have written at great depth on this topic, but jank is generally caused by <strong>scripting</strong>, <strong>style calculations</strong>, <strong>layout</strong>, <strong>paint</strong>, or <strong>compositing</strong>. JavaScript tends to degrade render performance because its handlers can frequently and exponentially trigger the other operations.</p><p><a href="http://jankfree.org/">Jankfree.org</a> is a great resource for best practices around improving your site’s interaction performance. There are plenty of other resources available for debugging and fixing rendering performance issues that I won’t cover in this article.</p><h3>How can I detect user jank?</h3><p>We’ve now <a href="https://github.com/ExpediaGroup/fpsmeter">open-sourced</a> our JavaScript utility that we use to make FPS RUM collection easy!</p><p>Here’s a brief snippet of how you could integrate FPSMeter to collect 10 samples of FPS data every 500ms:</p><pre>import FPSMeter from &#39;@vrbo/fpsmeter&#39;;</pre><pre>const meter = new FPSMeter({<br>    calculatePerMs: 500,<br>    maxCalculations: 10<br>});<br>meter.start();<br><br>function onSummarizeClientTelemetry() {<br>    let summary = {};<br>    // stop meter<br>    meter.stop();<br>    // collect fps windows into string attribute<br>    summary.fps = meter.fpsWindows.join(&#39;,&#39;);<br>    return summary;<br>}</pre><pre>// Demonstrates collection<br>setTimeout(() =&gt; {<br>    let summary = onSummarizeClientTelemetry();<br>    console.log(summary.fps); // prints &quot;60,60,60,60,60,60,60,60,60,60&quot; if perfect client performance<br>}, 10000);</pre><p>If the user loses focus on the page, <a href="https://github.com/ExpediaGroup/fpsmeter#caveat-fpsmeter-stops">FPSMeter will halt collection</a> to ensure the data being collected is clean.</p><h3>How to determine FPS sample size</h3><p>Through trial and error, we determined that measuring FPS in 500ms sample windows was an effective measurement of customer interaction performance. We tried other sample windows (such as 5s), but found that shorter windows gave much richer distribution and deterministic results.</p><p>Ultimately, if you want to measure interaction performance most effectively, you will need to tweak your sample window size and number of samples to suit your performance measuring needs. Simply adjust the <em>calculatePerMs </em>and<em> maxCalculation</em>s in <a href="https://github.com/ExpediaGroup/fpsmeter">FPSMeter</a> to tweak your sampling strategy. With some trial and error, you should be able to get the best quality readings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YFelTg0GTTuYvgFyeJS18A.png" /></figure><p>When observing performance of your sites, interaction performance is an important aspect of the user experience. Collecting FPS RUM data is a great and inexpensive way to approximate interaction performance without adding overhead to your customer’s device. By using <a href="https://github.com/ExpediaGroup/fpsmeter">FPSMeter</a> with some data processing and a graphing tool, you can create a key performance view and get a more holistic view of your site’s performance.</p><h3>Credits</h3><ul><li><a href="https://medium.com/u/b57b9f93675e">Brian Quinn</a> —Co-author of this article, involved in early research, developed initial version of FPS graph visualizations</li><li><a href="https://medium.com/u/b9d376fc7894">Carlos Moro</a> — Involved in early research, developed current FPS graph visualizations</li></ul><figure><a href="https://lifeatexpedia.com/brands"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5tdXqz9KfPYEgPG9thFk9w.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0eee1d102c4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/expedia-group-tech/measuring-interaction-performance-with-fps-data-b0eee1d102c4">Measuring Interaction Performance with FPS Data</a> was originally published in <a href="https://medium.com/expedia-group-tech">Expedia Group Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>