<?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 Andrew Cunliffe on Medium]]></title>
        <description><![CDATA[Stories by Andrew Cunliffe on Medium]]></description>
        <link>https://medium.com/@cunliffeandrewc?source=rss-254deda426d6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fcKMarH_Q2HZUo-7UvyAAA.jpeg</url>
            <title>Stories by Andrew Cunliffe on Medium</title>
            <link>https://medium.com/@cunliffeandrewc?source=rss-254deda426d6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:23:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cunliffeandrewc/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[Animate SVGs in Framer with GSAP]]></title>
            <link>https://medium.com/framer-prototyping/animate-svgs-in-framer-with-gsap-7112002038a0?source=rss-254deda426d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/7112002038a0</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[framer]]></category>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[svg]]></category>
            <dc:creator><![CDATA[Andrew Cunliffe]]></dc:creator>
            <pubDate>Wed, 19 Jul 2017 16:47:46 GMT</pubDate>
            <atom:updated>2017-07-28T18:30:45.447Z</atom:updated>
            <content:encoded><![CDATA[<h4>Green Sock’s Animation Platform (GSAP) is the easiest and most powerful way to animate SVGs in <a href="https://framer.com/?utm_source=medium&amp;utm_medium=link&amp;utm_campaign=Cunliffe_Svgs&amp;utm_content=subtitle">Framer</a>.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EleTiIocF9dGofhFpHGTlw.png" /></figure><h3>A Little Background</h3><p>There are a few articles out there on working with SVGs in Framer, most focus on what SVGs are, their various attributes, and the multiple ways of getting them into Framer. The most in-depth article I’ve seen on animating SVGs is this <a href="https://medium.com/@Airytram/make-simple-svg-stroke-animation-in-framer-a23d109bcf19">one</a> by <a href="https://medium.com/@Airytram?source=post_header_lockup">Thomas Law</a>. Thomas uses CSS animations to animate the SVGs in his project, which is fine and works, but there is an easier way to do it using <a href="https://greensock.com/">Green Sock’s Animation Platform</a> or “GSAP.” You can learn more about GSAP on their site, but in a nutshell it’s a collection of JavaScript files and plugins that make it easy to create web animations that are compatible with multiple browser types, including out of date ones.</p><p>I got interested in animating SVGs in Framer following at keynote by <a href="https://blog.prototypr.io/@melissacameron?source=post_header_lockup">Melissa Cameron</a> at a recent SF Framer Session. Melissa wrote a <a href="https://blog.prototypr.io/shaping-up-your-framer-prototypes-with-svg-f147f554cc6f">great article</a> about the basics of using SVGs in Framer, which I highly suggest.</p><p><a href="https://framer.cloud/CcSIO">Grab my prototype here</a> to follow along. If you don’t have Framer, be sure to <a href="https://framer.com/download?utm_source=medium&amp;utm_medium=link&amp;utm_campaign=Cunliffe_Svgs&amp;utm_content=post">download their 14 day free trial</a> to follow along with this tutorial.</p><h3>Getting Started</h3><p>This first step towards animating an SVG is creating a Framer Project and making an artboard in the Design tab. I love MMA, and can’t wait for the upcoming McGregor vs Mayweather fight (and yes I know it’s boxing not MMA). Fun fact about me: after I got out of the U.S. Army I went to college and when it came time to pick a major, I initially picked accounting because my favorite fighter of all time, Chuck Liddell, has an accounting degree. I ended up switching to finance, but such is life. Time to get our Framer project set up.</p><p>First, create an artboard by typing “A” on your keyboard. You can select one of the preloaded devices to make an artboard. I chose the default iPhone 7 size and added some images I had previously edited in Sketch (I edited them in Sketch because Framer Design is currently lacking features like circular gradients). I targeted and named the artboard “<strong>fighterScreen</strong>,” which we’ll use to call the artboard in the FlowComponent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KPEWFfqMvpjO7YoJRtCZig.png" /></figure><h3>Setup Flow Component</h3><p>When dealing with complex images and SVGs, I find it best to enable the preloader with <strong>Framer.Extras.Preloader.enable()</strong> to ensure they are loaded in the DOM before rendering. But it’s important to note that you should probably wait until the end to do this, especially if you plan on folding any code. I created a FlowComponent that shows “<strong>fighterScreen</strong>” as the first screen. I almost always create a FlowComponent when starting a new project. It provides a degree of consistency and enables screen transitions to be easily employed if the prototype becomes more than one screen. Here’s how the code should look:</p><pre>Framer.Extras.Preloader.enable()</pre><pre>Utils.domComplete -&gt;<br> flowParent = new FlowComponent<br>  width: Screen.width<br>  height: Screen.height<br>  backgroundColor: &quot;#171717&quot;<br>   <br> fighterScreen.blur = 20<br> conorM.scale = 0.90<br> floydM.scale = 0.90<br>   <br> flowParent.showNext(fighterScreen)</pre><h3>Create The SVG</h3><p>Since I had already created the initial screen in Sketch, I only needed to make the two SVGs that I would be animating. One is a loading circle, the other is a “boxing bell”. We’ll only be animating the circle with GSAP. I exported the bell and the circle as SVGs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7U2hLagEFfBXQsfhPJoCyw.png" /></figure><h3>Cleanup The SVG In A Text Editor</h3><p>Generally, running your exported SVGs through <a href="https://jakearchibald.github.io/svgomg/">SVGOMG</a> by <a href="https://github.com/jakearchibald">Jake Archibald</a> is a good idea to clean things up. I downloaded the cleaned up version and opened it in Sublime Text to make sure everything looked good for import into Framer.</p><p>The SVG code should be nice and concise like this:</p><pre>&lt;svg width=&quot;182&quot; height=&quot;182&quot; xmlns=&quot;<a href="http://www.w3.org/2000/svg">http://www.w3.org/2000/svg</a>&quot;&gt;<br>  &lt;circle cx=&quot;90&quot; cy=&quot;90&quot; r=&quot;90&quot; transform=&quot;translate(1 1)&quot; stroke-width=&quot;2&quot; stroke=&quot;#EAEAEA&quot; fill=&quot;none&quot;/&gt;<br>&lt;/svg&gt;</pre><h3>Copy And Paste The SVG Into Framer</h3><p>In the text editor hit ⌘ + A to select all the SVG code, then ⌘ + C to copy it. In order to animate SVGs in Framer with GSAP, they need to be “inline” which means placing the SVG code within the Framer code. Create a new layer in Framer that will be a container for the SVG, add HTML to that layer with “layer.html = ” and use triple quotes so that nothing breaks up the SVG code. Paste the SVG code within the two sets of triple quotes.</p><pre> loadingCircle = new Layer<br>  parent: homeOverlay<br>  x: Align.center<br>  y: Align.center<br>  height: 182<br>  width: 182<br>  backgroundColor: &quot;null&quot;<br>   <br> loadingCircle.html = &quot;&quot;&quot;<br> &lt;svg width=&quot;182&quot; height=&quot;182&quot; xmlns=&quot;<a href="http://www.w3.org/2000/svg">http://www.w3.org/2000/svg</a>&quot;&gt;<br> &lt;circle cx=&quot;90&quot; cy=&quot;90&quot; r=&quot;90&quot; transform=&quot;translate(1 1)&quot; stroke-width=&quot;2&quot; stroke=&quot;#EAEAEA&quot; fill=&quot;none&quot;/&gt;<br> &lt;/svg&gt; <br> &quot;&quot;&quot;</pre><h3>Add GSAP to the Framer Project</h3><p>Now we need to add the GSAP files and plugins into our Framer project and include them in our index.html file to be able to animate the SVG. To do this, <a href="https://greensock.com/forums/register/">sign up for GSAP</a>, download the files and create a folder in your Framer project’s directory (I named mine “js”). Then, copy over the minified versions of their files, minified plugins folder (you only need to copy over the “<strong>DrawSVGPlugin.min.js</strong>,” “<strong>CSSPlugin.min.js</strong>,” “<strong>MorphSVGPlugin.min.js</strong>,”and “<strong>AttrPlugin.min.js</strong>” files for this example), the minified “<strong>easing</strong>” folder, and the minified “<strong>utils</strong>” folder, then add the JS files to the “<strong>index.HTML</strong>” file in the project directory. Checkout the index.HTM file in my project for what files to include there. With these added, the GSAP is ready to go.</p><p>Your project directory should now look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8jaGFTDnkhT1_bYn3DM07A.png" /></figure><p>Now this is important: the SVGs need to have a <strong>fill =“none,”</strong> and “<strong>IDs</strong>” or “<strong>classes</strong>” added to their “<strong>paths</strong>” (or whatever shapes are contained in the SVG, eg: &lt;circle&gt;, &lt;rect&gt;, &lt;ellipse&gt;, &lt;polygon&gt;, &lt;polyline&gt;, and &lt;line&gt;). In this example we are going to morph the circle and draw it. I changed “<strong>fill</strong>” to “<strong>=none</strong>” in the SVG code and gave the circle a class of “<strong>.loadingCircle</strong>.” Depending on what program you used to export, you may need to add color to the stroke. In this example I used <strong>stroke=“#EAEAEA.”</strong></p><p>You can add the fill style and the IDs/classes in the text editor before copying into Framer, but I prefer to add them in Framer and then quickly copy the ID or class names into the GSAP code.</p><p>Here’s how the circle class applied to the SVG looks:</p><pre>loadingCircle.html = &quot;&quot;&quot;<br> &lt;svg width=&quot;182&quot; height=&quot;182&quot; xmlns=&quot;<a href="http://www.w3.org/2000/svg">http://www.w3.org/2000/svg</a>&quot;&gt;<br> &lt;circle class=&quot;loadingCircle&quot; cx=&quot;90&quot; cy=&quot;90&quot; r=&quot;90&quot; transform=&quot;translate(1 1)&quot; stroke-width=&quot;2&quot; stroke=&quot;#EAEAEA&quot; fill=&quot;none&quot;/&gt;<br> &lt;/svg&gt; <br> &quot;&quot;&quot;</pre><h3>Let’s Trace the Circle</h3><p>I created a function called “<strong>traceCircle,</strong>” which fires as soon as the whole project loads by calling “<strong>traceCircle()</strong>” near the bottom of the code.</p><p>Now, we get to the part you’ve been waiting for— let’s setup the GSAP animations! We are going to be using GSAP’s SVGMorph and TimelineMax constructor which is a “<em>powerful sequencing tool that acts as a container for tweens and other timelines, making it simple to control them as a whole and precisely manage their timing</em>.” GSAP’s docs are extensive and you can read more about TimelineMax <a href="https://greensock.com/docs/TimelineMax">there</a>.</p><p>In order to draw the circle using GSAP, we need to “morph” it into a path. This is achieved by morphing the class we assigned to the circle in this way:</p><pre>MorphSVGPlugin.convertToPath(&quot;circle&quot;);</pre><p>To create the TimelineMax we set it as a variable, in this case “<strong>loadingCircleTrace.</strong>”</p><pre>loadingCircleTrace = new TimelineMax()</pre><ol><li>There are a lot of <a href="https://greensock.com/docs/TimelineMax/TimelineMax()">parameters</a> that can be set within the constructor, but we are just going to do a straightforward trace here, so I didn’t include any.</li><li>With the “<strong>loadingCircleTrace</strong>” variable set, next we need to add the <a href="https://greensock.com/docs/TimelineMax/from()"><strong>.from()</strong></a> method to the “<strong>loadingCircleTrace</strong>” variable. Within the <strong>.from()</strong> method we call the “<strong>.loadingCircle” </strong>class added to the circle, set the animation to run for 2 seconds, add an easing curve (GSAP has a <a href="https://greensock.com/docs/Easing">great visualizer</a> for using their curves), and add the <a href="https://greensock.com/docs/Plugins/DrawSVGPlugin"><strong>drawSVG</strong></a> value. In this case it’s a straight trace so I set the value at 0%, meaning that the SVG will trace from 0–100%.</li><li>Done, now the SVG should animate!</li></ol><p>Here’s the full GSAP draw code:</p><pre>traceCircle = () -&gt; <br>  MorphSVGPlugin.convertToPath(&quot;circle&quot;); <br>  loadingCircleTrace = new TimelineMax()<br>  loadingCircleTrace.from(&#39;.loadingCircle&#39;, 2, {ease: Elastic.easeInOut.config(0.5, 2), drawSVG:&quot;0%&quot;})<br>  traced = true</pre><h3>Further Animations</h3><p>I also set up animations that load in some text from offscreen right by making the top part of the “bell” SVG “shake”. Retrace the circle down to zero, show the “<strong>fighterScreen,</strong>” and scale up the images of Conor and Floyd:</p><pre>textLoad = () -&gt;<br>  selectAFighter.animate<br>   x: Align.center<br>   options: <br>    curve: Spring(damping: 0.65)</pre><pre>shake = (times = 4) -&gt;<br>  <br>  i = 0<br>  <br>  right = new Animation bellIconTop,<br>   x: bellIconTop.x + 3<br>   rotation: + 1<br>   options:<br>    curve: &quot;bezier-curve&quot;<br>    time: 0.08<br>   <br>  left = new Animation bellIconTop,<br>   x: bellIconTop.x - 3<br>   rotation: - 1<br>   options:<br>    curve: &quot;bezier-curve&quot;<br>    time: 0.08<br> <br>  right.onAnimationEnd -&gt;<br>   if i &lt; times<br>    left.start()<br>    i++<br>   else<br>    bellIconTop.animate<br>     rotation: 0<br>     x: 0<br>     options: <br>      time: 0.1<br>     <br>  left.onAnimationEnd -&gt;<br>   if i &lt; times<br>    right.start()<br>    i++<br>   else<br>    bellIconTop.animate<br>     rotation: 0<br>     x: 0<br>     options: <br>      time: 0.1<br> <br>  right.start()</pre><pre>...</pre><pre>traceCircle()<br> <br> Utils.delay 1.25, -&gt;<br>  loadBellIconParent.start()<br> loadBellIconParent.onAnimationEnd -&gt;<br>  shake()<br>  Utils.delay 0.65, -&gt;<br>   textLoad()<br>   loadingCircleTrace = new TimelineMax({paused:false, repeat:0, yoyo:false})<br>   loadingCircleTrace.to(&#39;.loadingCircle&#39;, 2, {ease: Elastic.easeInOut.config(0.5, 2), drawSVG:&quot;0%&quot;})<br>   traced = false<br>   Utils.delay 2, -&gt;<br>    if traced == false<br>     homeOverlay.animate<br>      opacity: 0<br>      options: <br>       time: 0.3<br>     fighterScreen.animate<br>      blur: 0<br>     conorM.animate<br>      scale: 1<br>     floydM.animate<br>      scale: 1</pre><h4>Check It Out In GIF Form</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/308/1*wLqKahr4j68EfKm37fT3Bg.gif" /></figure><p>I hope this helps you get started animating SVGs in GSAP. If you have any questions about the other stuff I’m doing here, or need help using GSAP in your prototypes, feel free to reach out to me on <a href="https://twitter.com/acunliffedesign">Twitter</a> or comment below!</p><figure><a href="https://blog.framer.com/framer-flows-bd18617bbcf5"><img alt="" src="https://cdn-images-1.medium.com/max/900/1*fSLORhHmb6yycsRtfgT_lQ.png" /></a></figure><figure><a href="https://www.facebook.com/groups/framerjs/?ref=bookmarks"><img alt="" src="https://cdn-images-1.medium.com/max/265/1*H6W5-QpHqVSRRR2N9NSe3w@2x.png" /></a></figure><figure><a href="https://framer.com/download?utm_source=medium&amp;utm_medium=link&amp;utm_campaign=Cunliffe_Svgs&amp;utm_content=subtitle"><img alt="" src="https://cdn-images-1.medium.com/max/265/1*WJp-afZyQk72Y14YsubOcQ@2x.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7112002038a0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framer-prototyping/animate-svgs-in-framer-with-gsap-7112002038a0">Animate SVGs in Framer with GSAP</a> was originally published in <a href="https://medium.com/framer-prototyping">Framer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Sketch and Framer to Create Responsive Mobile Prototypes for Remote Testing: Part 2]]></title>
            <link>https://medium.com/framer-prototyping/using-sketch-and-framer-to-create-responsive-mobile-prototypes-for-remote-testing-part-2-f10973d2f917?source=rss-254deda426d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/f10973d2f917</guid>
            <category><![CDATA[framer]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Andrew Cunliffe]]></dc:creator>
            <pubDate>Tue, 16 May 2017 21:14:31 GMT</pubDate>
            <atom:updated>2017-05-16T21:14:31.058Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dLbf6dGXBw_8EiUP3GVuKw.png" /></figure><p>In my previous post, I shared my comprehensive workflow for creating native mobile prototypes in Framer that responsively scale across devices with resolution ratios of ~1.778. Please read that post first, as this one will utilize 99% of its workflow. Building upon that workflow, here I am showing my solution for the two problems I experienced testing prototypes on Android devices. Many of the solutions I came up with in this workflow can also be applied to other platforms besides Android.</p><h4>The need for these solutions comes from the success criteria I set for this project previously:</h4><ol><li>The ability to reuse some code from the desktop prototypes, and in this case, iOS prototypes.</li><li>Be responsive across multiple mobile devices.</li><li>Solve the problems my team has been experiencing: <a href="https://medium.com/@cunliffeandrewc/using-sketch-and-framer-to-create-responsive-mobile-prototypes-for-remote-testing-part-1-a0f4d0d98e2c#3c82">Multiple Resolutions</a>, <a href="https://medium.com/@cunliffeandrewc/using-sketch-and-framer-to-create-responsive-mobile-prototypes-for-remote-testing-part-1-a0f4d0d98e2c#d1de">Native Nuances</a>, and <a href="https://medium.com/@cunliffeandrewc/using-sketch-and-framer-to-create-responsive-mobile-prototypes-for-remote-testing-part-1-a0f4d0d98e2c#10e8">Sharing With Remote Testers</a>.</li><li>Have a gentle learning curve for those with little to no coding experience.</li></ol><p>This post mainly addresses solutions for creating the correct native nuances on Android.</p><h3>My Android Problems</h3><h4>Problem 1</h4><p>Swap the iOS status bar out for an Android one, and show an Android bottom navigation bar that displays above on top of every other object in the prototype. Neither of these is severe, but they do require a little work.</p><h4>Problem 2</h4><p>There seems to be a bug using overlays that are not full-screen in Framer Flows on Android, sometimes “flow.showPrevious()” events trigger from user interactions with UI objects not bonded to that flow event’s respective event handler. I have found this behavior to be completely unpredictable. The primary event I have been solving for is using an overlay flow event to show and hide a keyboard. Often on Android, tapping out of an active keyboard to close it transitions to the previous screen, instead of the expected behavior. Here is the video of the bug I showed in my previous post.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F216956802&amp;url=https%3A%2F%2Fvimeo.com%2F216956802&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F634052366_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="640" height="360" frameborder="0" scrolling="no"><a href="https://medium.com/media/edba7a52a88a6eb5a98bf8032c4677e9/href">https://medium.com/media/edba7a52a88a6eb5a98bf8032c4677e9/href</a></iframe><h3>My Android Solutions</h3><h3>Solution 1</h3><p>The main course of action in solving the first problem is setting up the Sketch file. From there, it’s only a few lines of code to have everything up and running.</p><h4>Step 1: Setting up the Sketch File</h4><p>Using the <a href="https://drive.google.com/file/d/0B4sKLQLv5UEOUEwxeF80UllnWjg/view?usp=sharing">original Sketch file</a> from the previous post as a starting point, here is a step-by-step process to make it Android ready.</p><ol><li>Make a copy of the original file, and add “Android’ onto the end of the new file’s filename.</li><li>Select all the artboards and add “Android” onto their names. I use the <a href="https://github.com/rodi01/RenameIt">Rename It Sketch plugin</a> to do this efficiently.</li><li>Copy and paste an Android status bar and bottom navigation from another project, UI kit, or create your own. Scale them up to the correct width of your artboards if needed.</li><li>To make the status bar Android specific delete contents of the iOS Status bar, then copy and paste the new Android status bar layer group into the old iOS status bar artboard. Add 10 px to the height of the artboard to accommodate the taller status bar.</li><li>Select the bottom navigation layer group, hit “cmd-a” and create an artboard with the selection. Rename the artboard using the naming convention, and the bottom navigation is ready to go.</li><li>Select every layer except the status bar and the bottom navigation, remove 100 px from their height, then move the affected elements up by 100 px.</li><li>paste in an Android keyboard, scale it to the correct width, rename it, and your Sketch file is ready to go.</li></ol><p>Here is a video I made of getting the Sketch file ready, I went slow, and it still took less than three minutes. The only thing the video is missing is creating the keyboard.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F217238447&amp;url=https%3A%2F%2Fvimeo.com%2F217238447&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F634406558_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/5df3bb6060c1f59ffe05f8a1cce7d5ca/href">https://medium.com/media/5df3bb6060c1f59ffe05f8a1cce7d5ca/href</a></iframe><h4>Grab the Android ready Sketch file <a href="https://drive.google.com/file/d/0B4sKLQLv5UEOT1ZyRW5MQ3N2WDQ/view?usp=sharing">here</a></h4><h4>Step 2: Importing the Sketch File into Framer and Copying Over Some Code.</h4><p>Create a new Framer project and import the Sketch file. Copy and Paste all the code from the previous Framer project except for the “keyboard events,” and add “Android” to all layer names that need it, e.g. flow events, the header, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*91d9hRWDAv6CdyiMBfQoIQ.png" /></figure><p>Make the bottom navigation a Framer Flows footer and assign its parent to “all.” Setting it as a footer with a parent outside of the flow component ensures that it will always render on top of all other layers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*PQ91TFuYRElSdESjapMBhQ.png" /></figure><p>Set the height of the overlay on screen4 “s.screen4OverExampleMobileAndroid” to its height plus that of the bottom navigation. Without this step, the overlay’s “maxY” value will be the Framer Flows default of the bottom of the screen, and its children will all be 100 px lower than they are in the Sketch file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/893/1*B12n4quPApCTZ-aANcA7DQ.png" /></figure><p>At this point, problem 1 is solved.</p><h3>Solution 2</h3><p>Here comes the hard(er) part, setting up a keyboard that does what I want it to do. My solution is a little “hacky,” but it fulfills my success criteria, and is the most reliable of my keyboard solutions.</p><p>Go back to Sketch and create a layer group in the keyboard artboard that is a transparent rectangle the same width of the artboard, and the height of a user journey screen artboard minus the keyboard (1184–458 = 738). Make it a group, rename it “keyboardHider,” and set it outside the bounds of the artboard by putting it above the keyboard, without resizing the artboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*380ZeR8bRjk_RDh-SQLwyw.png" /><figcaption>Keyboard with “keyboardHider” layer</figcaption></figure><h4>Step 1: Set the Parent and Default State of the Keyboard</h4><p>Import the Sketch file back into Framer and set the keyboard’s parent to “all,” this ensures the keyboard will always show over everything except the bottom navigation. The keyboard should now show over the first screen and above the bottom navigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*aKFsNGykcnJSZrYIZ3CBEA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*Xti9j_PPo6zbvQHWKiUn0Q.png" /></figure><p>Set the default “y” value of the keyboard to the “maxY” value of the bottom navigation so that it sits below the screen. Now, the first screen looks as it should, and the keyboard is already loaded.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*kPVr8PpAYIqVttSnvsrSzQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/405/1*TLa5RdDl0p7BGBUGMvGRKQ.png" /></figure><h4>Step 2: Create an Array and For Loop</h4><p>With a keyboard that lives across all screens, it’s possible to place all UI elements that cause the keyboard to show in a single array, then use the contents of that array to show and hide the keyboard.</p><p>Create an array called “inputArray,” then add all user input objects that trigger the keyboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*Im4StvVV-_NOfo9f6qsn9g.png" /></figure><p>Create a boolean value “keyboardShown” and set it to “false.” Then create a for loop that listens for events on the contents of the “inputArray.” In this case if “keyboardShown == false,” then clicking/tapping on one of the input objects sets the boolean value “keyboardShown” to “true,” and shows the keyboard by changing its “maxY” value to the “y” value (top) of the bottom navigation.</p><p>Here comes the “keyboardHider” layer; within the same conditional set “keyboardHider’s” “y” value to “0,” thus when an “input” object is clicked/tapped the “keyboardHider” extends from the top of the keyboard to the top of the screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*YtpNAlUMV6Vo6Ea7jtztsA.png" /></figure><p>Next, set up an event handler that hides the keyboard when the “keyboardHider” is clicked/tapped when “keyboardShown == true.” This event handler hides the keyboard, moves the “keyboardHider” down below the bottom navigation and sets the “keyboardShown” boolean value back to “false.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*ZYpc530b52Bb1GGpGFVLwg.png" /></figure><p>Move the keyboard user events from the original prototype into the for loop, and tab them over until they line up with the “keyboardHider” interactions interactions under the “if keyboardShown == true” conditional. Remove any flow events that came from the previous prototype.</p><p>Add the same logic that hides the keyboard when the “keyboardHider” is clicked/tapped to the keyboard user events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*YSQl7NcLKavCivyojhDU7A.png" /></figure><p>Now, when a user taps into an input field the keyboard will show, if they tap out of it, the keyboard will hide, and nothing will change. If they tap the keyboard’s keys when it’s active, the keyboard will hide, and the input fields will fill.</p><h4>Here it is in action</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F217738271&amp;url=https%3A%2F%2Fvimeo.com%2F217738271&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F635028330_960.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="960" height="540" frameborder="0" scrolling="no"><a href="https://medium.com/media/c06d7440c1091246891ca7b5224492f0/href">https://medium.com/media/c06d7440c1091246891ca7b5224492f0/href</a></iframe><p>Sometimes, if I tap in and out of the keyboard as fast as I can on my old Galaxy S5, the keyboard can get stuck, but tapping the keyboard’s keys hides it and fills in the respective fields. I really have to work at tapping quickly to make this happen.</p><h4>Grab the Android ready Framer project <a href="https://framer.cloud/idsIP/">here</a></h4><h3>Key Takeaways</h3><p>The workflows in this post, and the previous, should create a good foundation for you and your team to make complex, end-to-end prototypes. Prototypes that are responsive across multiple mobile devices, only require one or two Sketch files, and can be tested with remote users.</p><p>I’m working on a solution for modals on Android and can post it if it’s helpful. Please do reach out if you have any questions, improvements, or help with adapting anything to your specific applications.</p><p>The third part in this series will detail adopting this workflow for other screen resolution ratios, like tablets.</p><p>Thanks again to <a href="https://medium.com/@charliedeets">Charlie Deets</a> for his <a href="https://medium.com/facebook-design/framer-sketch-an-intentional-workflow-f91ee2ee1cc1">workflow</a>, and his <a href="https://medium.com/facebook-design/framer-snippets-library-24c60a724410">snippets</a> that provided the springs for the keyboard animations in this prototype.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f10973d2f917" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framer-prototyping/using-sketch-and-framer-to-create-responsive-mobile-prototypes-for-remote-testing-part-2-f10973d2f917">Using Sketch and Framer to Create Responsive Mobile Prototypes for Remote Testing: Part 2</a> was originally published in <a href="https://medium.com/framer-prototyping">Framer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Sketch and Framer to Create Responsive Mobile Prototypes for Remote Testing: Part 1]]></title>
            <link>https://medium.com/framer-prototyping/using-sketch-and-framer-to-create-responsive-mobile-prototypes-for-remote-testing-part-1-a0f4d0d98e2c?source=rss-254deda426d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0f4d0d98e2c</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[framer]]></category>
            <dc:creator><![CDATA[Andrew Cunliffe]]></dc:creator>
            <pubDate>Thu, 11 May 2017 08:15:54 GMT</pubDate>
            <atom:updated>2017-05-15T23:21:59.104Z</atom:updated>
            <content:encoded><![CDATA[<p>I have found that prototypes solve 99% of design problems. Whether reviewed with other designers, <a href="https://www.boxuk.com/insight/blog-posts/unboxing-guerrilla-usability-testing">guerrilla tested</a> on coworkers with limited knowledge of the project, or tested with users, if there is a problem in the design it will show up when prototyped. Framer is my prototyping tool of choice, for multiple reasons, the main reason being the ability to build prototypes that feel as close to a native application as possible. If you are new to <a href="https://framer.com/?utm_source=Medium&amp;utm_medium=Blog&amp;utm_campaign=responsive_body">Framer</a>, learn more by checking out their website or download the <a href="https://framer.com/download?utm_source=Medium&amp;utm_medium=Blog&amp;utm_campaign=responsive_body1">free trial</a>, as this post is rather technical.</p><p>My team does most of our user-testing with remote users on <a href="https://www.usertesting.com/">UserTesting.com</a>. Many of our core customers primarily use our products within a desktop browser, but when trying to build and share “native feeling” mobile prototypes, members of my team ran into various problems.</p><p>I previously constructed an example workflow for desktop browser prototypes that worked well but did not translate to mobile. To maintain that Framer was still a viable rapid prototyping tool for multiple platforms with my team and the rest of the product team, I had to come up with a workflow that solved the issues my team was experiencing. The success criteria I established for this workflow was the ability to reuse some code from the desktop prototypes, be responsive across multiple mobile devices, solve the problems my team has been experiencing, and have a gentle learning curve for those with little to no coding experience.</p><h3>Problem 1: Testing in Multiple Resolutions.</h3><p>Designing in 1x resolution is a best practice — there are a lot of posts that outline the benefits, <a href="https://medium.com/shyp-design/design-at-1x-its-a-fact-249c5b896536">here is one</a>. Framer renders prototypes in their native resolution, for iPhone 7 that’s 2x, iPhone 7+ 3x, and Android is all over the place with the vast amount of models in circulation. Designers on my team would have to make Sketch files and prototypes in multiple resolutions for multiple devices, or only test with users that possess a certain device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PX-EbHzVht3RYTZKgogxtw.png" /><figcaption>iPhone Resolution Chart from <a href="https://www.paintcodeapp.com/news/ultimate-guide-to-iphone-resolutions">PaintCode</a></figcaption></figure><h3>Problem 2: Native Nuances</h3><p>My team was having problems creating the little nuances that make a prototype feel native with multiple screen flows. Some of the questions I received on the matter: “how do you make the status bar seem static?”, “can you make a keyboard that works across multiple devices?”, “can you hide the gray background for overlays?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*qNkrWxJYkBy18jiMTdlp9Q.png" /><figcaption>An overlay’s gray background showing over the status bar</figcaption></figure><h3>Problem 3: Sharing With Remote Testers</h3><p>When sharing prototype links from Framer Cloud with desktop browser users, the prototype renders within its respective device. On mobile, the prototypes render as a native app within the browser UI, making them unviable for user-testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*Q1fTK-k5mcdE97bGKORZyA.png" /><figcaption>Opening the prototype by default on iOS in Safari</figcaption></figure><h3>The Solution Workflow</h3><p>The foundation of the workflow I have created come from a post written by <a href="https://twitter.com/charliedeets">Charlie Deets</a> entitled <a href="https://medium.com/facebook-design/framer-sketch-an-intentional-workflow-f91ee2ee1cc1">Framer &amp; Sketch: An Intentional Workflow</a>. Building upon Charlie’s workflow, I came up with naming conventions for groups and artboards to easily be organized in and exported from Sketch, compiled an example Sketch file, built an example Framer project, and constructed an easy to follow process for remote users to setup a testing environment on their devices.</p><h3>Solving Problem 1</h3><h4>Setting Up The Sketch File</h4><p>When using Framer Flows, I set up my Sketch file to follow the same linear progression that will occur within the prototype. However, any screens that I will be using as headers, footers, keyboards, or overlays globally across the prototype I place before the user journey screens, and arrange them vertically to differentiate them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bOKySfxvefk_8zxkv-aTZQ.png" /></figure><h4>Naming Convention for Artboards</h4><p>After iterating and reviewing with my team, I decided upon a baseline naming system that contains up to five descriptors in camelCase for easy importing. For more information about using camelCase in programming, reference this <a href="https://en.wikipedia.org/wiki/Camel_case#Programming_and_coding">Wikipedia article</a>.</p><h4>Sketch Artboard Naming System:</h4><p>screen / footer / header / keyboard / modal / overlay number<br> + <br>project name<br>+<br>if applicable, current screen’s child overlay / modal / etc<br>+<br>device / operating system.</p><h4>For example:</h4><p>keyboard1ProjectTablet</p><p>screen1ProjectMobile</p><h4>Device / Operating System</h4><p>This descriptor can be as equivocal as “Mobile,” or as precise as “GooglePixelXLLandscape.” So far, my most common level of granularity in this respect is “MobileiOS” and “MobileAndroid,” nonetheless, I find it best to be thorough when adopting team or company-wide paradigms.</p><h4>Child Overlays and Modals</h4><p>In the case of an overlay, or any other object that is a child of a screen in the user journey, I add a fifth descriptor after the “number” and before the “project name” denoting the object type.</p><h4>Overlay example:</h4><p>screen4OverProjectMobile</p><h4>Modal example:</h4><p>screen5ModalProjectDesktop</p><h4>New User Journey</h4><p>In the case that a user journey forks into multiple unique journeys, I add another two digit number to the end of the first screen number. This added descriptor is helpful in tracking where the original journey forks and the new one begins (I did not include an example of this in my Sketch file, but it is part of the paradigm).</p><h4>New User Journey Example:</h4><p>screen601ProjectMobile</p><h4>Naming Convention for Groups</h4><p>For Sketch layers to be recognized as layers in Framer, they have to be assigned to a group in Sketch, even if the layer is a single icon, etc. With the vast diversity of group types, I apply a less strict naming system.</p><h4>Sketch Group Naming System:</h4><p>object name<br>+<br>parent artboard, if applicable<br>+<br>device / operating system, if applicable</p><ol><li>I omit the “project name” from the group name, as it makes reusing groups across multiple Sketch files less efficient when having to rename company-wide design objects between projects, for example: “hamburger menus” and “back buttons. “</li><li>If the group is a single or global occurrence, e.g. a “sign up button” that only occurs on one screen, or a “back button” that occurs across all screens, the groups’ names will be “signUpButton” and “backButton” respectively.</li><li>If the group occurs on multiple screens, but interactions with the instances induce different behavior, I add the parent’s main descriptor to the end of the group. In the case of a “yes button” that occurs throughout a sign-up flow but induces different behavior, I would name the group on the third screen “yesButtonScreen3.”</li><li>When the group is iOS or Android specific I add the operating system to the end of the name, “passwordInputAndroid.”</li></ol><p>I am fastidious about my naming convention with artboards, but do find myself missing groups from time-to-time. I highly suggest naming artboards and groups as you create them, this makes it far easier to keep things organized, and helps you formulate your plain text logic (reference “Step 2” in Charlie’s <a href="https://medium.com/facebook-design/framer-sketch-an-intentional-workflow-f91ee2ee1cc1">post</a> for more on that).</p><h4>Sizing Artboards For Exporting</h4><p>Framer supports importing from 1x resolution and then converting to the native resolution of the device: 2x, 3x, etc., but I have found importing artboards with native iPhone7 resolution (750 x 1334 px) works best when making prototypes that are responsive across multiple mobile devices. To do this, I simply duplicate my 1x Sketch file, add “Proto” to the end of the new file’s name — denoting it will be for exporting as a prototype, then select all the artboards and use Sketch’s scale tool to scale them up to 200% of the originals artboards. To accommodate the iOS status bar, I subtract 40 px from the height of all the user journey artboards, making them 1296 px tall, and adjust affected layers accordingly.</p><h4>Grab my example Sketch file <a href="https://drive.google.com/file/d/0B4sKLQLv5UEOUEwxeF80UllnWjg/view?usp=sharing">here</a>.</h4><h4>Import the Sketch File into Framer</h4><p>Once I have all of the above set in Sketch, I create a new Framer project and import my Sketch file. Note that I shorten “sketch” to “s” to make the code more succinct. I find it helpful to have the “s” in front of Sketch layers to differentiate them from layers I create in Framer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/541/1*ESGX_0H5TxvPacDrQY2EYw.png" /></figure><h4>Setting up the Framer Project to be Responsive</h4><p>My methodology for making these prototypes “responsive” does not make them truly responsive from mobile up to a large screen desktop. The code I am using merely scales the Framer projects to fit mobile devices using portrait layouts with resolution ratios of ~1.778, ( iPhone 7: 1334 / 750 px = 1.778, Samsung Note5: 2560 / 1440 px = 1.778, etc). We can reuse this same code to work across other devices with different ratios by changing two values (that will be the third part in this series). If you want a Framer solution to make your prototypes responsive across all devices, I suggest checking out <a href="https://github.com/sigtm/Framer-Adapt">Framer-Adap</a>t (it does require some more work than what I am doing).</p><p>To make the prototypes responsive, I use Chris Chen’s code from his post <a href="https://medium.com/@chrisdeli/framer-tips-responsive-for-multiple-devices-a23b212b8f62">Framer Tips — Responsive for Multiple Devices</a>. For a more in-depth look at what the code is doing, I suggest reading his post, as I am going to just give a quick synopsis for setting up my prototype.</p><ol><li>I set the default height and width of the original screens.</li><li>I calculate the ratio of the width of the current device by using the built-in Framer object “Screen.width” divided by the default width I set in the previous step: “defaultW,” and assign this value to the variable “ratio.” Note that I made a small change to Chris’s code here to make it slightly more succinct: I use Framer’s built in Screen object to detect the height and width of the current device’s screen, without setting those values as variables, which Chris does in his example.</li><li>I make a new layer “all” that I use to wrap all the objects in the prototype, effectively making it responsive. The layer “all” achieves responsive scaling by setting all of its child layers’ width and height to their respective default values, then scales them up or down to fill the current device’s screen size using “ratio.” To ensure the scaling originates from the top left corner of the device’s screen “all’s” “originY” is set to a value of 0, its value of “y” to 0, and then all layers are centered on the x-axis of the device’s screen.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/527/1*bsGQGJoR7mBUIts6aeLnYQ.png" /></figure><p>Again, if you want a more in-depth look at why I am doing anything in this step, I implore you to read Chris’s <a href="https://medium.com/@chrisdeli/framer-tips-responsive-for-multiple-devices-a23b212b8f62">post</a>.</p><h4>Setting up the Flow Component and Making it Responsive</h4><p>I love Framer Flows; it has made it far easier for the other designers on my team to create user journeys, but it can have its quirks. To initiate Framer Flows I create a Flow Component and assign some values to it to make it responsive: I set the “parent” of the Flow Component to “all” and its width and height to that of “all.” These values make it scale to fill the entire screen real estate established by the “all” layer.</p><p>Next, I set the first screen in the flow, and create any “header” or “footer” layers — in this case the iOS status. For more on what I am doing here check out the Flow Component in the Framer docs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/1*qWcBpPXsoRZTtg9tTVE3_g.png" /></figure><h4>It’s Magic!</h4><p>The prototype now scales across all devices with similar resolution ratios. In this picture can see the same prototype rendered on an iPhone5C, Samsung GalaxyS5, iPhone 6s, and iPhone7+.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pf0GdHr2W0BkIJz8502OxQ.png" /></figure><h4>Setting the Default Layer States</h4><p>After making everything responsive I create my “default states” for layers that are different upon loading the prototype, than they are in Sketch. In this example, I have created “disabled” states for buttons by using 50% opacity and disabling their event listeners with conditional boolean values. These boolean values change after the user enters text into the buttons’ linked input fields. I also create states for text in input fields that set their width to 0, which hides the text until the user enters their username, password, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/506/1*hWYm62JHdNYkGdfZ5jFXiw.png" /></figure><h3>Solving Problem 2</h3><h4>Creating Multiple Types of Flow Events</h4><p>I codify flow events by assigning those that move to a new screen, and child objects that correspond to a flow event within a screen, to their separate respective code blocks. In this example, I have “Flow Events” which trigger moving to a new screen, “Keyboard Flow Events” that show and hide keyboards, and “Overlay Flow Events” that show and hide an overlay that only occurs on one screen.</p><h4>Flow Events</h4><p>The first flow event loads the first screen: “flow.showNext(s.screen1ExampleMobile).” This event triggers upon loading the prototype, while user actions trigger all other flow events in this example.</p><p>Before the second flow event triggers, when the user taps “s.signUpBtn,” I assign a boolean value stating that the current screen is not “s.screen2ExampleMobile” to establish how the user interacts with the keyboard on the next screen. After the user taps “s.signUpBtn” the prototype transitions to the next screen and makes “screen2 = true.” With this boolean value “true,” interacting with the keyboard on this screen enables different behavior than that which would occur by interacting with the keyboard on a different screen (more on that in the next section).</p><p>The next two flow events are triggered when the user taps their respective buttons. These flow events use conditional statements initially set in the “Default States” section to make the buttons “disabled” by ignoring events. When the conditional requirements are met by the user interacting with the keyboard within the respective screens, the buttons become “enabled,” and are actionable for moving to the next screen in the flow.</p><p>The last two flow events are triggered by users tapping on a button that then transitions to a new screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*WOMRFmvJ7RciWVlchINeKA.png" /></figure><h4>Keyboard Flow Events</h4><p>As is evident in the Sketch file, I use a single keyboard across multiple screens; this is made possible by using conditional statements dependent on the screen where the keyboard occurs and user events. In this section, I have three flow events, two that trigger showing the keyboard as an overlay, and one that conditionally hides the keyboard, changes boolean values, and animates layers.</p><p>An essential part of the workflow resides here, to make a Flow Component overlay work for a keyboard I hide the gray background that fills the parent screen outside the bounds of the overlay</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*mVtH-wIGh_g6B05pWU7xMw.png" /></figure><p>I do this by assigning the gray background layer “flow.children[0]” to a variable “overlayBack,” and setting that variable’s “backgroundcolor” to “transparent.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*_4xC_teuY1dCBhSbyg3ckA.png" /></figure><p>On iOs, and within the desktop browser, this makes the overlay show and hide as it should, but I am running into a bug on Android that sometimes goes to the previous screen when tapping out of the keyboard. Here is a video of the bug on my old Samsung Galaxy S5.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F216956802&amp;url=https%3A%2F%2Fvimeo.com%2F216956802&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F634052366_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="640" height="360" frameborder="0" scrolling="no"><a href="https://medium.com/media/edba7a52a88a6eb5a98bf8032c4677e9/href">https://medium.com/media/edba7a52a88a6eb5a98bf8032c4677e9/href</a></iframe><p>I have only tested this on a Galaxy S5 and a Galaxy Note6, so perhaps it doesn’t happen on more recent devices; nonetheless, this bug impacts my success criteria. I can hack it by making the “overlayBack” variable ignore user events, but this makes the keyboard not hide like it should when a user taps out of it. Thus, I don’t use it as it negatively affects the majority of our users that will be testing this prototype on iOS. Part 2 of this series will be a post on my Android keyboard solution, an example Android Sketch file with bottom navigation, and an example prototype.</p><h4>Overlay Flow Events</h4><p>I have two flow events that show and hide an overlay that occurs on the fourth screen of the prototype’s flow. The overlay displays over the fourth screen up to the status bar, by being 1296 px tall. The same essential part of this workflow mentioned in the previous section occurs here; the gray background of the overlay must be set to “transparent” or it will cover the status bar. I use the same code as previously, and it solves the problem here too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*BiLp4Nf-Ocr4Ii0gDxYvOA.png" /></figure><h4>You can play around with and download my Framer project <a href="https://framer.cloud/fVdlE">here</a>.</h4><h3>Solving Problem 3</h3><h4>Delivering the Prototype to Users for Testing</h4><p>UserTesting.com will work with you to <a href="https://www.usertesting.com/product/website-usability-testing">test anything</a>: mobile apps, TVs, refrigerators, and everything in between. They allow you to set almost any criteria for user tests, and virtually any instructions or user questions you want. Depending on how you setup the test, or how you ask for one of their amazing moderated tests, you can inject instructions where appropriate on how to use your prototype.</p><p>Originally, I came up with a process for users to set up their testing environment that addressed both Android and iOS users, but with UserTesting’s excellent ability to filter users, I found it better to provide iOS and Android specific instructions. I suggest adapting these instructions to meet your needs, but the basic steps are as follows:</p><h4>On iOS</h4><ol><li>Have the user download <a href="https://itunes.apple.com/us/app/framer-preview/id1124920547?mt=8">Framer Preview</a> from the App Store</li><li>Have them copy the link to your prototype in Framer Cloud on their device</li><li>When Framer preview is finished downloading, have them open the app</li><li>Next, have them tap “links” at the bottom right of the tab bar</li><li>Lastly, have them tap the copied link</li></ol><p>If they did everything correctly, the prototype should render full screen on their iOS device.</p><h4>On Android</h4><ol><li>Have the user download <a href="https://play.google.com/store/apps/details?id=com.framerjs.android&amp;hl=en">Framer</a> in the Google Play Store</li><li>Have them copy the link to your prototype in Framer Cloud on their device</li><li>When Framer is finished downloading, have them open the app</li><li>Next, have them paste the copied link and tap the “done” or “next” button</li></ol><p>If they did everything correctly, the prototype should render full screen on their Android device.</p><h3>Wrapping Up</h3><p>I hope this workflow helps you, and I will post my Android solutions in Part 2. Part 3 of this series will outline how to adapt this framework for other devices and layouts. While I know this isn’t a complete end-to-end solution, I hope it at least provides a foundation that solves a lot of the small but critical problems you might experience.</p><p>If you have any questions, improvements, or just want to talk design, feel free to reach out to me on Twitter or comment below.</p><p>Thanks to <a href="https://medium.com/@charliedeets">Charlie Deets</a> and <a href="https://medium.com/@chrisdeli">Chris Chen</a> for their work that made this workflow possible.</p><p>Thank you for reading!</p><figure><a href="https://framer.com/features/handoff/?utm_source=Medium&amp;utm_medium=Blog&amp;utm_campaign=responsive_footer1"><img alt="" src="https://cdn-images-1.medium.com/max/900/1*iDDdgl0YNt5yOiz3SSnh8Q.png" /></a></figure><figure><a href="https://www.facebook.com/groups/framerjs/?utm_source=Medium&amp;utm_medium=Blog&amp;utm_campaign=responsive_footer2"><img alt="" src="https://cdn-images-1.medium.com/max/265/1*H6W5-QpHqVSRRR2N9NSe3w@2x.png" /></a></figure><figure><a href="https://framer.com/download?utm_source=Medium&amp;utm_medium=Blog&amp;utm_campaign=responsive_footer3"><img alt="" src="https://cdn-images-1.medium.com/max/265/1*WJp-afZyQk72Y14YsubOcQ@2x.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0f4d0d98e2c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/framer-prototyping/using-sketch-and-framer-to-create-responsive-mobile-prototypes-for-remote-testing-part-1-a0f4d0d98e2c">Using Sketch and Framer to Create Responsive Mobile Prototypes for Remote Testing: Part 1</a> was originally published in <a href="https://medium.com/framer-prototyping">Framer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>