<?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 John Traver on Medium]]></title>
        <description><![CDATA[Stories by John Traver on Medium]]></description>
        <link>https://medium.com/@john_traver?source=rss-e197dd0d06a3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jB0LcLeTzhTMsRY1mamCWA.jpeg</url>
            <title>Stories by John Traver on Medium</title>
            <link>https://medium.com/@john_traver?source=rss-e197dd0d06a3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:22:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@john_traver/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[Framer X Walkthrough: Page View]]></title>
            <link>https://blog.prototypr.io/framer-x-walkthrough-page-view-684333109d8?source=rss-e197dd0d06a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/684333109d8</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[framer-x]]></category>
            <category><![CDATA[interactive-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[John Traver]]></dc:creator>
            <pubDate>Sun, 23 Sep 2018 17:58:34 GMT</pubDate>
            <atom:updated>2018-09-23T18:14:16.462Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LP6bzIRSIciwNEocd5MSjQ.png" /></figure><p>Framer X is a powerful tool for creating interactive prototypes, but what I find more impressive, is the underlying library that powers it all. Framer.js provides a constraint based layout engine, a powerful physics engine, and a handful of components that immediately add rich interactivity to our prototypes. These components are not all exposed in the Framer X UI (yet), so I’m going to show you how you can use one of these components called Page.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FEeBduAQLpfw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEeBduAQLpfw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FEeBduAQLpfw%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/7142eab3ff276d9f19ff174f195f4753/href">https://medium.com/media/7142eab3ff276d9f19ff174f195f4753/href</a></iframe><p>Topics Covered:</p><ul><li>Page Component (exported from Framer)</li><li>this.props.children</li></ul><p>Source:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/baa69b078e76e0a8ffabe869b4eead54/href">https://medium.com/media/baa69b078e76e0a8ffabe869b4eead54/href</a></iframe><p>Short and sweet. Although we’ll have to wait to see the Page component in the Framer X UI, it’s exciting to know how much power is still under the hood. Hope you all learned something and we’ll see you next time.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=684333109d8" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/framer-x-walkthrough-page-view-684333109d8">Framer X Walkthrough: Page View</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Framer X Walkthrough: Animatable Menu]]></title>
            <link>https://blog.prototypr.io/framer-x-walkthrough-animatable-menu-2ef203cfecb3?source=rss-e197dd0d06a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ef203cfecb3</guid>
            <category><![CDATA[framer]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[interactive-design]]></category>
            <dc:creator><![CDATA[John Traver]]></dc:creator>
            <pubDate>Wed, 19 Sep 2018 15:40:03 GMT</pubDate>
            <atom:updated>2018-09-19T15:47:43.868Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qzqXhkvZBrn9V4fwZ30VXg.png" /></figure><p>Hey guys! Super excited to do my first animation session. Animation is the reason I got into programming. From After Effects scripts, to generating 3D architecture programmatically, there is a special place in my heart for animation. When you open up Framer X for the first time, animations are a bit hidden. Unless you want a transition that can’t be customized, you are going to have to jump into the code. So let’s take a look at how it’s done!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhOx1XwkC8rs%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhOx1XwkC8rs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhOx1XwkC8rs%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/ea036dc99b57be7bafefe6f13450dbb0/href">https://medium.com/media/ea036dc99b57be7bafefe6f13450dbb0/href</a></iframe><p>Topics Covered:</p><ul><li>Container Components</li><li>Significance of props.children</li><li>The child connector whip</li><li>Overrides</li><li>Animatable</li><li>Animatable.set</li><li>Spring Options</li><li>animate.spring</li><li>Bezier options</li><li>animate.bezier</li></ul><p>Source Code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1e53c6c302b630454535eb046ad386cd/href">https://medium.com/media/1e53c6c302b630454535eb046ad386cd/href</a></iframe><p>Thanks again for following along! I’ll keep saying it, but it you have any suggestions for components or functionality you would like to see, please let me know!</p><p>Best,</p><p>John</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ef203cfecb3" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/framer-x-walkthrough-animatable-menu-2ef203cfecb3">Framer X Walkthrough: Animatable Menu</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Framer X Live Coding: Simple Button]]></title>
            <link>https://blog.prototypr.io/framer-x-live-coding-simple-button-1eb4536eb7b9?source=rss-e197dd0d06a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1eb4536eb7b9</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[framer-x]]></category>
            <dc:creator><![CDATA[John Traver]]></dc:creator>
            <pubDate>Tue, 18 Sep 2018 16:32:28 GMT</pubDate>
            <atom:updated>2018-09-19T15:00:08.968Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QLNMWaPdC_rxLvKRmMWVzA.png" /></figure><p>Hey guys, this is my very first of what I hope to be an instructional series for anyone looking to get their feet wet in Framer X.</p><p>The format is simple. I’m going to screen record a session where I explain my process building various components. I’m hoping if you guys like these, you’ll provide me with ideas for what you would like to learn more about. I love digging in and learning, so it’s not a problem if I don’t already know it! :)</p><p>Well let’s get on with it! Here is the first session: A simple Button!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FiPSg6Jk2o5o%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DiPSg6Jk2o5o&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FiPSg6Jk2o5o%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/132bb658b52d93159cc2ef530473d4f3/href">https://medium.com/media/132bb658b52d93159cc2ef530473d4f3/href</a></iframe><p>Topics Covered:</p><ul><li>Creating a code component</li><li>Navigating to project directory</li><li>Installing and importing styled components</li><li>Property control type: ControlType.Color</li><li>String interpolation into styled components</li><li>Hover psuedoclass</li><li>Override functions</li><li>OnClick functions</li></ul><p>Source Files:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c499fd8475817417bb47f4eaea02117a/href">https://medium.com/media/c499fd8475817417bb47f4eaea02117a/href</a></iframe><p>Hope you guys enjoyed this! Please give me a clap or two or fifty, and let me know what you would like to see next!</p><p>Best,</p><p>John</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1eb4536eb7b9" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/framer-x-live-coding-simple-button-1eb4536eb7b9">Framer X Live Coding: Simple Button</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Framer X: to future or not to future]]></title>
            <link>https://medium.com/@john_traver/framer-x-to-future-or-not-to-future-7d83ce1421d6?source=rss-e197dd0d06a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d83ce1421d6</guid>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[framer]]></category>
            <dc:creator><![CDATA[John Traver]]></dc:creator>
            <pubDate>Mon, 17 Sep 2018 16:51:33 GMT</pubDate>
            <atom:updated>2018-09-19T02:00:17.900Z</atom:updated>
            <content:encoded><![CDATA[<p>This in no way is sponsored by Framer. The love I may pour, is all from the heart. For me, Framer X hits a special chord.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lr3SRzHKZSCvpIrcJxV42A.png" /></figure><h3>Who am I?</h3><p>I’m a startup hacker. Co-founder of <a href="https://frame.io/">Frame.io</a> a video review and collaboration platform, and a technical creative that has always used code to deliver better media workflows. I believe strongly in the paradigms of framer.js, the library that supports Framer X. As you will see later on, it is something I’ve been thinking about for years.</p><h3>So what is Framer X?</h3><p>Framer X is the new version of the Framer prototyping tool. It’s built on top of framer.js, an open source library to seamlessly integrate your visual designs with interactive components and code. What makes Framer X so much more special, is the ability to write React components that show up in the Framer X UI. With the components available, a designer can design using the components that are already built. This eliminates the problem of wandering design systems, as components that are built will already have constraints. With such a dependency on code..</p><h3>Who is Framer X for?</h3><p>The original Framer Studio had robust tools for designers to build interactive prototypes though the UI. When looking at Framer X, theres a steeper curve into getting started with highly interactive prototypes. There are a few tools, with very few options to configure. The impression that I get is that people with no coding background, don’t immediately understand the power of the tool, and may be deterred from investing significant time into it. If you are designer who can code, or a coder that can design, Framer X will be your very best friend.</p><h3>OK.. That’s not me so now what?</h3><p>Even if you do not design and code there are many ways you may still benefit from using Framer X.</p><h3>I’m just a designer</h3><p>As a designer, Framer X offers an open components store where you can browse components other people have published and download and use them for free. Being simply React components, there are no limits to what can be built and shared in the components store. Once you download a component you can also check out the code used to create it. I believe Framer X will get more designers interested in basic React, and they will be able to unleash their creativity to the fullest.</p><h3>I’m just a coder</h3><p>As a coder, Framer X is your perfect little playground. It allows you to build using the framer.js library (if you wish) to get concepts out quickly and iterate. It’s perfect for laying out complex components visually, and seeing how small changes to a child component may propagate up to the parent. It’s also great to be able to write in controls for your component’s properties, and tweak them to perfection using the Framer X UI.</p><h3>Best of both worlds</h3><p>Being in the software business, I see the real value of Framer X for the design and handoff stages of software development. With a strong designer and developer working together, you can design and code prototypes at the same time. A developer can build a skeleton of advanced functionality, and expose controls to the designer for things like animation, and view states.</p><h3>Is that the Vision?</h3><p>Right now, Framer X seems suitable for prototyping, and not building components that ship into production. Framer X wants to bridge the gap between design and developer, but in order to do that, we need more robust tooling around management of components, versioning, and deploying to a production environment. At Frame.io (my company, I know.. little confusing), we plan to use Framer X to get prototypes done quickly with code that is not supposed to be ready for production. We want to be able to iterate on ideas quickly with design and product teams, so that we know EXACTLY how they should look and feel. This in theory should minimize the amount of back and forth during the development cycle, as edge cases, and complications are experienced during the design process.</p><h3>And then (6–12 months?) later…</h3><p>The team at Framer builds a cloud service to host your components, open sources the React version of framer.js, and tells you with a few clicks, that little prototype of yours can be a real production application. I believe when more developers see the benefits of constraint based layout engines, they will happily dump Divs and Spans in favor of Frames and Stacks. An example of a company who tried building one of these platforms was Famo.us, now sadly hosted at <a href="http://deprecated.famous.org/">http://deprecated.famous.org/</a> . And hey.. if you look on StackOverflow, there I am, the top answerer to all your Famo.us questions!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*_lcQ1UHkvu1JxCBnxfjZIw.png" /></figure><p>I have believed strongly for years in the approach of building a unified layout engine that overcomes the limits of the browser using GPU accelerated transforms, and seamlessly handles scrolling, dragging, and physics based animations. I think Framer is doing the right thing by providing value to the community, while allowing everyone to get up to speed with the tool. When it’s ready for primetime, Framer X has the potential to change the way we build rich and interactive applications.</p><h3>Thank you!</h3><p>Thank you guys for reading, and thank you team Framer for delivering on this vision! I’m excited to start writing tutorials and sharing components with you all!</p><p>Best,</p><p>John</p><h4>More where this came from</h4><p>This story is published in <a href="http://blog.usejournal.com/">Noteworthy</a>, where thousands come every day to learn about the people &amp; ideas shaping the products we love.</p><p>Follow our publication to see more product &amp; design stories featured by the <a href="https://usejournal.com/?utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_campaign=guest_post">Journal</a> team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d83ce1421d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prodigy Technology]]></title>
            <link>https://medium.com/@john_traver/prodigy-technology-ab94cf0bba7f?source=rss-e197dd0d06a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab94cf0bba7f</guid>
            <dc:creator><![CDATA[John Traver]]></dc:creator>
            <pubDate>Mon, 21 Jul 2014 15:15:30 GMT</pubDate>
            <atom:updated>2014-07-21T21:58:46.250Z</atom:updated>
            <content:encoded><![CDATA[<h4>Famo.us and the Frame.io signup page</h4><h4>Hello Famo.us</h4><p>My name is John Traver and I am the co-founder of Frame.io. Our mission is to manage the world’s media. We allow you to upload all your source media, work in progress, and assets into private workspaces where you can invite your team and clients to collaborate. We replace the hodgepodge of Dropbox for file sharing, Vimeo for video review, and Email for communication.</p><p>In the last three months, I was fortunate enough to spend time building our beta signup page in Famo.us. You can find that live at <a href="http://frame.io/?r=famo45">Frame.io</a>. We at Frame.io have a clear idea of how software should look, feel, and behave, and we set very high standards for ourselves. The Famo.us Javascript framework has been a way for us to achieve these standards with greater ease.</p><p>Famo.us has the goal of easing web and mobile application development, by giving the developer the ability to create fluid applications that will perform on any device. They are able to achieve such by building their own render and layout engine, that behaves much in the same way as a game engine. This approach allows companies to save money by eliminating the need to develop separate applications for each platform.</p><h4>A New Approach</h4><p>There are so few times in our respective fields we get to experience technology that so radically changes the way we work. The motion picture and photography industry for instance is experiencing the transition from film to digital imaging systems. These transitions take time but in the end just become another thing of the past. Famo.us is a technology that has the ability to make a similarly groundbreaking effect on the process of building HTML5 applications for mobile and web. Maybe one day we can look back and see this time as such a turning point.</p><p>When the vision of Famo.us was first presented a couple years ago, my co-founder and I were among the first to signup. It was clear that if we wished to build the most beautiful and performant applications on the web, we would need to be building with Famo.us. From the initial demos, it was easy to see right away that there was nothing especially incomprehensible about the technologies that were being used. These technologies were recognizable by those familiar with HTML5 and CSS3. There was just some kind of magic engine making all these transformations.</p><p>A few months back, it came time to build a signup page for Frame.io. After hiring out the work, we were a bit displeased with the quality of animations and transitions that we knew would not work as a first impression for our product. Fortunately, Famo.us had just opened its doors, and we were immediately let in. We knew the signup page would be a wonderful one off project to get our feet wet with the new framework. From what we had seen thus far in Famo.us, we knew we could engineer one of the most beautiful signup pages on the web.</p><h4>Starting From Nowhere</h4><p>Building from Day 1 on Famo.us was like no experience I had before. I love solving problems, but sometimes you just have to use the internet to find answers. Knowing that it was not possible to google answers was quite a practice of discipline in itself. It made me really dig into the source of Famo.us to ensure I knew how objects were working together and it made it near impossible to give up. Having all the source code meant the answers to all my questions where living somewhere within.</p><p>Besides the lack of support, I was dealing with the very first released version of Famo.us. All though there were some bugs, many times there were just things I expected to be able to do, that Famo.us was not capable of. The one that bothered me the most was that true-sized surfaces could not be stacked in any sort of sequential layout or scrollview. This is the first instance I really grappled through the code to determine at what point would be best to access a Surfaces underlying DOM element. I found the deploy function and through a little hackery, learned how to get around this pitfall. It is good to know that this is being addressed by Famo.us, and these quirky hacks will no longer be needed.</p><p>For many people, the layout engine in Famo.us is a new concept. The ideas of modifiers on surfaces is new to me, but the idea of building with absolute positions is very much like native app development. Absolute positioning is extremely static when it comes to plain CSS, but giving the power of Javascript, absolute positioning can behave more dynamic. Web design for many years has bashed absolute positioning as bad practice for this very reason. If you were not familiar with Javascript, you would literally be ‘stuck’ with a static layout. Making a shift to a new layout utilizing in full absolute positioning makes sense for a framework that is pure Javascript.</p><h4>What I Learned</h4><p>Building the signup page for Frame.io has been a wonderful experience, but there are still some things that everyone should keep in mind next time they tackle a project like this.</p><p><strong>Lesson 1 : Use Famo.us only where Famo.us needs to be used.</strong></p><p>I spent a ton of time using Surfaces for every element on the page and having to arrange them in a way that would use other Famo.us layout objects in a responsive way. On the first page of the signup, I have header text, subheader text, an email input box, and a submit button. To have them arranged vertically on the screen I used a SequentialLayout where the header was the first cell, the subheader was the second cell, and the third cell was made up of a second horizontal aligned SequentialLayout consisting of both the email input and submit button. The result was an obscene amount of floating variables and code that is difficult to maintain. Aside from maintenance, it hits the engine hard with unnecessary layout calculations. In this situation, the elements are not moving in any unique way relative to each other. It would have been best to use a single surface and contain all of these elements within the content of that surface.</p><p><strong>Lesson 2: Use Famo.us how Famo.us should be used.</strong></p><p>Famo.us shines the brightest in the when building applications that resemble native mobile or desktop apps. The main differentiator here is again the fact that Famo.us relies on absolute positioning of elements for layout. This is contrary to the free form layout of the box model, where elements are rendered one after the next. The first page of the Frame.io signup page was very much like a normal content scrollable webpage, and thus was a bit more difficult to size and resize content to look good at any screen size. If we had to do it again, we would certainly design the first page to be complementary to absolute positioning.</p><p><strong>Lesson 3: Work the way Famo.us works.</strong></p><p>There are a multitude of optimizations that the Famo.us engine makes in order to render in the most efficient manner. One such optimization is keeping track of unused elements and recycling them when possible. I learned that it is not enough to simply assume Famo.us will be taking care of all the dirty work. For instance, the signup page makes use of RenderController to hide and show elements only when they come into view. Although it seems as though I am only rendering what is needed, the effect was a bit misleading. Since I was initializing my entire layout and then hiding what was not visible, I was creating a large depot of unused DOM. Famo.us often makes you feel like you will get performance no matter what, but you really need to keep in mind how Famo.us works in order to maximize its potential.</p><h4>Looking Forward</h4><p>Although longer than expected, the process of building the Frame.io signup page in Famo.us has been like no other experience. The process of diving deep into the framework to solve problems was incredibly unique and valuable. Even though it was tough at times, knowing what Famo.us could do for me, kept me moving forward. I learned so much about how Famo.us works by building with these early versions, that now I feel capable of developing for best performance in almost any situation. The great thing about Famo.us is that the technology is already where it needs to be, and it is the browser manufacturers that need to keep up. I look forward to building Frame<a href="http://frame.io/?r=famo45">.</a>io in Famo.us because Famo.us is the first presentation framework that is in line with how we at Frame<a href="http://frame.io/?r=famo45">.</a>io believe software should look, feel, and behave.</p><p>Check it out if still have yet to! <a href="http://frame.io/?r=famo45">Frame.io</a></p><p>John</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab94cf0bba7f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>