<?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[Qwikly - Medium]]></title>
        <description><![CDATA[Convert Sketch Designs to iOS Apps - Medium]]></description>
        <link>https://medium.com/qwikly?source=rss----b9bc89077d2d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Qwikly - Medium</title>
            <link>https://medium.com/qwikly?source=rss----b9bc89077d2d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 14:29:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/qwikly" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Qwikly 1.7-beta]]></title>
            <link>https://medium.com/qwikly/qwikly-1-7-beta-f4f12eacaace?source=rss----b9bc89077d2d---4</link>
            <guid isPermaLink="false">https://medium.com/p/f4f12eacaace</guid>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[swift]]></category>
            <dc:creator><![CDATA[Robert Malko]]></dc:creator>
            <pubDate>Thu, 13 Jul 2017 19:30:51 GMT</pubDate>
            <atom:updated>2017-07-13T19:30:50.741Z</atom:updated>
            <content:encoded><![CDATA[<p>Our latest version of Qwikly focuses on performance enhancements and introduces a sneak peek of our Components feature. Check out the <a href="https://www.getqwikly.com/changelog">full changelog</a> and download a copy to try for free <a href="https://www.getqwikly.com/download">from our website</a>.</p><p>We also have a <strong>50% off </strong>sale going on right now and ending on July 16th (my birthday). Head over to our pricing page <a href="https://www.getqwikly.com/pricing">to purchase a license now</a> to support our future development and unlock Qwikly Pro. If you act soon, you’ll get some extra time on your license, because we’re not starting the 12 month license period until we come out of beta!</p><h3>Performance Enhancements</h3><p>With this release, we really hammered down on some performance trouble spots in our Sketch plugin and our build system. To identify the problem areas, we first profiled (and profiled, and profiled some more…) our code to find any calls that were slowing down Sketch. Then, we looked for opportunities to speed up builds. I am happy to announce that we were able to achieve some serious performance gains with 1.7-beta. Hopefully, you will find builds completing faster and more reliably, all while experiencing as-fast-as-normal Sketch behavior with our plugin enabled.</p><p>There were many culprits, but one really rough spot we noticed involved shape layers with a lot of paths. Sometimes, these complex shapes would make builds take essentially forever to complete. With some strategic fixes to our code generators, we were able to reduce some builds that that took over 90 seconds to well under a second!</p><p>Awesome!</p><h3>Components</h3><p>First off, what are we calling Components? In Qwikly, a Component is any Sketch design layer that is not a basic image, text layer, or shape group layer. All of these “fundamental” layer types are relatively straightforward to convert into their counterparts on the iOS side: UIImageView, UILabel, and custom drawable UIViews using Core Graphics. But how can Qwikly know how to turn something in your Sketch design into a switch or slider? Enter Sketch’s symbols…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TnucRxPYg_JbgNykT3595A.png" /><figcaption>Qwikly’s Sketch Symbols</figcaption></figure><p>When you create a project from one of our three templates, it will come packaged with a very small set of Qwikly Component symbols. Since this is the first release, it’s bundled with just a few Component symbols to introduce this concept. We are really excited about how powerful Components can be, and we will be rolling out more robust support for them in future releases. There’s even talk of possibly supporting <a href="https://medium.com/u/8cebe625c432">Jon Moore</a>’s awesome <a href="https://medium.com/ux-power-tools">UX Power Tools</a> in the future.</p><p>We’ve achieved this by creating JSON mappings for our Sketch symbols and then updating our Sketch plugin to “do stuff” with them. In the future, we’d love to open up these systems so anyone can start creating mappings for their own components. We have a vision for a robust plugin system inside Qwikly, so this is just the beginning of our journey on components.</p><p>Take a look at adding a switch with custom on and off colors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*niBnVr-MRvapnBKyJVf6Tg.gif" /></figure><p>But now we can’t see the “off” color. That’s ok, all you have to do is change the color of the hidden “Off” layer in our symbol.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*8WVMQQ14pRDjdBeUe51_FA.gif" /></figure><h3>What’s Next?</h3><p>Here are some of the things we’re working for the next few releases:</p><ul><li>Bug fixes and rendering improvements: Think rotation, flipped, masks, all font properties.</li><li>More components: Tab Bars/Nav Bars, and support for nested symbols.</li><li>Animation support through the awesome <a href="https://kiteapp.co/">Kite Compositor</a> app.</li></ul><p>Also, after our Independence Day sale ends, we’ll be introducing a full-featured trial period, instead of the limited Qwikly Basic option we have now. You’ll get 14 days to try Qwikly with no restrictions. More on that to come…</p><p>Keep on rocking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4f12eacaace" width="1" height="1" alt=""><hr><p><a href="https://medium.com/qwikly/qwikly-1-7-beta-f4f12eacaace">Qwikly 1.7-beta</a> was originally published in <a href="https://medium.com/qwikly">Qwikly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Future of App Development: Beyond Prototypes]]></title>
            <link>https://medium.com/qwikly/the-future-of-app-development-beyond-prototypes-c04668d3d334?source=rss----b9bc89077d2d---4</link>
            <guid isPermaLink="false">https://medium.com/p/c04668d3d334</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[sketchapp]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Robert Malko]]></dc:creator>
            <pubDate>Wed, 28 Jun 2017 13:22:29 GMT</pubDate>
            <atom:updated>2017-06-28T13:22:29.517Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m a developer by trade, but am incredibly interested in interface design and have personally designed and built many apps over the last 15 years. Like many of you, I am always looking for new ways to improve my productivity and processes. Two years ago, I found myself growing increasingly frustrated by the inefficiencies in building mobile apps. I would get a design from my team, only to have to work with the development team to reassemble the assets, create a prototype that worked, and then start the process all over again <em>from scratch</em> to build the finished product.</p><blockquote>“Why do I have to spend all this time doing the same thing over and over again?”</blockquote><p>Obsessed with this problem, I enrolled in a wonderful program at <a href="https://www.recurse.com/">The Recurse Center</a> in New York. There, I set out to devise a solution that would radically reduce the time and complexity involved in building apps.</p><h3><strong>The Big Idea: </strong>Designs<strong> as code</strong></h3><p>In the last few years, there has been an explosion of app-building tools focused on prototyping, design, development, and design-to-development workflow. There has also been a big shift towards interaction design for mobile, focused on the question of, “Why waste a bunch of time and money to get a product developed when you can produce something that <em>“feels”</em> real and get feedback on it with a prototype?”</p><p>These tools, and especially prototypes, are a wonderful addition to the designer/developer toolkit, but they just scratch the surface of what is possible to make our processes better. Developers still have to “start from scratch” to build the end product. When looked at this way, prototypes have enhanced the process and improved results, but they haven’t made things significantly more efficient.</p><blockquote>For example, we spend a lot of time on prototypes to get user feedback, but they still don’t allow teams to use them as the basis for development.</blockquote><p>One way to address this lingering challenge is to treat our designs themselves as part of the development workflow. <em>“Rob, that’s a pretty heady statement, can you tell me what that means?” </em>Sure!</p><p>If you think about it, designs have a lot of amazing information baked right into them, such as:</p><ul><li>Document structure &amp; hierarchy</li><li>How to draw all the shapes and vectors</li><li>Typography</li><li>All of the various styles you apply to each of your layers</li><li>The layout of your design elements</li></ul><p>Of course, the design needs more information to be able to generate working code. But once I had this “aha” moment (designs as code!), I knew that I had an approach to solve the design&gt;development inefficiencies. In June 2015, I formed Qwikly with my best friend and our co-founder Mark Wise. We set out to build a tool that would allow design and development teams to leverage the rich information contained in their designs, and go directly from design&gt;code without losing any design requirements or duplicating efforts.</p><h3>Introducing Qwikly for Sketch-to-iOS</h3><p>In May, we introduced the first public beta version of Qwikly for Sketch-to-iOS. Qwikly automates much of the repetitive work that occurs when teams move from design to development, saving both designers and developers a lot of time. Importantly, it also alleviates the need for those painful conversations when designs are not faithfully realized during the development process.</p><p><em>Here’s how it works: You download our Sketch plugin, start a new project or enable Qwikly for an existing design, add some interactions, and hit run to see Qwikly generate your code and show your app on the iOS simulator.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*sgW3RgHhv8eg7eLB-T4AaA.gif" /></figure><p>The designers and developers already using Qwikly beta (<a href="http://bit.ly/2rnKAbk">available for free here!</a>) have been giving us great feedback.</p><blockquote><em>“So you’re like a prototyping tool on steroids?”</em></blockquote><p><strong>Yup</strong>! Our goal is to have Qwikly fit right into your existing workflow. Either use Qwikly to replace your traditional prototyping solution, or use it after you prototype in another tool to generate a better starting point for your application. Since we are generating real code, Qwikly will be able to provide features and functionality not seen in traditional prototyping tools.</p><p>Download the beta for free on <a href="http://bit.ly/2rnKAbk">our website</a>. You can pay for an upgrade when you are ready to get the generated code and hide the ‘Made with Qwikly’ splash screen. We’re working <a href="https://trello.com/b/ecwJ25d7/qwikly-public-roadmap">on a lot of new features</a>, including adding rich support for more iOS components through the use of Qwikly’s Sketch symbols, but it can already save you countless hours by bootstrapping your iOS app development while doing things like this (and yes that’s a real project):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*YEqyiuljb9lM5AJdAGOnuw.gif" /></figure><p>With our first product release, Sketch -&gt; iOS is just the first step. Ultimately, we plan to support more design programs (like Photoshop), and more development platforms (like Android and React Native). While we’re still early on in Qwikly’s journey, it’s been awesome to see the vision we had back in 2015 come to fruition and to be receiving such great feedback from our users.</p><h3>The Future: Blending the design + development processes</h3><p>The design and development worlds are inching closer to each other. Every day I see a new article <em>“Should designers learn how to code?”,</em> and more developers are starting to use design tools like Sketch. Qwikly exists in between these worlds, with the goal of designing tools that make building apps easier, faster and hopefully more fun. We believe that when design and technology work better together, it results in better products and happier, more productive teams.</p><p><a href="http://bit.ly/2rnKAbk"><strong>Download Qwikly beta here</strong></a><strong> and tell us which features or platforms you’d like to see us support next.</strong> We’re building Qwikly for you — design and development teams everywhere — so I always want to hear from you.</p><p>Drop us a line in the comments or email me at <a href="/service/mailto:Rob@GetQwikly.com">Rob@GetQwikly.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c04668d3d334" width="1" height="1" alt=""><hr><p><a href="https://medium.com/qwikly/the-future-of-app-development-beyond-prototypes-c04668d3d334">The Future of App Development: Beyond Prototypes</a> was originally published in <a href="https://medium.com/qwikly">Qwikly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Qwikly 1.5-beta]]></title>
            <link>https://medium.com/qwikly/introducing-qwikly-1-5-beta-5937770d5faf?source=rss----b9bc89077d2d---4</link>
            <guid isPermaLink="false">https://medium.com/p/5937770d5faf</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Robert Malko]]></dc:creator>
            <pubDate>Fri, 23 Jun 2017 05:10:03 GMT</pubDate>
            <atom:updated>2017-06-23T05:10:03.482Z</atom:updated>
            <content:encoded><![CDATA[<p>This week we unveiled Qwikly’s 1.5-beta, making it more reliable and easier than ever to turn Sketch designs into iOS apps. We added an interactive help system, brought certain features more to the forefront, and even made it easier for designers to install Xcode, a core requirement for building apps and using Qwikly.</p><p><a href="http://bit.ly/2rnKAbk">Download Qwikly for free here</a>.</p><p>Here’s a look at what’s new:</p><p><a href="https://www.getqwikly.com/changelog">Changelog</a></p><h3>In-app help system</h3><p>Prior to 1.5-beta, understanding every aspect of our Sketch plugin wasn’t always intuitive. Now, we’ve added a contextually aware help system that displays detailed information about every feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Okc4OhbYyV2SfO8BHoTgww.gif" /></figure><h3>Enabling Qwikly for your existing design</h3><p>Qwikly can create a new project based on a template, or you can enable Qwikly for your existing design. This feature was hidden behind a plugin menu item, but now we’ve brought it upfront in the ui.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*y5NCjCM7Q0BF_uXOfWr9PQ.gif" /></figure><h3>New run widget</h3><p>After talking to our users, we knew we needed to put the <strong>run button</strong> front and center instead of buried within the project settings panel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*j5Pi0AqdN593yaP29foVcA.gif" /></figure><h3>System tab in preferences</h3><p>If you try to run without having Xcode and the Command Line Tools installed, you will be prompted to resolve this issue by taking you to the the System Preferences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*vyQEiBoUG_Ew6gjGo7dtdA.gif" /></figure><h3>What’s next?</h3><p>Our next release will support more iOS components through the use of Qwikly’s Sketch symbols! We’re really excited to get that into your hands, so look for a new story talking about that update when it’s released.</p><p>Let us know what features you’d like to see supported by Qwikly in the comments below, or email me at <a href="/service/mailto:rob@getqwikly.com">Rob@getqwikly.com</a>.</p><p>Till next time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5937770d5faf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/qwikly/introducing-qwikly-1-5-beta-5937770d5faf">Introducing Qwikly 1.5-beta</a> was originally published in <a href="https://medium.com/qwikly">Qwikly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>